Skip to content

Commit

Permalink
Name and Description Guidance Section: fix capitalization typo (pull #…
Browse files Browse the repository at this point in the history
…1292)

Co-authored-by: Matt King <a11yThinker@Gmail.com>
  • Loading branch information
smhigley and mcking65 committed Jan 23, 2020
1 parent d75c28b commit c59168a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion aria-practices.html
Original file line number Diff line number Diff line change
Expand Up @@ -3786,7 +3786,7 @@ <h3>What ARE Accessible Names and Descriptions?</h3>
Authors supply a description when there is a need to associate additional information with an element, such as instructions or format requirements for an input field.
</p>
<p>
assistive technologies present names differently from descriptions.
Assistive technologies present names differently from descriptions.
For instance, screen readers typically announce the name and role of an element first, e.g., a button named <q>Mute Conversation</q>could be spoken as <q>Mute Conversation button</q>.
If an element has a state, it could be announced either before or after the name and role; after name and role is the typical default.
For example, a switch button named <q>Mute Conversation</q> in the <q>off</q> state could be announced as <q>Mute Conversation switch button off</q>.
Expand Down

0 comments on commit c59168a

Please sign in to comment.