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

Jump to bottom

List SC 4.1.1 as obsolete #2823

Closed
wants to merge 5 commits into from
Closed

List SC 4.1.1 as obsolete #2823

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
9db7363
List SC 4.1.1 as obsolete
WilcoFiers Dec 1, 2022
ca34887
Update guidelines/sc/20/parsing.html
WilcoFiers Dec 2, 2022
71dc84b
Removing extra full stop
alastc Dec 2, 2022
5c9b19c
Update parsing.html
mbgower Dec 12, 2022
bcc6cd8
Update guidelines/sc/20/parsing.html
alastc Mar 9, 2023
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
31 changes: 27 additions & 4 deletions guidelines/sc/20/parsing.html
View file
Open in desktop
@@ -1,8 +1,31 @@
<section class="sc">

<h4>Parsing</h4>
<h4>Parsing (Obsolete)</h4>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This "(Obsolete)" is new.


<p class="conformance-level">A</p>

<p>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>

<div class="note">
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This note is also new. (Everything else is a revert from #2797)

<p>
Modern web technologies have standardized how user agents parse incorrect markup.
Any invalid markup is therefore allowed under 4.1.1 Parsing for technologies such as
HTML 5 and CSS 3. This success criterion is always satisfied for these technologies.
This success criterion is therefore obsolete.
</p><p>
Issues such as incorrect states or names due to a duplicate ID, or missing roles
due to inappropriately nested elements are covered by different success criteria.
</p>
</div>

<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>


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

</section>
</section>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note I didn't update the understanding doc. If this goes through, the understanding doc needs to be tweaked. Happy to help with that if the group's open to this solution.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

4.1.1 is already noted as being obsolete in the PR #2840, which has been merged