search

w3c / wcag21

Repository used during WCAG 2.1 development. New issues, Technique ideas, and comments should be filed at the WCAG repository at https://github.com/w3c/wcag.
https://w3c.github.io/wcag/21/guidelines/
Other
142 stars 55 forks source link

Understanding Success Criterion 2.4.1: Bypass Blocks #939

Closed devarshipant closed 6 years ago

devarshipant commented 6 years ago

First bullet under Benefits does not sound like a Benefit on satisfying this criterion:

When this Success Criterion is not satisfied, it may be difficult for people with some disabilities to reach the main content of a Web page quickly and easily.

Compare it to second bullet, where it's usage is more appropriate.

Screen reader users who visit several pages on the same site can avoid having to hear all heading graphics and dozens of navigation links on every page before the main content is spoken.

awkawk commented 6 years ago

Thank you for the comment. Can you suggest improved language for the first bullet? When I review it, it seems that a positive restatement of this first bullet is what the 2nd and 3rd bullets do. Perhaps we should just remove the first bullet?

devarshipant commented 6 years ago

What do you think of combining the first and second bullets to something like:

A mechanism to bypass repetitive blocks of content allows screen reader and keyboard only users who visit several pages on the same site to reach content with fewer keystrokes.

awkawk commented 6 years ago

The three bullets are: -When this Success Criterion is not satisfied, it may be difficult for people with some disabilities to reach the main content of a Web page quickly and easily.

Your suggestion makes the combined bullet overlap with the original 3rd bullet. What to do with that one?

devarshipant commented 6 years ago

Can we replace the first 3 bullets with the revised combined bullet?

Thanks, Devarshi

On Fri, May 25, 2018 at 11:47 AM, Andrew Kirkpatrick < notifications@github.com> wrote:

The three bullets are: -When this Success Criterion is not satisfied, it may be difficult for people with some disabilities to reach the main content of a Web page quickly and easily.

  • Screen reader users who visit several pages on the same site can avoid having to hear all heading graphics and dozens of navigation links on every page before the main content is spoken.
  • People who use only the keyboard or a keyboard interface can reach content with fewer keystrokes. Otherwise, they might have to make dozens of keystrokes before reaching a link in the main content area. This can take a long time and may cause severe physical pain for some users.

Your suggestion makes the combined bullet overlap with the original 3rd bullet. What to do with that one?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/w3c/wcag21/issues/939#issuecomment-392100144, or mute the thread https://github.com/notifications/unsubscribe-auth/AHCQkPsZnftmydyN-zeEclbZgrH9Scnwks5t2Cd-gaJpZM4UK6f4 .

michael-n-cooper commented 6 years ago

This issue was moved to w3c/wcag#404