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.

Joseph Scheuhammer, 6 Oct 2014, 14:24:44

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:00

Closing.

Joseph Scheuhammer, 19 Jul 2016, 19:47:58

Changelog:

Created issue 'Text Alt Comp too specific to ARIA attributes (aria-valuetext and aria-valuenow)' nickname owned by James Craig on product ARIA 1.1, description '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).' non-public

James Craig, 8 Nov 2012, 20:31:06

Description changed to '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).'

James Craig, 8 Nov 2012, 20:56:58

Product changed to ARIA 1.1 Implementation Guide

James Craig, 6 Oct 2014, 17:40:36

Status changed to 'open'

James Craig, 6 Oct 2014, 17:40:36

Status changed to 'closed'

Joseph Scheuhammer, 19 Jul 2016, 19:48:11


Joanmarie Diggs <jdiggs@igalia.com>, James Nurthen <nurthen@adobe.com>, Chairs, Michael Cooper <cooper@w3.org>, Ruoxi Ran <ran@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $