You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>The two labels, "Hated it" and "Loved it", are adjacent to the first and last radio buttons, and should be their accessible names. Speech-input users can speak either of these labels to select a radio button, and then use arrow navigation (e.g., "Press right arrow") to modify the selection. "Rate your response" is the text describing the whole widget and can be associated as the group label (here using <codeclass="language-html">legendcode>). The three middle radio buttons do not have visible labels. In the code example they are given title attributes of "Disliked", "So-so" and "Liked" in order to meet 3.3.2 Labels or Instructions.p>
Copy file name to clipboardExpand all lines: techniques/general/G56.html
+24-15Lines changed: 24 additions & 15 deletions
Original file line number
Diff line number
Diff line change
@@ -21,37 +21,46 @@
An announcer speaking over a riot scene
21
21
<h3>Sufficient audio contrast between a narrator and background musich3>
22
22
23
23
<p>This example demonstrates a voice with music in the background in which the voice is the appropriate 20 DB above the background. The voice (foreground) is recorded at -17.52 decibels (average RMS) and the music (background) is at -37.52 decibels, which makes the foreground 20 decibels louder than the background.p>
24
-
<h4>Audio exampleh4>
25
-
<pclass="working-example">
26
-
<ahref="../../working-examples/audio-contrast/good-contrast.mp3">Audio Example: Foreground is 20 decibels above the background (mp3)a>
27
-
p>
28
-
<h4>Transcript of audio example (good contrast)h4>
29
-
<p>"Usually the foreground refers to a voice that is speaking and should be understood. My speaking voice right now is 20 decibels above the background which is the music. This is an example of how it should be done.."p>
30
-
<h4>Visual example of the recording aboveh4>
31
-
<p>The audio example above is visually represented below in a snapshot of the file in an audio editor. A section is highlighted that contains foreground and background. It is a much larger wave than the section that contains only background.p>
32
-
<figureid="figure-visual-color-contrast">
33
-
<imgalt="A display showing a sound wave. The left third of the sound wave is just background noise, registering from -10 to +10 decibels. The remaining right-hand section is foreground and background noise showing a range from -50 to +40 decibels." src="img/Audio_3.jpg"/>
34
-
<figcaption>Visual representation of sufficient contrast.figcaption>
35
-
figure>
36
-
24
+
<section>
25
+
<h4>Audio exampleh4>
26
+
<pclass="working-example">
27
+
<ahref="../../working-examples/audio-contrast/good-contrast.mp3">Audio Example: Foreground is 20 decibels above the background (mp3)a>
28
+
p>
29
+
section>
30
+
<section>
31
+
<h4>Transcript of audio example (good contrast)h4>
32
+
<p>"Usually the foreground refers to a voice that is speaking and should be understood. My speaking voice right now is 20 decibels above the background which is the music. This is an example of how it should be done.."p>
33
+
section>
34
+
<section>
35
+
<h4>Visual example of the recording aboveh4>
36
+
<p>The audio example above is visually represented below in a snapshot of the file in an audio editor. A section is highlighted that contains foreground and background. It is a much larger wave than the section that contains only background.p>
37
+
<figureid="figure-visual-color-contrast">
38
+
<imgalt="A display showing a sound wave. The left third of the sound wave is just background noise, registering from -10 to +10 decibels. The remaining right-hand section is foreground and background noise showing a range from -50 to +40 decibels." src="img/Audio_3.jpg"/>
39
+
<figcaption>Visual representation of sufficient contrast.figcaption>
40
+
figure>
41
+
section>
37
42
section>
38
43
<sectionclass="example">
39
44
<h3>Insufficient Audio Contrast between a narrator and background musich3>
40
-
45
+
<section>
41
46
<h4>Audio example of the failureh4>
42
47
<p>This example demonstrates a voice with music in the background in which the voice is not 20 DB above the background. The voice (foreground) is at -18 decibels and the music (background) is at about -16 decibels making the foreground only 2 decibels louder than the background.p>
43
48
<pclass="working-example">
44
49
<ahref="../../working-examples/audio-contrast/bad-contrast.mp3">Audio Example: Foreground is less than 20 decibels above the background (mp3)a>
45
50
p>
51
+
section>
52
+
<section>
46
53
<h4>Transcript of audio example (bad contrast)h4>
47
54
<p>"This is an example of a voice that is not loud enough against the background. The voice which is the foreground is only about 2 decibels above the background. Therefore is difficult to understand for a person who is hard of hearing. It is hard to discern one word from the next. This is an example of what not to do."p>
55
+
section>
56
+
<section>
48
57
<h4>Visual example of the failureh4>
49
58
<p>The highlighted section contains foreground and background. The wave is almost the same size the section that contains only background, which means the background is too loud in comparison to the foreground voice.p>
<imgalt="A display showing a sound wave. A short section on the left is just background noise with a range of -35db to +35db. The main section of the wave has background and foreground noise, with a range of almost -70db to +70db. The final background-only section has a spike of a similar size." src="img/Audio_4.jpg"/>
52
61
<figcaption>Visual representation of bad contrast.figcaption>
Copy file name to clipboardExpand all lines: understanding/21/label-in-name.html
+14-15Lines changed: 14 additions & 15 deletions
Original file line number
Diff line number
Diff line change
@@ -50,26 +50,25 @@
Symbolic text characters
50
50
figure>
51
51
<p>Likewise, where an author has used a greater-than symbol (">") to mimic the appearance of the right-facing arrow, the text does not convey something in human language. It is a symbol, in this scenario likely meant to mimic the icons used for a "Play" button or a "Next" arrow.p>
52
52
section>
53
-
<h4>Punctuation and capitalizationh4>
54
53
55
54
<section>
56
-
<p>The use of punctuation and capitalization in labels <em>mayem> also be considered optional for the same reason. For example, the colon conventionally added at the end of input labels does not express something in human language, and capitals on the first letter of each word in a label do not normally alter the words' meaning. This is particularly relevant in the context of this SC, since it is primarily aimed at users of speech recognition; capitals and most punctuation are frequently ignored when a user speaks a label as a means of interacting with a control.p>
57
-
58
-
<p>While it is certainly not an error to include the colon and capitalization in the accessible name, a computed name of "First name" should not be considered a failure of "First Name:".<br/>
Likewise, "Next…" visibly shown on a button could have "Next" as the accessible name.<br/>
61
-
<inputtype="submit" value="Next..." />. When in doubt, where a meaningful visible label exists, match the string exactly for the accessible name.p>
55
+
<h4>Punctuation and capitalizationh4>
56
+
<p>The use of punctuation and capitalization in labels <em>mayem> also be considered optional for the same reason. For example, the colon conventionally added at the end of input labels does not express something in human language, and capitals on the first letter of each word in a label do not normally alter the words' meaning. This is particularly relevant in the context of this SC, since it is primarily aimed at users of speech recognition; capitals and most punctuation are frequently ignored when a user speaks a label as a means of interacting with a control.p>
62
57
58
+
<p>While it is certainly not an error to include the colon and capitalization in the accessible name, a computed name of "First name" should not be considered a failure of "First Name:".<br/>
Likewise, "Next…" visibly shown on a button could have "Next" as the accessible name.<br/>
61
+
<inputtype="submit" value="Next..." />. When in doubt, where a meaningful visible label exists, match the string exactly for the accessible name.p>
63
62
section>
64
63
65
-
<h4>Mathematical expressions and formulaeh4>
66
-
<section>
67
-
<p>Mathematical expressions are an exception to the previous subsection about symbolic characters. Math symbols can be used as labels; for example "11×3=33" and "A>B" convey meaning.<br/>
64
+
<section>
65
+
<h4>Mathematical expressions and formulaeh4>
66
+
<p>Mathematical expressions are an exception to the previous subsection about symbolic characters. Math symbols can be used as labels; for example "11×3=33" and "A>B" convey meaning.<br/>
<p>The label should not be overwritten in the accessible name, and substitutions of words where a formula is used should be avoided since there are multiple ways to express the same equation. For example, making the name "eleven multiplied by three is equivalent to thirty-three" might mean a user who said "eleven times three equals thirty-three" may not match. It is best to leave the formulas as used in the label and count on the user's familiarity with their speech software to achieve a match. Further, converting a mathematical formula label into an accessible name that is a spelled-out equivalent may create issues for translation. The name should match the label's formula text. Note that a consideration for authors is to use the proper symbol in the formula. For instance 11x3 (with a lower or upper case letter X), 11*3 (with the asterisk symbol), and 11×3 (with the <code>&code>times<code>;code> symbol) are all easy for sighted users to interpret as meaning the same formula, but may not all be matched to "11 times 3" by the speech recognition software. The proper operator symbol (in this case the times symbol) should be used.p>
<p>The label should not be overwritten in the accessible name, and substitutions of words where a formula is used should be avoided since there are multiple ways to express the same equation. For example, making the name "eleven multiplied by three is equivalent to thirty-three" might mean a user who said "eleven times three equals thirty-three" may not match. It is best to leave the formulas as used in the label and count on the user's familiarity with their speech software to achieve a match. Further, converting a mathematical formula label into an accessible name that is a spelled-out equivalent may create issues for translation. The name should match the label's formula text. Note that a consideration for authors is to use the proper symbol in the formula. For instance 11x3 (with a lower or upper case letter X), 11*3 (with the asterisk symbol), and 11×3 (with the <code>&code>times<code>;code> symbol) are all easy for sighted users to interpret as meaning the same formula, but may not all be matched to "11 times 3" by the speech recognition software. The proper operator symbol (in this case the times symbol) should be used.p>
73
72
section>
74
73
section>
75
74
<section>
@@ -89,7 +88,7 @@
Text in parentheses
89
88
<section>
90
89
<p>Note: The term "parenthetical" in this section is describing text that literally appears within a set of round brackets (). It is not used in the more abstract sense of "information related to".p>
91
90
<p>It is important to mention parenthetical text in labels in the context of accessible name versus description. In common usage, text in parentheses is considered secondary but relevant to meaning. Users of speech recognition would not typically announce text in parentheses as part of the input name. For that reason, parenthetical text may be optionally considered a description and left out of the accessible name.p>
92
-
<p>However, where parenthetical information provides important context, such as indication of a required field or limitations on what is allowed for input, this information must be provided programmatically in some other way to the user if that information is not included as part of the accessible name. For example, "Name (required)" and "Date (YYYY-MM-DD)" could accept "Name" and "Date" as the accessible names. However, in order to pass 1.3.1 Info & Relationships, authors would need to programmatically surface both the required state and the limit on the allowed data formatting (in this example, eight integers fitting the YYYY-MM-DD pattern). The "required" state could be surfaced through the HTML <code>requiredcode> attribute or by using <code>aria-required="true"code>. The allowed data formatting could be surfaced by being referenced using the <code>aria-describedbycode>) attribute.p>
91
+
<p>However, where parenthetical information provides important context, such as indication of a required field or limitations on what is allowed for input, this information must be provided programmatically in some other way to the user if that information is not included as part of the accessible name. For example, "Name (required)" and "Date (YYYY-MM-DD)" could accept "Name" and "Date" as the accessible names. However, in order to pass 1.3.1 Info & Relationships, authors would need to programmatically surface both the required state and the limit on the allowed data formatting (in this example, eight integers fitting the YYYY-MM-DD pattern). The "required" state could be surfaced through the HTML <code>requiredcode> attribute or by using <code>aria-required="true"code>. The allowed data formatting could be surfaced by being referenced using the <code>aria-describedbycode>) attribute.p>
0 commit comments