Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Name and Description Guidance Section: Fix capitalization typo #1292

Merged
merged 2 commits into from
Jan 23, 2020
Merged

Name and Description Guidance Section: Fix capitalization typo #1292

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e169058
fix capitalization typo
smhigley Dec 26, 2019
3620b98
Merge branch 'master' into 1289-typo
mcking65 Jan 23, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion aria-practices.html
View file
Open in desktop
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