Edit comment LC-2605 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-2625 Next: LC-2620

Comment LC-2605
Commenter: Mark Rogers <mark.rogers@powermapper.com>

Resolution status:

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.
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Developed and maintained by Dominique Hazaël-Massieux (dom@w3.org).
$Id: 2605.html,v 1.1 2017/08/11 06:39:57 dom Exp $
Please send bug reports and request for enhancements to w3t-sys.org