Update ARIA11

[JAWS-test2]

Fixes #919

Also:

• Update and addition of links
• Remove role=application (no landmark region)
• Adding role=region
• Adding the test for meaningful labeling

[netlify]

✅ Deploy Preview for wcag2 ready!

Name	Link
🔨 Latest commit	5e345bd
🔍 Latest deploy log	https://app.netlify.com/projects/wcag2/deploys/687eb5328d0b67000804dc33
😎 Deploy Preview	https://deploy-preview-1023--wcag2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[kfranqueiro]

I synced this branch today while looking through old PRs, which required resolving conflicts:

• In the list of landmarks, I only kept the banner change (which concerns the referenced bug); application had since been removed, navigation had since been changed to something similar to what was in this PR, and region had since been added. I did correct one duplicated word in the navigation item.
• The modification of one line of the first example was no longer applicable as the example had changed
• Preserved the addition to the test prodecure, although I wonder if items 3 and 4 could be merged?
• Preserved the additions under related techniques
• Preserved the changes to the first 3 resource links; the 4th is already pointing to a newer URL for what was added in this PR, and the 5th was added after this PR

See df64f09e for what was in the original commit of this PR.

[bruce-usab]

Discussed on backlog call 5/16. We did not resolve if "each landmark region" was equivalent to "same type of landmark".

[mbgower]

In step 3 we talk about accessible name. In step 4 we talk about "labelled meaningfully".
Should we try to make the language more consistent?

The procedure is a little atypical in its construction. We could try to make it more usual, but it's not crucial

[mbgower]

Suggested change

	<li>If the same type of landmark appears multiple times on the page, check that each one is labelled meaningfully.</li>
	<li>If the same type of landmark appears multiple times on the page, check that each one is given a unique and meaningful accessible name.</li>

[mbgower]

There seems to be a bit of friction between how "name" is used in this document. There is also inconsistency with how "label" and "accessible name" are used. I am making some suggestions to try to improve.

[mbgower]

Suggested change

<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>

<p>Landmarks are inserted into the page using the role attribute on an element that marks the section. The value of the attribute designates the type of 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>

[mbgower]

Suggested change

<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">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, often provided using <code class="language-html">aria-label</code> or <code class="language-html">aria-labelledby</code>.</li>

[mbgower]

Note that I meant to put this in as a suggestion, so flagging that it is commited. If there is agreement with the change, it can stand.

[mbgower]

@mbgower to copy over phrase

[mbgower]

As per TF discussion, repeating the same final sentence as in regions, which was also stated as valid for forms. However, @giacomo-petri, looking at https://www.w3.org/TR/wai-aria-1.2/#form it seems like there must be a label? Is the following actually true?

Suggested change

	<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">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. A <code class="language-html">form</code> landmark isn't exposed as a landmark region unless it has an accessible name.</li></li>

[giacomo-petri]

A few notes:

According to ARIA specifications, both the region and form roles require an accessible name provided by the author:

• https://www.w3.org/TR/wai-aria-1.2/#region
• https://www.w3.org/TR/wai-aria-1.2/#form

This requirement remains in ARIA 1.3 as well:

• https://www.w3.org/TR/wai-aria-1.3/#region
• https://www.w3.org/TR/wai-aria-1.3/#form

However, with the proposed change in this PR w3c/aria#2297, the form role may no longer require an accessible name in the future.

That said, according to the Core AAM (https://w3c.github.io/core-aam/#role-map-form-nameless), a form element without an accessible name will not be exposed as a landmark.

[giacomo-petri]

We also need to update lines 49 and 51 in Example 1, as they are not handled as landmarks (missing acc name), even though the title suggests otherwise.