Skip to content

Commit

Permalink
Remove unnecessary technique title from technique links
Browse files Browse the repository at this point in the history 
these are auto-populated by the publishing script
  • Loading branch information
@patrickhlauke
patrickhlauke committed Sep 3, 2024
1 parent 71ff5c1 commit 633684e
Showing 1 changed file with 16 additions and 36 deletions.
52 changes: 16 additions & 36 deletions understanding/20/name-role-value.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -98,27 +98,23 @@ <h4>Situation A: If using a standard user interface component in a markup langua
</li>
<li>
<p>
<a href="../Techniques/general/G108" class="general">Using markup features to expose the name and role, allow user-settable properties
to be directly set, and provide notification of changes
</a> using technology-specific techniques below:
<a href="../Techniques/general/G108" class="general"></a> using technology-specific techniques below:
</p>
<ul>
<li>
<a href="../Techniques/html/H91" class="html">Using HTML form controls and links</a>
<a href="../Techniques/html/H91" class="html"></a>
</li>
<li>
<a href="../Techniques/html/H44" class="html">Using label elements to associate text labels with form controls</a>
<a href="../Techniques/html/H44" class="html"></a>
</li>
<li>
<a href="../Techniques/html/H64" class="html">Using the title attribute of the frame element</a>
<a href="../Techniques/html/H64" class="html"></a>
</li>
<li>
<a href="../Techniques/html/H65" class="html">Using the title attribute to identify form controls when the label element cannot
be used
</a>
<a href="../Techniques/html/H65" class="html"></a>
</li>
<li>
<a href="../Techniques/html/H88" class="html">Using (X)HTML according to spec</a>
<a href="../Techniques/html/H88" class="html"></a>
</li>
</ul>
</li>
Expand Down Expand Up @@ -146,9 +142,7 @@ <h4>Situation C: If using a standard user interface component in a programming t
<ul>
<li>
<p>
<a href="../Techniques/general/G135" class="general">Using the accessibility API features of a technology to expose the names and roles,
allow user-settable properties to be directly set, and provide notification of changes
</a> using technology-specific techniques below:
<a href="../Techniques/general/G135" class="general"></a> using technology-specific techniques below:
</p>
<ul>
<li>
Expand All @@ -166,10 +160,7 @@ <h4>Situation D: If creating your own user interface component in a programming
<ul>
<li>
<p>
<a href="../Techniques/general/G10" class="general">Creating components using a technology that supports the accessibility API features
of the platforms on which the user agents will be run to expose the names and roles,
allow user-settable properties to be directly set, and provide notification of changes
</a> using technology-specific techniques below:
<a href="../Techniques/general/G10" class="general"></a> using technology-specific techniques below:
</p>
<ul>
<li>
Expand All @@ -193,39 +184,28 @@ <h3>Additional Techniques (Advisory) for Name, Role, Value</h3>
<h3>Failures for Name, Role, Value</h3>
<ul>
<li>
<a href="../Techniques/failures/F59" class="failure">Failure due to using script to make div or span a user interface control in HTML</a>
<a href="../Techniques/failures/F59" class="failure"></a>
</li>
<li>
<a href="../Techniques/failures/F15" class="failure">Failure due to implementing custom controls that do not use an accessibility API</a>
<a href="../Techniques/failures/F15" class="failure"></a>
</li>
<li>
<a href="../Techniques/failures/F20" class="failure">Failure due to not updating text alternatives when changes to non-text content occur</a>
<a href="../Techniques/failures/F20" class="failure"></a>
</li>
<li>
<a href="../Techniques/failures/F42" class="failure">Failure of Success Criterion 1.3.1 and 2.1.1 due to using scripting events to emulate
links
</a>
<a href="../Techniques/failures/F42" class="failure"></a>
</li>
<li>
<a href="../Techniques/failures/F68" class="failure">Failure of 1.3.1 and 4.1.2 due to the association of label and user interface controls
not being programmatically determinable
</a>
<a href="../Techniques/failures/F68" class="failure"></a>
</li>
<li>
<a href="../Techniques/failures/F79" class="failure">Failure of Success Criterion 4.1.2 due to the focus state of a user interface component
not being programmatically determinable or no notification of change of focus state
available
</a>
<a href="../Techniques/failures/F79" class="failure"></a>
</li>
<li>
<a href="../Techniques/failures/F86" class="failure">Failure of Success Criterion 4.1.2 due to not providing names for each part of a multi-part
form field, such as a US telephone number
</a>
<a href="../Techniques/failures/F86" class="failure"></a>
</li>
<li>
<a href="../Techniques/failures/F89" class="failure">Failure of 2.4.4 due to using null alt on an image where the image is the only content
in a link
</a>
<a href="../Techniques/failures/F89" class="failure"></a>
</li>
</ul>
</section>
Expand Down

0 comments on commit 633684e

Please sign in to comment.