Update "Nested headers" accessibility docs #10088
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Why should it be hard to build a logical semantic structure. And the size of the fonts don't help screen readers.
| @@ -733,8 +733,9 @@ <h1 id="accessibility">Accessibility</h1> | |||
| {% endhighlight %} | |||
|
|
|||
| <h3>Nested headers</h3> | |||
| <p>Another "gotcha" has to do with how you nest your <code><header></code> elements. <a href="http://squizlabs.github.io/HTML_CodeSniffer/Standards/Section508/">Section 508</a> states that your largest header must be an <code>h1</code>, and the next header must be an <code><h2></code>, etc. This is hard to achieve in practice, but if the largest header on your site is smaller than Bootstrap's default 38px, you should consider modifying your stylesheets before using a smaller header element.</p> | |||
|
|
|||
| <p>Another "gotcha" has to do with how you nest your header elements (the H1, H2, H3...H6 tags). <a href="http://squizlabs.github.io/HTML_CodeSniffer/Standards/Section508/">Section 508</a> states that your largest header must be an <code><h1></code> followed by an other <code><h1></code> or a subordinate heading element (h2 to h6). The structure of the headers should reflex the structure of your document. So the heading structure should be logically nested. Screen readers read this semantic heading structure to construct a table of contents. Screen readers don't use any formatted style. Visual readers use the formatted style in stead of the semantic structure. See also: <a href="http://accessibility.psu.edu/headings">http://accessibility.psu.edu/headings</a>.</p> | |||
There was a problem hiding this comment.
"H1" etc. ought not to be capitalized, for consistency with the rest of the docs.
There was a problem hiding this comment.
Should use <code> around the heading tag references
|
@cvrebert thanks for your fixes |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why should it be hard to build a logical semantic structure? And the size of the fonts don't help screen readers.