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

Update: account for common labeledby spelling variant for aria-labell… #2371

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

Update: account for common labeledby spelling variant for aria-labell… #2371

Changes from 3 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
3209da7
Update: account for common labeledby spelling variant for aria-labell…
scottaohara Nov 8, 2024
4ed8c8a
Update index.html
scottaohara Nov 17, 2024
5220d74
remove extra word from the prior sentence wording
scottaohara Nov 17, 2024
cadad47
Update index.html
scottaohara Dec 19, 2024
7c638f7
Update index.html
scottaohara Dec 19, 2024
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
3 changes: 2 additions & 1 deletion index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11821,7 +11821,8 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
<p>If the interface is such that it is not possible to have a visible label on the screen, authors SHOULD use <pref>aria-label</pref> and SHOULD NOT use <pref>aria-labelledby</pref>. Authors MUST NOT specify <code>aria-labelledby</code> on an element which has an explicit or implicit WAI-ARIA role where <code>aria-labelledby</code> is <a href="#prohibitedattributes">prohibited</a>. As required by the <a href="#textalternativecomputation">accessible name and description computation</a>, user agents give precedence to <pref>aria-labelledby</pref> over <pref>aria-label</pref> when computing the accessible name property.</p>
<p>The <pref>aria-labelledby</pref> attribute is similar to <pref>aria-describedby</pref> in that both reference other elements to calculate a text alternative (an accessible name, and description, respectively). While a concise accessible name is preferable, a description can either be concise, or provide more verbose information.</p>
<!-- keep previous sentence synced with the associated description in #aria-describedby -->
<p class="note">The expected spelling of this property in <abbr title="United States">U.S.</abbr> English is "labeledby." However, the <a>accessibility <abbr title="Application Programing Interfaces">API</abbr></a> features to which this property is mapped have established the "labelledby" spelling. This property is spelled that way to match the convention and minimize the difficulty for developers.</p>
<p class="note">The expected spelling of this property in <abbr title="United States">U.S.</abbr> English is "labeled by." However, the <a>accessibility <abbr title="Application Programing Interfaces">API</abbr></a> feature this property was originally based on had established the <abbr title="United Kingdom">U.K.</abbr> English spelling, "labelled by."</p>
<p>To mitigate against common author use of the "labeledby" misspelling, thus ensuring more content will be properly named, user agents MUST support the canonical "aria-labelledby" and the alternate "aria-labeledby" spelling. Authors MUST NOT use both spelling variants of the attribute on the same element. For instances where an author has used both spelling variants on the same element, user agents MUST use the canonical <code>aria-labelledby</code> spelling and ignore the alternate spelling of the attribute.</p>
scottaohara marked this conversation as resolved.
Show resolved Hide resolved
</div>
<table class="property-features">
<caption>Characteristics:</caption>
Expand Down
Loading