Expand tab navigation functionality to all widgets

robert.wiwi_fulcogis

Currently, the tab order created by the A11Y "auto-calculate element tab orders in fixed layout" option skips over (1) plain text widgets and (2) views within the Views Navigation widget. Functional tab navigation is necessary for compliance with the Americans with Disabilities Act (ADA) and Web Content Accessibility Guidelines (WCAG). In the US, government entities are required to meet WCAG 2.1 Level AA by April 2026. 

johnsonn35_MDHHS

With the caveat that I'm not an accessibility expert:

If plain text widgets received focus, I think it might actually be like telling the user, "you can type here," or, "this is an interactive element." You DO want things like links and buttons to receive focus, but not just plain text.

For the section views, use the arrow keys to navigate inside the section once you've tabbed to it. Being able to navigate only with the Tab key is definitely not a requirement of the upcoming federal rule. (Keyboard access/no keyboard traps is.)