This document:Public document·View comments·Disposition of Comments·
Nearby:Accessibility Guidelines Working Group Other specs in this tool Accessibility Guidelines Working Group's Issue tracker
Quick access to LC-2585 LC-2586 LC-2597 LC-2603 LC-2604 LC-2607 LC-2608 LC-2614 LC-2615 LC-2616 LC-2617 LC-2618 LC-2621 LC-2624 LC-2629 LC-2630 LC-2633 LC-2634 LC-2717 LC-2722 LC-2733 LC-2744 LC-2747 LC-2748 LC-2749 LC-2774 LC-2781 LC-2782 LC-2783 LC-2828 LC-2829
Previous: LC-2747 Next: LC-2604
http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-order.html I have long felt that inserting dynamic content behind the control that is inserting the content, messes up screen reader users. If the inserted information has any focus-able content then I suggest it is a failure if 2.4.3 because the person is at a certain point of moving through the page, and important information that they want to focus on is behind them in the focus order. Proposed Change: I can create a technique failure of 2.4.3 due to dynamic insertion of focus-able content before the control that inserts it.