RE: WCAG2.1 and keyboard navigation

Hi,

> 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.

In general, only active elements must be in focus order, i.e. links, form elements and widgets.

There may be exceptions in an application (role="application"), where there is no reading mode for screen readers. Text must then either be associated with active elements with aria-labelledby/aria-describedby or can be placed in focus order.

If your popup has forms and focus is within a form element there may be usability issues with screen readers. Typically, Esc is used to leave editing mode in a screen reader, and sometimes Esc closes a dialog window as well. Focussing text could be a solution there.

Jan


--
Hellbusch Accessibility Consulting
Chemnitzer Str. 50, 44139 Dortmund
Tel.: +49 (231) 58054815 Mobil: +49 (163) 3369925
--
Accessibility-Consulting seit 2000 

Leistungen, Bücher, Artikel: https://www.barrierefreies-webdesign.de
Blog: https://www.hellbusch.de