E-mail List Archives
Thread: Best Practices
Number of posts in this thread: 3 (In chronological order)
From: Sumit Patel
Date: Wed, Mar 11 2020 2:59AM
Subject: Best Practices
No previous message | Next message →
Hai all,
Again Sumit here....
I've a doubt on the best practices
Even though, WCAG says
Heading levels should be semantically logical
Provide unique label for each navigation landmarks if there are
multiple navigation landmarks are in a page
Use a single <h1> in a page
All the content should be marked under regions
Iheard that these all are best practices. Not really violations of WCAG.
What if in the case of "Skip to main content" and
"Skip navigation" link. Is it fall into best practices or violations
of WCAG - 2.4.1 (Bypass Blocks)?
Sumit Patel
From: Jared Smith
Date: Wed, Mar 11 2020 8:03AM
Subject: Re: Best Practices
← Previous message | Next message →
Sumit -
WCAG requires "a mechanism" to bypass repeated blocks of content on
multiple pages - typically interpreted to mean navigation. If your
main content starts with a heading (optimally an <h1>) or if you use a
<main> element, these could be considered mechanisms to bypass the
navigation, thus a "skip" link would not be necessary for WCAG
conformance.
However, while headings and regions are useful for screen reader
users, they do not (yet) provide much utility for sighted keyboard
users who would need to manually navigate through the repeated
navigation on each page. Because of this, we still strongly recommend
a "skip" link be provided, even if WCAG may not require it.
The things you listed aren't "best practices" arbitrarily - they are
best practices because they provide demonstrable benefit to users with
disabilities.
Thanks,
Jared
From: Jeremy Echols
Date: Wed, Mar 11 2020 1:32PM
Subject: Re: Best Practices
← Previous message | No next message
It may also be worth noting that today's best practices often become tomorrow's requirements. If you're looking for a cheaper way to follow WCAG, bear in mind that it's actually a better investment to get things done today that are likely to be required in the next release of WCAG compared to doing the bare minimum today and having gaps in the future.