WCAG2.1 and keyboard navigation

Ginger Claassen <[email protected]> Tue, 21 Jan 2020 13:05:11 +0100
Newsgroups gmane.org.w3c.accessibility.general
Message-ID <[email protected]>
Hi folks,


I have a question regarding keyboard navigation and WCAG2.1. We had a
discussion today with one colleague who is blind and one who is visually
impaired (screen magnifier user).

What exactly has to be in keyboard navigation - especially in a pop-up
dialogue. I, as a screen reader user, am of the opinion that only
interaction elements have to be keyboard navigateable and my colleague
is of the opinion that also the text in a dialogue box as well as text
in general has to be in the tab-order.

Looking in the WCAG2.1 we were not sure how to interpret it: At one
point it says all elements have to be in tab-order and a bit further
down it says only interaction elements have to be in tab-order.

Thus, is there a clear rule for this, is this rather weak and therefore
depends (both would be a pass) or is there a destinction missing between
SR and SM users?


I am looking forward for your expert opinions!


Solong and thx


      Ginger