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.

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

[accname] Do “AriaLabel” substep before “Embedded Control” substep #2377

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

sideshowbarker
Copy link

This change reorders the “AriaLabel” substep in the set of steps in the accname Computation algorithm such that it occurs before the “Embedded Control” substep, rather than after that step.

Otherwise, without this change, the spec as written doesn’t match the behavior as implemented in existing UAs, nor the corresponding requirements at https://w3c.github.io/html-aam/#accname-computation in the HTML-AAM spec:

If the [embedded-control] element has an aria-label or an aria-labelledby attribute the accessible name is to be calculated using the algorithm defined in Accessible Name and Description: Computation and API Mappings.

(Which is the first step in accname computation for each control)

Also, without this change, the spec doesn’t match the expectations in http://wpt.fyi/results/accname/name/comp_label.html for the “input with label for association is superceded by aria-label” subtest.

Test, Documentation and Implementation tracking

Once this PR has been reviewed and has consensus from the working group, tests should be written and issues should be opened on browsers. Add N/A and check when not applicable.

  • "author MUST" tests: N/A
  • "user agent MUST" tests: https://wpt.fyi/results/accname/name/comp_label.html
  • Browser implementations: WebKit, Gecko, and Blink all implement the AriaLabel-computation-step-before-Embedded-Control-computation-step behavior in this patch.
  • Does this need AT implementations? No
  • Related APG Issue/PR: N/A
  • MDN Issue/PR: N/A

This change reorders the “AriaLabel” substep in the set of steps in the
accname Computation algorithm such that it occurs before the “Embedded
Control” substep, rather than after that step.

Otherwise, without this change, the spec as written doesn’t match the
behavior as implemented in existing UAs, nor the corresponding
requirements at https://w3c.github.io/html-aam/#accname-computation in
the HTML-AAM spec:

> If the [embedded-control] element has an aria-label or an
> aria-labelledby attribute the accessible name is to be calculated
> using the algorithm defined in Accessible Name and Description:
> Computation and API Mappings.

(Which is the first step in accname computation for each control)

Also, without this change, the spec doesn’t match the expectations in
http://wpt.fyi/results/accname/name/comp_label.html for the “input with
label for association is superceded by aria-label” subtest.
Copy link

netlify bot commented Nov 18, 2024

Deploy Preview for wai-aria ready!

Name Link
🔨 Latest commit ee133dd
🔍 Latest deploy log https://app.netlify.com/sites/wai-aria/deploys/673aca9b5bf1c1000853e8c6
😎 Deploy Preview https://deploy-preview-2377--wai-aria.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

@spectranaut spectranaut assigned accdc and MelSumner and unassigned accdc Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants