-
Notifications
You must be signed in to change notification settings - Fork 266
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
2.5.3 - control with label but no accname (understanding note + new f…
…ailure technique) (#2057) Also cleans-up 2.5.3 understanding document markup/structure - adds new F111 Control with visible label text but no accname (improperly numbered F109 initially) - add failure technique in Understanding document - added notes in Understanding about UI components with visible text and no name failing both 4.1.2 and 2.5.3 - removed direct reference to WCAG 2.1 - resolved discussion with ACT on where to report some of the failure examples Closes #2045 --------- Co-authored-by: Alastair Campbell Co-authored-by: Mike Gower Co-authored-by: Scott O'Hara Co-authored-by: Dan Bjorge
- Loading branch information
1 parent
a0215ed
commit 6fc9553
Showing
3 changed files
with
153 additions
and
59 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,83 @@ | ||
<!DOCTYPE html> | ||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en"> | ||
<head> | ||
<title>Failure of Success Criteria 1.3.1, 2.5.3, and 4.1.2 due to a control with visible label text but no accessible name</title> | ||
<link rel="stylesheet" type="text/css" href="../../css/editors.css"/> | ||
</head> | ||
<body> | ||
<h1>Failure of Success Criteria 1.3.1, 2.5.3, and 4.1.2 due to a control with visible label text but no accessible name</h1> | ||
<section id="meta"> | ||
<h2>Metadata</h2> | ||
<p id="id"></p> | ||
<p id="technology">general</p> | ||
<p id="type">failure</p> | ||
</section> | ||
|
||
<section id="applicability"> | ||
<h2>When to Use</h2> | ||
<p>All technologies that include interactive controls (such as links or form inputs).</p> | ||
</section> | ||
|
||
<section id="description"> | ||
<h2>Description</h2> | ||
<p>The objective of this Failure is to describe situations where speech input users cannot reliably speak the name of a control because although it has a visible label, it lacks an accessible name.</p> | ||
<p>When speech input users interact with a web page, they usually speak a command followed by the reference to some visible label (like the text in a button or a link, or the text labelling some input). If the control lacks an accessible name, speech users won't be able to activate the control using its visible label.</p> | ||
</section> | ||
|
||
<section id="examples"> | ||
<h2>Examples</h2> | ||
|
||
<section class="example"> | ||
<h3>A text input with a visible label, but without an accessible name</h3> | ||
<p>The text input is preceded by a visible text label "Enter name", but the text is not marked up as a <code><label></code> for the input, and there is no alternative way (e.g., <code>aria-label</code>) to provide the input with an accessible name at all.</p> | ||
<pre><code> | ||
<p>Enter name</p> | ||
<input type="text"> | ||
</code></pre> | ||
</section> | ||
|
||
<section class="example"> | ||
<h3>A text input with a visible label and aria-labelledby pointing to a non-existent id</h3> | ||
<p>The text input is preceded by a visible text label "Enter name". The text's container has an <code>id</code> of <code>nameEntry</code>, but the input has an <code>aria-labelledby</code> referencing a non-existent <code>name-entry</code> <code>id</code>. As a result, the input lacks an accessible name altogether.</p> | ||
<pre><code> | ||
<p id="nameEntry">Enter name</p> | ||
<input type="text" aria-labelledby="name-entry" > | ||
</code></pre> | ||
</section> | ||
</section> | ||
|
||
<section id="tests"> | ||
<h2>Tests</h2> | ||
<section class="test-procedure"> | ||
<h3>Procedure</h3> | ||
<p>For all controls with a visible label (e.g., link text, button text, programmatically linked label, images in links or buttons with text, etc.), check that:</p> | ||
<ol> | ||
<li>The control has a visible text label.</li> | ||
<li>The control has an accessible name.</li> | ||
<li>The accessible name contains the text that appears as the visible label.</li> | ||
</ol> | ||
</section> | ||
<section class="test-results"> | ||
<h3>Expected Results</h3> | ||
<ul> | ||
<li>If check #1 is false, the Success Criterion does not apply.</li> | ||
<li>If check #1 is true, but checks #2 and/or #3 are false, the content fails the Success Criterion.</li> | ||
<li>If all checks are true, the content passes the Success Criterion.</li> | ||
</ul> | ||
</section> | ||
</section> | ||
<section id="related"> | ||
<h2>Related Techniques</h2> | ||
<ul> | ||
<li><a href="../../techniques/general/F96">F96</a></li> | ||
<li><a href="../../techniques/general/G131">G131</a></li> | ||
<li><a href="../../techniques/aria/ARIA7">ARIA7</a></li> | ||
<li><a href="../../techniques/aria/ARIA8">ARIA8</a></li> | ||
<li><a href="../../techniques/aria/ARIA9">ARIA9</a></li> | ||
<li><a href="../../techniques/aria/ARIA14">ARIA14</a></li> | ||
<li><a href="../../techniques/aria/ARIA16">ARIA16</a></li> | ||
<li><a href="../../techniques/client-side-script/SCR30">SCR30</a></li> | ||
</ul> | ||
</section> | ||
</body> | ||
</html> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.