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

Jump to bottom

Landmark Regions: Fix labeling requirement issue #453 #687

Merged
merged 2 commits into from
Jun 15, 2018
Merged

Landmark Regions: Fix labeling requirement issue #453 #687

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
14441c7
Fix for #453
jnurthen May 21, 2018
d8b9b4e
Revision to explain when it is OK to duplicate labels
mcking65 Jun 15, 2018
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
7 changes: 6 additions & 1 deletion aria-practices.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2903,7 +2903,12 @@ <h3>General Principles of Landmark Design</h3>
<p><strong>Step 3: Label areas</strong></p>

<ul>
<li>If a specific landmark role is used more than once on a web page, it should have a unique label.</li>
<li>
If a specific landmark role is used more than once on a page, provide each instance of that landmark with a unique label.
There is one rare circumstance where providing the same label to multiple instances of a landmark can be beneficial: the content and purpose of each instance is identical.
For example, a large search results table has two sets of identical pagination controls -- one above and one below the table, so each set is in a navigation region labeled <q>Search Results</q>.
In this case, adding extra information to the label that distinguishes the two instances may be more distracting than helpful.
</li>

<li>If a landmark is only used once on the page it may not require a label. See Landmark Roles section below. </li>

Expand Down