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-2582 LC-2583 LC-2584 LC-2595 LC-2596 LC-2601 LC-2605 LC-2610 LC-2611 LC-2612 LC-2613 LC-2619 LC-2620 LC-2622 LC-2625 LC-2626 LC-2627 LC-2628 LC-2631 LC-2632 LC-2646 LC-2647 LC-2648 LC-2683 LC-2684 LC-2703 LC-2704 LC-2718 LC-2719 LC-2723 LC-2724 LC-2726 LC-2728 LC-2729 LC-2730 LC-2745 LC-2770 LC-2771 LC-2773
Previous: LC-2625 Next: LC-2620
I can see what example 3 is trying to demonstrate, but if this example is used verbatim I think it would lead to a failure (because the tab order doesn't match the presentation order) Worth noting that H4 example 3 is also almost identical to F44 failure example 1 (so it's pretty confusing) Proposed Change: Perhaps adding some CSS classes that imply layout is different from source order would make this clearer: <a href="" class="topNav" tabindex="1">one</a> <a href="" class="subNav" tabindex="2">three</a> <a href="" class="topNav" tabindex="1">two</a> <a href="" class="subNav" tabindex="2">four</a> The other alternative would be placing the code in table like example 1.