ISSUE-541: Text Alt Comp too specific to ARIA attributes (aria-valuetext and aria-valuenow)
Text Alt Comp too specific to ARIA attributes (aria-valuetext and aria-valuenow)
- State:
- CLOSED
- Product:
- ARIA 1.1 Core Mapping Specification
- Raised by:
- James Craig
- Opened on:
- 2012-11-08
- Description:
- http://www.w3.org/WAI/PF/aria/complete#tac_embed_range
This section of the name computation is too limiting to aria-specific attrs, such that it does not accurately cover native elements like <input type="range" value="5">.
If the embedded control is a range (e.g., a spinbutton or slider), use the value of the aria-valuetext attribute if available, or otherwise the value of the aria-valuenow attribute.
It should probably say this instead:
If the embedded control is a range (e.g., a spinbutton or slider), use the text value if defined (e.g. aria-valuetext), or otherwise the value of the control (e.g., aria-valuenow, or host language value attribute). - Related Actions Items:
- No related actions
- Related emails:
- No related emails
Related notes:
I agree.
Also, with the new approach where the TAC has a core section, plus native host langauge sections, the lingo, "...or host language value attribute", can be used in the core.
Actually, the new separate doc already uses this language. Likely part of my attempts to "neutralize" the algorithm
Joseph Scheuhammer, 6 Oct 2014, 17:14:00Closing.
Joseph Scheuhammer, 19 Jul 2016, 19:47:58Display change log
