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

output element is a labelable element #225

Closed
scottaohara opened this issue Jul 22, 2019 · 3 comments · Fixed by #402
Closed

output element is a labelable element #225

scottaohara opened this issue Jul 22, 2019 · 3 comments · Fixed by #402
Assignees
Labels
accName & Desc Related to accessible name or description

Comments

@scottaohara
Copy link
Member

scottaohara commented Jul 22, 2019

The output element is a labelable element and as such, its naming algorithm should be updated to indicate this.

Presently the algorithm is:

  1. aria-label and aria-labelledby
  2. subtree
  3. title
  4. no name

Should be updated to:

  1. aria-label and aria-labelledby
  2. name from label element
  3. title
  4. no name

edit: subtree shouldn't be considered for name. name AND subtree need to be announced by the output live region and should not just announce name.

@dd8
Copy link

dd8 commented Aug 12, 2019

Some other elements are defined as 'labelable elements' by the HTML Standard but the label isn't used in the accessible name calculation:
https://html.spec.whatwg.org/multipage/forms.html#category-label

button
https://w3c.github.io/html-aam/#button-element-accessible-name-computation

input type="button" , input type="submit" and input type="reset"
https://w3c.github.io/html-aam/#input-type-button-input-type-submit-and-input-type-reset

meter
progress
no name calculation - these don't seem to fall into any of the general categories since they're not form-associated elements and aren't text level elements (e.g. you can use a progress bar to indicate progress without a form, and use a meter in to display data like current temperature)

select
It's not mentioned explicitly so it falls into https://w3c.github.io/html-aam/#other-form-elements (so only allows a single label)

and form-associated custom elements

@scottaohara
Copy link
Member Author

scottaohara commented Aug 12, 2019

yes, thank you. all of these are being covered in my pending update.

@scottaohara
Copy link
Member Author

anything not output related will be covered in other issues. such as: #210 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accName & Desc Related to accessible name or description
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants