Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add explainer about applicability of SC 2.4.6 #1834

Merged
merged 3 commits into from
Sep 30, 2021
Merged

Add explainer about applicability of SC 2.4.6 #1834

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d813ced
add section explaining SC 2.4.6 does not require the heading describe…
mattgarrish Sep 29, 2021
09550e3
add change log entry
mattgarrish Sep 29, 2021
a704188
s/that that/that the/
mattgarrish Sep 30, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 28 additions & 1 deletion epub33/a11y-tech/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1199,6 +1199,31 @@ <h4>TITLES-002: Ensure numbered headings reflect publication hierarchy</h4>
&lt;/html></pre>
</aside>
</section>

<section class="suppress-numbering" id="titles-003">
<h4>TITLES-003: Heading topic or purpose</h4>

<p>[[WCAG2]] <a href="https://www.w3.org/TR/WCAG2/#non-text-content">Success Criterion 2.4.6</a>
currently states that all headings must describe their topic or purpose. The implication of this
wording is that all chapters in a novel, for example, have a topic or purpose and that the topic
or purpose is always clearly reflected by the title of the chapter. Not only is this not always
the case, but this success criterion also complicates the use of chapter numbers as headings
since these do not establish a topic.</p>

<p>After discussion in the <a href="https://github.com/w3c/wcag/issues/2039">Accessibility
Guidelines Working Group's issue tracker</a>, it is clear that the <a
href="https://www.w3.org/WAI/WCAG21/Understanding/headings-and-labels">understanding
document for 2.4.6</a> captures the intent of the success criterion better than the current
wording &#8212; namely, that the requirement for headings is only that they establish a unique
context for the content.</p>

<p>By this interpretation, the headings in publications should always pass provided they are
unique.</p>

<p>It is expected that the wording of the success criterion will be updated to better reflect the
uniqueness requirement, likely in the future WCAG 3 due the complexities of changing the wording
for WCAG 2.</p>
</section>
</section>

<section id="sec-wcag-descriptions">
Expand Down Expand Up @@ -1291,7 +1316,6 @@ <h3>Accessible Alternatives</h3>
<p>This section will be updated with techniques for using multiple renditions when there is enough
support in Reading Systems to broadly recommend their use.</p>
</section>

</section>
<section id="sec-epub">
<h2>EPUB Techniques</h2>
Expand Down Expand Up @@ -1691,6 +1715,9 @@ <h2>Change Log</h2>
>working group's issue tracker</a>.</p>

<ul>
<li>29-Sep-2021: Added <a href="#titles-003">TITLES-003</a> to explain that headings only have to be
unique, not define the topic or purpose of a section. See <a
href="https://github.com/w3c/epub-specs/issues/1810">issue 1810</a>.</li>
<li>10-June-2021: Clarified the technique on meaningful sequence that it applies to content that spans
pages in a spread and is not about ordering documents in the spine. See <a
href="https://github.com/w3c/epub-specs/issues/1695">issue 1695</a>.</li>
Expand Down