- From: Sailesh Panchang <sailesh.panchang@deque.com>
- Date: Wed, 14 Dec 2022 08:54:08 -0500
- To: Accessibility Conformance Testing <public-wcag-act@w3.org>, w3c-wai-gl@w3.org
Ref: https://www.w3.org/2022/12/13-ag-minutes.html#item09 The ACT Rule title: "Iframe with interactive elements is not excluded from tab-order" seems to mistate what is actually meant based on a reading of the description. Ref: https://www.w3.org/WAI/standards-guidelines/act/rules/akn7bn/proposed/ Based merely on the title I wondered why is this associated with SC 2.1.1 ( keyboard navigation) and not SC 2.4.3. The description states, "This rule checks that iframe elements which contain an interactive (tabbable) element are not excluded from sequential focus navigation" and it relies on negative tabindex to identify such a situation. It is mapped against: Atomic rule to test 2.1.1: Keyboard (Level A). Therefore, based on the description and intended mapping, I believe, the Rule should be more accurately titled as "Iframe with interactive element(s)is focus-navigable and keyboard operable", as this is what the rule really checks for. Also, the word "sequential" should perhaps be dropped from the description. Getting rid of the tabindex does not by itself ensure the focus order is meaningful or logical. Once such an iframe is established to be keyboard navigable primarily, a test against SC 2.4.3 is needed to establish that it is navigable in the expected order; i.e. check for tab order sequence . Should the description section for the rule clarify why an interactive iframe is being singled out over other interactive elements or containers that hold them? Thanks, -- Sailesh Panchang Customer Success Strategist and Principal Accessibility Consultant Deque Systems Inc 381 Elden Street, Suite 2000, Herndon, VA 20170 Mobile: 571-344-1765
Received on Wednesday, 14 December 2022 13:54:22 UTC