Skip to content

Commit

Permalink
Revert "Remove H75 (w3c#3650)" and add obsolete front-matter
Browse files Browse the repository at this point in the history 
This reverts commit c7643f8.
  • Loading branch information
@kfranqueiro
kfranqueiro committed Aug 6, 2024
1 parent 938c15f commit ff6d04c
Show file tree
Hide file tree
Showing 4 changed files with 91 additions and 0 deletions.
1 change: 1 addition & 0 deletions techniques/failures/F77.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,7 @@
</section>
</section><section id="related"><h2>Related Techniques</h2><ul>
<li><a href="../general/G108">G108</a></li>
<li><a href="../html/H75">H75</a></li>
</ul></section><section id="resources"><h2>Resources</h2>

<ul>
Expand Down
81 changes: 81 additions & 0 deletions techniques/html/H75.html
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,81 @@
---
obsoleteMessage: |
This technique relates to 4.1.1: Parsing, which was removed as of WCAG 2.2.
obsoleteSince: 22
---
<!DOCTYPE html><html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml"><head><title>Ensuring that Web pages are well-formed</title><link rel="stylesheet" type="text/css" href="../../css/sources.css" class="remove"></link></head><body><h1>Ensuring that Web pages are well-formed</h1><section class="meta"><p class="id">ID: H75</p><p class="technology">Technology: html</p><p class="type">Type: Technique</p></section><section id="applicability"><h2>When to Use</h2>
<p> Any XML-based markup languages. </p>
</section><section id="description"><h2>Description</h2>
<p> The objective of this technique is to avoid key errors that are known to cause
problems for assistive technologies when they are trying to parse contents.
Well-formedness is checked by parsing the document with a conforming XML parser and
checking if the validation report mentions well-formedness errors. Every conforming XML
parser is required to check well-formedness and stop normal processing when a
well-formedness error is found (a conforming XML parser does not need to support
validation).</p>
</section><section id="examples"><h2>Examples</h2>
<section class="example">
<h3></h3>

<p>XML files include a document type declaration, a xsi:schemaLocation attribute or
other type of reference to a schema. The developer can use off-line or online
validators, an XML editor or an IDE with XML support (see Resources below) to check
well-formedness. </p>

</section>
<section class="example">
<h3></h3>

<p> When XML files do not include a document type declaration, a xsi:schemaLocation
attribute or a processing instruction referencing a schema even though there is a
schema for them, the relevant schema is specified by a command line instruction, a
user dialog or a configuration file, and the XML files are checked against the
schema.</p>

</section>
<section class="example">
<h3></h3>

<p>When XML files do not include a document type declaration, a xsi:schemaLocation
attribute or a processing instruction referencing a schema even though there is a
schema for them, the namespace is dereferenced to retrieve a schema document or
resource directory (Resource Directory Description Language: <a href="http://www.rddl.org/">RDDL</a>), and the XML files are checked against the
schema.</p>

</section>
<section class="example">
<h3></h3>

<p>When a Website generates XML dynamically instead of serving only static documents,
a developer can use <a href="http://xmlunit.sourceforge.net/">XMLUnit</a>, <a href="http://xmltestsuite.sourceforge.net/">XML Test Suite</a> or a similar
framework to test the generated XML code. </p>

</section>
</section><section id="tests"><h2>Tests</h2>
<section class="procedure"><h3>Procedure</h3>
<ol>
<li> Load each file into a validating XML parser. </li>
<li> Check that there are no well-formedness errors. </li>
</ol>
</section>
<section class="results"><h3>Expected Results</h3>
<p>Step 2 is true.</p>
</section>
</section><section id="related"><h2>Related Techniques</h2></section><section id="resources"><h2>Resources</h2>

<ul>
<li>
<a href="https://www.w3.org/TR/2004/REC-xml-20040204/Overview.html#sec-well-formed">Well-Formed XML Documents</a> in Extensible Markup Language (XML) 1.0 (Third
Edition), W3C Recommendation 04 February 2004. </li>
<li>
<a href="https://www.w3.org/TR/2004/REC-xml11-20040204/#sec-well-formed">Well-Formed XML Documents</a> in Extensible Markup Language (XML) 1.1, W3C
Recommendation 04 February 2004. </li>
<li>
<a href="https://www.w3.org/TR/REC-xml/#wf-entities">4.3.2 Well-Formed Parsed
Entities</a> in Extensible Markup Language (XML) 1.1, W3C Recommendation 04
February 2004.</li>
</ul>
<p> For other resources, see <a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G134">Validating Web
pages</a>. </p>

</section></body></html>
1 change: 1 addition & 0 deletions techniques/html/H88.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -53,6 +53,7 @@ <h3>Expected Results</h3>
<h2>Related Techniques</h2>
<ul>
<li><a href="../html/H74">H74</a></li>
<li><a href="../html/H75">H75</a></li>
</ul></section><section id="resources"><h2>Resources</h2>

<p>Refer to the resources section of <a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G134">Validating Web
Expand Down
8 changes: 8 additions & 0 deletions understanding/20/parsing.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -158,6 +158,14 @@ <h3>Sufficient Techniques for Parsing</h3>

</li>

<li>

<a href="https://www.w3.org/WAI/WCAG21/Techniques/html/H75" class="html">Ensuring that
Web pages are well-formed
</a>

</li>

</ul>

</li>
Expand Down

0 comments on commit ff6d04c

Please sign in to comment.