- 🇺🇸United States chri5tia PDX
I re-rolled the patch from #4 to work with Drupal 10.4.x
- 🇨🇦Canada mgifford Ottawa, Ontario
It might also be a Firefox issue.
I don't have a Windows device to test with JAWS, but it could be that running Drupal CMS and testing with JAWS would be a good indication.
This is the fastest way for a JAWS user to get to running Drupal CMS locally to test it:
https://new.drupal.org/drupal-cms/launcherThis may not address this issue reported against Drupal Core.
- 🇨🇦Canada mgifford Ottawa, Ontario
I'm not sure that this patch puts us ahead.
Maybe.
The comment from the Belgium audit is "There is no reason to create a navigation block in the accessibility tree of the language switcher block". Which isn't to say it is a WCAG error, as much as it isn't needed. Maybe it isn't needed, but maybe that depends on the site setup.
Is this just two languages? Would it need it (in the view of Anysurfer.be) if there were 5 languages?
I usually try to find some documentation for this.
There is no minimum that I could find in:
- https://wai-aria-practices.netlify.app/aria-practices/
- https://udn.realityripple.com/docs/Web/Accessibility/ARIA/Roles/Navigati...
- https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Referenc...
- https://www.w3.org/WAI/ARIA/apg/practices/landmark-regions/
@andystitt829 you make good points here. As you say, "it could be a navigation menu on its own, or it could not."
But if it is going to be brought into another menu, it wouldn't be that difficult to strip out the nav function.
I do think we need to document how to build a list involving the language switcher where the 'role="navigation' is removed, alternatively, how we add 'role="navigation' should we change the default as per this patch.
Not having the 'role="navigation' would be a slight simplification of the code. It may not be needed. I do think it would be useful to have some documentation on this with some actual user testing though.