Re: WAI Translations - Language of site nav - talk by phone

ahh yes, good points.

Perhaps we can do something to emphasize the translated pages - make them
bigger and boldly outlined in the navigation list and provide a legend for
the meaning of that presentation.



On Thu, Oct 25, 2018 at 4:05 AM, Eric Eggert <ee@w3.org> wrote:

>
>
> On 25 Oct 2018, at 10:08, Sharron Rush wrote:
>
> My preference was the example given where the only navigation that shows on
>> the translated page are links to other pages that have also been
>> translated. The only other link would be back to the WAI Home page.
>> Otherwise it is confusing and risky. If this is the only question to meet
>> about, maybe just put on a survey or use the GitHub issue you raised?
>>
>
> I feel the opposite way, having language “ghettos” means that people don’t
> see the breadth of our content, it also means we don’t show a commitment to
> translations to the user.
>
> As someone who regularly had content withheld from them because someone
> thought “this is enough translated information for German readers”, I am
> very reluctant to not give users options to see English content 8in the
> navigation) instead. It also means that potential translators would not see
> what else could be translated.
>
> While I feel relatively strongly that we should keep the navigation (with
> clear indication of English links, I agree that it is a problem as long as
> we have only a handful resources translated maximum.
>
> Maybe we could have an expand/collapse underneath the French only
> information that says “more resources in this category in English” that on
> click reveals the English navigation items (setting cookie to keep it
> expanded?).
>
> I haven’t processed the discussion enough to come up with a “clever”
> solution to this.
>
> Eric
>
>
>> Best,
>> Sharron
>>
>>
>>
>> On Wed, Oct 24, 2018 at 6:34 PM, Shawn Henry <shawn@w3.org> wrote:
>>
>> Summary: If you have a chance to talk more about WAI Translations while at
>>> TPAC, great! If you can loop me in, even better! (ping me in IRC
>>> afternoons
>>> Europe time)
>>>
>>> Big issue right now is having most of the navigation in English on
>>> translated pages. When we looked at other options, they all seemed to
>>> have
>>> negatives (cons) that were pretty much "showstoppers" -- but maybe we
>>> missed something?
>>>
>>> More info:
>>>
>>> At the EOWG meeting Tuesday afternoon, some participants did not like
>>> that
>>> in the translation mock-up most of the navigation was in English and some
>>> was in French. I explored some options (including not having the
>>> site-wide
>>> navigation on translations), Eric provided more input (showing why
>>> that's a
>>> bad idea for some users, like him :-), I revised the info and straw
>>> proposal, and now it's ready for more input. Analysis of the issue and
>>> options is at:
>>> <https://www.w3.org/wiki/WAI_Translations#Language_of_site_n
>>> av_-_or_not_include_in_translations>
>>>
>>> (GitHub issue for more input: <https://github.com/w3c/wai-tr
>>> anslations/issues/14> )
>>>
>>> It would be a little smoother for me if we did the next steps on getting
>>> shared understanding by phone and then I can integrate additional info in
>>> the wiki. However, if it's easier to send input via e-mail, or edit the
>>> wiki, or put in GitHub issues, feel free to do that instead.
>>>
>>> In case we can't talk this week and can talk next week, I set up a Doodle
>>> poll to try to find a time:
>>>         https://doodle.com/poll/agxdrg5euvxf6wpq
>>>
>>> I hope that we'll talk about the nearly-final proposals in the EOWG
>>> teleconference on Fri 2 Nov (I'll send a request to eo-plan) -- and
>>> finalize the UI proposals right after that.
>>>
>>> Cheers,
>>> ~Shawn
>>>
>>>
>>>
>>
>> --
>> Sharron Rush | Executive Director | Knowbility.org | @knowbility
>> *Equal access to technology for people with disabilities*
>>
>
>
>
>
>
> --
>
> Eric Eggert
> Web Accessibility Specialist
> Web Accessibility Initiative (WAI) at World Wide Web Consortium (W3C)
>
>


-- 
Sharron Rush | Executive Director | Knowbility.org | @knowbility
*Equal access to technology for people with disabilities*