Skip to content

Updated ARIA11 to standardize internal wording and ensure definitions are consistent with ARIA standards #4534

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

Merged
mbgower merged 9 commits into from
Oct 17, 2025
Merged

Updated ARIA11 to standardize internal wording and ensure definitions are consistent with ARIA standards #4534

Changes from 2 commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
16ae784
aligned definitions with ARIA ones
giacomo-petri Aug 11, 2025
acb6c11
Merge branch 'main' into giacomo-petri-aria11-align-with-aria-specs
patrickhlauke Aug 17, 2025
5ec03a5
Merge branch 'main' into giacomo-petri-aria11-align-with-aria-specs
patrickhlauke Sep 5, 2025
93ccf67
Update techniques/aria/ARIA11.html
mbgower Sep 19, 2025
57710fa
Update techniques/aria/ARIA11.html
patrickhlauke Oct 3, 2025
3e0db7c
Merge branch 'main' into giacomo-petri-aria11-align-with-aria-specs
patrickhlauke Oct 3, 2025
3c8a9aa
Update techniques/aria/ARIA11.html
mbgower Oct 10, 2025
05b9788
Remove class from inline code tags
kfranqueiro Oct 10, 2025
667bae3
Merge branch 'main' into giacomo-petri-aria11-align-with-aria-specs
mbgower Oct 17, 2025
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
14 changes: 7 additions & 7 deletions techniques/aria/ARIA11.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,13 +22,13 @@ <h1>Using ARIA landmarks to identify regions of a page</h1>
</p>
<p>Landmarks are inserted into the page using the role attribute on an element that marks the section. The value of the attribute is the name of the landmark. These role values are listed below. For HTML mappings of landmark roles, refer to the <cite>Rules of ARIA attribute usage by HTML element</cite> table in the <a href="https://www.w3.org/TR/html-aria/">ARIA In HTML recommendation</a>.</p>
<ul>
<li><code class="language-html">banner</code>: A region that contains the prime heading or internal title of a page.</li>
<li><code class="language-html">navigation</code>: A region that contains navigation links links to other pages or different parts of the same page.</li>
<li><code class="language-html">main</code>: A region that contains a page's main content.</li>
<li><code class="language-html">region</code>: A region that contains a perceivable section of the page containing content that is sufficiently important for users to be able to navigate to the section. A <code class="language-html">region</code> landmark isn't exposed as a landmark region unless it has an accessible name.</li>
<li><code class="language-html">form</code>: A region of the document that represents a collection of form-associated elements, some of which can represent editable values that can be submitted to a server for processing.</li>
<li><code class="language-html">search</code>: A region of the page containing search functionality.</li>
<li><code class="language-html">complementary</code>: Any section of the document that supports the main content, yet is separate and meaningful on its own.</li>
<li><code class="language-html">banner</code>: A region that contains mostly site-oriented content, rather than page-specific content.</li>
<li><code class="language-html">navigation</code>: A region that contains a collection of navigational elements (usually links) for navigating the document or related documents.</li>
<li><code class="language-html">main</code>: A region that contains the main content of a document.</li>
<li><code class="language-html">region</code>: A region that contains a perceivable section of the page containing content that is relevant to a specific, author-specified purpose and sufficiently important that users will likely want to be able to navigate to the section easily A <code class="language-html">region</code> landmark isn't exposed as a landmark region unless it has an accessible name.</li>
Comment thread
patrickhlauke marked this conversation as resolved.
Outdated
<li><code class="language-html">form</code>: A region that represents a collection of form-associated elements, some of which can represent editable values that can be submitted to a server for processing.</li>
Copy link
Copy Markdown
Member

@scottaohara scottaohara Oct 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it also worth mentioning that a form is also not meant to be exposed as a landmark unless it is given a name - since this is like region and it that was called out for that role?

Comment thread
mbgower marked this conversation as resolved.
Outdated
<li><code class="language-html">search</code>: A region that contains a collection of items and objects that, as a whole, combine to create a search facility.</li>
Comment thread
mbgower marked this conversation as resolved.
Outdated
<li><code class="language-html">complementary</code>: A region that supports the main content, yet is separate and meaningful on its own.</li>
<li><code class="language-html">contentinfo</code>: A region that contains information about the parent document such as copyrights and links to privacy statements.</li>
</ul>

Expand Down