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-2429 LC-2453 LC-2454 LC-2455 LC-2461 LC-2462 LC-2463 LC-2468 LC-2470 LC-2472 LC-2473 LC-2474 LC-2477 LC-2478 LC-2479 LC-2480 LC-2495 LC-2497 LC-2498 LC-2499 LC-2501
Previous: LC-2501 Next: LC-2461
I feel that the 2 sufficient techniques for SC 2.4.1 should be 'and' not 'or'. I had originally read this that 1 and 2 were exactly that an 'and', then someone I know who does accessibility testing for a living, pointed out to me that I was wrong. They are not 'and', ie you can do one or the other. However I see a problem with that: Skip links are of main benefit to sighted users who navigate via the keyboard and are of only very limited benefit to screen reader users. However H69 (heading elements) is only of use to screen readers and provides no help whatsoever for sighted users navigating via the keyboard. (I don't know enough about map, frame and scripting to comment on those, but as they have been grouped with H69, I suspect that they too are of little or no benefit to sighted people who navigate with the keyboard.) Nonetheless, if someone writes a web page to H69, they would be deemed to have passed SC 2.4.1, even though they have not provided any method for sighted keyboard users to bypass blocks of content that are repeated on multiple pages. The most number of hits of the tab key that I counted before getting to the main page content on one web site was 69 each time I went onto a new page. Proposed Change: Please make it 'and' so that both sighted keyboard users and screen reader users are helped. At the moment it's perfectly possible to help only one of those groups and not help the other and still pass this SC.