Good afternoon!
I am reviewing accessibility of our Humboldt County, CA page Library Internet Links<https://humboldtgov.org/444/Internet-Links>. I have come across something that seems to pass WCAG 2 requirements, but not ACT requirements. This has to do with roles that have relationships (e.g. menu and menuitem), and whether or not it is still accessible when other roles are between them.
Within ACT, it seems this was determined to not be accessible, so the definition of Owned<https://www.w3.org/WAI/standards-guidelines/act/rules/bc4a75/proposed/#owned-by> was made more strict (where roles with relationships must be direct children in the accessibility tree, not just descendants). However, in my testing, having a "heading" role between "menu" and "menuitem", for example, doesn't interfere with screen readers; and it actually seems helpful to have the ability to navigate these items as a menu of subpages or as headings with a summary about each topic. I have included screenshots below my signature, in case it helps with visualizing this.
I was hoping for feedback on why it was determined that the direct child relationship is required, and if/how it affects assistive technology when there are other roles between.
Much appreciated,
Mike
[County of Humboldt Logo]<https://humboldtgov.org/>
Michael Tjoelker
Applications Analyst
Humboldt County IT
Main Line: 707-445-7556
Help Desk: 707-268-3671
Screenshot of accessibility tree:
[accessibility tree example with menu > heading > menuitem]
Screenshot of page:
[screenshot of a web page showing a listing of subpages, and each link contains a brief page summary below it.]
