Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

i18n needed for "left navigation" #3658

Closed
mitchellevan opened this issue Jan 26, 2024 · 6 comments · Fixed by #3765
Closed

i18n needed for "left navigation" #3658

mitchellevan opened this issue Jan 26, 2024 · 6 comments · Fixed by #3765

Comments

@mitchellevan
Copy link
Contributor

Currently

Some pages in Understanding give "left navigation" as an example. Here's one I noticed:

https://github.com/w3c/wcag/blob/main/understanding/22/focus-not-obscured-minimum.html

This is not as internationally neutral as it should be. In web pages where the primary language is a right-to-left language, it is a common convention for such navigation bars to be on the right, not the left.

Proposed

Find references to "left navigation" in non-normative content.

Change each to "side navigation", "left or right navigation", or similar, to account for both left-to-right (LTR) and right-to-left (RTL) web pages.

@rscano
Copy link
Contributor

rscano commented Jan 26, 2024

These pages are in English so left is correct. Btw I think the left and right indication inside Text could be in contrast with Wcag for sensory characteristics . Agree to have side navigation also as accessible name for aria region.

@DuffJohnson
Copy link

Left-side navigation may be more common in English as compared to right-side navigation, but that's about all one could say about it. Some websites use the right-side. Adobe's new Acrobat UI (controversially) puts navigational bookmarks on the right side. "Side navigation" is neutral and thus, preferable.

@mitchellevan
Copy link
Contributor Author

These pages are in English so left is correct.

If the prose were describing the English-language W3C pages themselves then this would be true. However, the prose at issue is describing the web in general, which is in many languages.

@rscano
Copy link
Contributor

rscano commented Jan 27, 2024

I agree @mitchellevan. What i've wrote (full comments) point attention that left / right are language reading order based and that can cause violation of a WCAG SC using words like" left menu" "top link".

@mbgower
Copy link
Contributor

mbgower commented Jan 30, 2024

Two of the uses of "left" are in an example that seems to refer to what happens on on a specific website. So I think "side" navigation is preferable in the third usage, it may or may not be as good in the example. (And of course to take this another step, in some situations, the 'side' navigation is repositioned 'above' the main content in top down languages, which would be better spoken of as 'before')

@mitchellevan or @rscano can either of you pick this up and put in a small PR to address?

@giacomo-petri
Copy link
Contributor

How about employing "side navigation," specifically indicating that in the present instance it is visually positioned on the "left side"? This maintains a generic approach suitable for both left-to-right and right-to-left languages, while offering additional context for the particular example.

@avkuo avkuo self-assigned this Mar 26, 2024
avkuo added a commit that referenced this issue Mar 27, 2024
Closes #3658
Updated one instance of left to side navigation. Decided to leave first two left navigation instances because they don't seem to respond to right-left layout. Checked the rest of the understanding folder, couldn't find anymore instances.
mbgower pushed a commit that referenced this issue Jun 12, 2024
Closes #3658
Updated one instance of left to side navigation. Decided to leave first
two left navigation instances because they don't seem to respond to
right-left layout. Checked the rest of the understanding folder,
couldn't find anymore instances.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants