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
Copy file name to clipboardExpand all lines: aria-practices.html
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -318,8 +318,8 @@ <h3>Button</h3>
318
318
To tell assistive technologies that a button is a toggle button, specify a value for the attribute <ahref="#aria-pressed" class="state-reference">aria-pressed</a>.
319
319
For example, a button labeled mute in an audio player could indicate that sound is muted by setting the pressed state true.
320
320
<strong>Important:</strong> it is critical the label on a toggle does not change when its state changes.
321
-
In this example, when the pressed state is true, the label remains “Mute” so a screen reader would say something like “Mute toggle button pressed”.
322
-
Alternatively, if the design were to call for the button label to change from “Mute” to “Unmute,” the aria-pressed attribute would not be needed.
321
+
In this example, when the pressed state is true, the label remains "Mute" so a screen reader would say something like "Mute toggle button pressed".
322
+
Alternatively, if the design were to call for the button label to change from "Mute" to "Unmute," the aria-pressed attribute would not be needed.
323
323
</li>
324
324
<li>Menu button: as described in the <ahref="#menubutton">menu button pattern</a>, a button is revealed to assistive technologies as a menu button if it has the property <ahref="#aria-haspopup" class="property-reference">aria-haspopup</a> set to <code>true</code>.</li>
0 commit comments