ISSUE-753: use X attribute if it was not used as the accessible name
use X attribute if it was not used as the accessible name
- State:
- CLOSED
- Product:
- ARIA 1.1 Name Computation
- Raised by:
- Cynthia Shelly
- Opened on:
- 2015-11-14
- Description:
- Issue with html-aam behavior
HTML-AAM has several places where it says to “use X attribute if it was not used as the accessible name.” Making that determination is quite hard. I understand the reasoning for it, but it really does not go well with the text alternative computation. Answering the question “what attribute will map to the name of node X” is not trivial.
Does the text alternative algorithm expect this kind of behavior too?
- Related Actions Items:
- No related actions
- Related emails:
- No related emails
Related notes:
This is covered in step. D of the ARIA name and description spec. where it refers to the host language definition of text alternatives. These alternatives are defined for each element in the HTML AAM. Hence it is very clear.
I have logged an issue whereby the HTML-AAM does not address use of the ARIA name and description spec. when an aria role is applied.
Here is the HTML AAM issue logged: https://github.com/w3c/html-aam/issues/100
Richard Schwerdtfeger, 10 Jul 2017, 17:04:06Given that:
- we refer to the host language spec. for text alternatives in step D and HTML's AAM is prescriptive as to what those text alternatives are.
- we have logged an issue against HTML AAM regarding the need to refer to the ARIA spec. in the case of ARIA roles being applied where there is no conflict
- It is up to HTML AAM to correct the ARIA role application for name and description
I am closing this issue.
Display change log
