- From: Jan Hellbusch <jan@hellbusch.de>
- Date: Mon, 13 Aug 2018 11:13:09 +0200
- To: <w3c-wai-ig@w3.org>
Hi, > I would like to get your opinion on the following scenario: > If an interactive element misses the tab-order, which criteria does it violate? > Example: A scripted button is not given (tabindex=”0”). Since a Keyboard > only user cannot reach this with tab/shift tab key, does it violate (2.1.1)? or, > since a Screen reader user can still reach it with quick navigation Key (B) and > activate the Button, does it violate (2.4.3)? I know Sean just suggested 2.4.3, but 2.4.3 is about focus order (tab key) and starts with " If a Web page can be navigated sequentially ...", which your page ist obviously not. 2.1.1 says it must be accessible by keyboard (tab key or other browser function). If you need a mouse to activate the button, then 2.1.1 fails (although I am ignoring the num block on the keyboard, which kann also control the mouse. It is not a too practical solution, though). On not too practical terms 2.1.1 is really hard to fail. To test keyboard accessibility you shouldn't have a screen reader running. At least if you are testing by WCAG. Jan -- Hellbusch Accessibility Consulting Chemnitzer Str. 50, 44139 Dortmund Tel.: +49 (231) 58054815 Mobil: +49 (163) 3369925 -- Accessibility-Consulting seit 15 Jahren Leistungen, Bücher, Artikel: https://www.barrierefreies-webdesign.de Blog: https://www.hellbusch.de
Received on Monday, 13 August 2018 09:13:40 UTC