- From: Ramakrishnan Subramanian <ram.eict2013@gmail.com>
- Date: Wed, 9 Jan 2019 19:19:09 +0530
- To: public-aria@w3.org
Hi Team, I feel that there is inconsistency between the point mentioned in aria 1.1 and the point in wcag 2.0 regarding the focus order behavior for Non-modal dialog. From WCAG 2.0 I understand that, From the last interactive control within the Non-modal, the tab focus can go to the next interactive control in the page which is out of the non-modal dialog. If there is any change in the behavioral pattern updated in aria 1.1. or, if I had mis interpreted the points, please kindly help me understand. Below I have given the relevant points and their links. WAI-ARIA Authoring Practices 1.1 https://www.w3.org/TR/wai-aria-practices-1.1/#dialog_modal Under the heading: 3.8 Dialog (Modal) (Like non-modal dialogs, modal dialogs contain their tab sequence. That is, Tab and Shift + Tab do not move focus outside the dialog) Understanding Success Criterion 2.4.3 | Understanding WCAG 2.0 https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-order.html Point 2 below the heading: Examples of Success Criterion 2.4.3 (2. A Web page implements modeless dialogs via scripting. When the trigger button is activated, a dialog opens. The interactive elements in the dialog are inserted in the focus order immediately after the button. When the dialog is open, the focus order goes from the button to the elements of the dialog, then to the interactive element following the button. When the dialog is closed, the focus order goes from the button to the following element.) -- Thanks and Regards Ramakrishnan
Received on Wednesday, 9 January 2019 13:54:19 UTC