2.1.1 vs 2.4.3

[Ramakrishnan Subramanian]

Dear Members,
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)?

Thanks and regards,
Ramakrishnan

[Sean Murphy (seanmmur)]

Hello,

It vilates 2.4.3 focus order. As the keyboard user cannot access the interactive element. Screen Reader navigation is technology specific.



Sean Murphy
SR ENGINEER.SOFTWARE ENGINEERING
***@cisco.com
Tel: [phone]

Cisco Systems, Inc.
The Forum 201 Pacific Highway
ST LEONARDS
2065
Australia
cisco.com

Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
http://www.cisco.com/c/en/us/about/legal/terms-sale-software-license-agreement/company-registration-information.html
-----Original Message-----
From: Ramakrishnan Subramanian <***@gmail.com>
Sent: Monday, 13 August 2018 12:48 PM
To: w3c-wai-***@w3.org
Subject: 2.1.1 vs 2.4.3

Dear Members,
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)?

Thanks and regards,
Ramakrish

[Jan Hellbusch]

Hi,

Post by Ramakrishnan Subramanian
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.: [phone] Mobil: [phone]
--
Accessibility-Consulting seit 15 Jahren
Leistungen, Bücher, Artikel: https://www.barrierefreies-webdesign.de
Blog: https://www.hellbusch.de