Conversation
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
patrickhlauke
approved these changes
Aug 17, 2025
adampage
approved these changes
Sep 19, 2025
Co-authored-by: Adam Page <adam@adampage.net>
bruce-usab
approved these changes
Sep 19, 2025
Contributor
bruce-usab
left a comment
There was a problem hiding this comment.
Discussed in TF call, 9/19/2025.
brianelton
reviewed
Oct 3, 2025
bruce-usab
approved these changes
Oct 3, 2025
scottaohara
reviewed
Oct 3, 2025
| <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> | ||
| <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> |
Member
There was a problem hiding this comment.
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?
scottaohara
approved these changes
Oct 3, 2025
Member
scottaohara
left a comment
There was a problem hiding this comment.
just one question to take or leave. otherwise, lgtm
mbgower
reviewed
Oct 10, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes: #919
Updated ARIA11 to standardize internal wording and ensure definitions are consistent with ARIA standards
(it also removes "links links" repetition)
Deploy preview and diff of Technique ARIA11: Using ARIA landmarks to identify regions of a page