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.

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

4.1.1 updates #2840

Merged
merged 4 commits into from Dec 20, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
7 changes: 3 additions & 4 deletions guidelines/sc/20/parsing.html
@@ -1,8 +1,7 @@
<section class="sc">

<h4>Parsing</h4>
<h4>Parsing (Obsolete and removed)</h4>

<p class="note">This criterion was originally adopted to address problems that Assistive Technology had directly parsing HTML. Assistive Technology no longer has any need to directly parse HTML and, consequently, these problems no longer exists. Accessibility errors failed by this criterion also fail other criteria. This criteria no longer has utility and is removed.</p>

<p>This criterion has been removed.</p>

</section>
</section>
16 changes: 14 additions & 2 deletions understanding/20/parsing.html
Expand Up @@ -13,13 +13,25 @@ <h1>Understanding Parsing</h1>
<h2>Intent of Parsing</h2>

<div class="wcag22">
<p class="note">This criterion has been removed from WCAG 2.2.</p>
<p>This criterion has been removed from WCAG 2.2.</p>

<p>The intent of this Success Criterion was to ensure that user-agents, including assistive technologies, can accurately interpret and parse content. Since WCAG 2.0 was published, the specifications (such as HTML) and browsers have improved their handling of parsing errors. It is also that case that assistive technology used to do their own parsing of markup, but now rely on the browser. For that reason this success criterion has been removed. Many issues that would have failed this criterion will fail <a href="info-and-relationships">Info and Relationships</a> or <a href="name-role-value">Name, Role, Value</a>. Other issues are excepted by the "except where the specification allow these features" part of the criterion.</p>
<p>The intent of this Success Criterion was to ensure that user-agents, including assistive technologies, could accurately interpret and parse content. Since WCAG 2.0 was published, the specifications (such as HTML) and browsers have improved their handling of parsing errors. It is also that case that assistive technology used to do their own parsing of markup, but now rely on the browser. For that reason this success criterion has been removed. Many issues that would have failed this criterion will fail <a href="info-and-relationships">Info and Relationships</a> or <a href="name-role-value">Name, Role, Value</a>. Other issues are excepted by the "except where the specification allow these features" part of the criterion.</p>

<p>The following content is left for historical purposes to show the original intent.</p>

<hr />

<blockquote class="scquote">
<p>Success Criterion <a href="https://www.w3.org/TR/WCAG21/#parsing" style="font-weight: bold;">4.1.1 Parsing</a> (Level A): In content implemented using markup languages, elements have complete start and end
tags, elements are nested according to their specifications, elements do not contain
duplicate attributes, and any IDs are unique, except where the specifications allow
these features.
</p>
<p class="note">Start and end tags that are missing a critical character in their formation, such
as a closing angle bracket or a mismatched attribute value quotation mark are not
complete.
</p>
</blockquote>
</div>

<p>
Expand Down