W3C home > Mailing lists > Public > wai-xtech@w3.org > April 2012

ARIA impl guide is not clear about aria-checked

From: Alexander Surkov <surkov.alexander@gmail.com>
Date: Wed, 4 Apr 2012 17:47:04 +0900
Message-ID: <CA+epNsfw2ZmjM5+m64LL14pzAP_sxj-BwCMNvK67irsaHOSpEQ@mail.gmail.com>
To: wai-xtech@w3.org

5.5.1. State and Property Mapping Table
aria-checked="false" (state) Expose object attribute checkable:true
aria-checked is undefined (state)	Not mapped

6.2. Author Errors

If a WAI-ARIA property contains an unknown or disallowed value, the
user agent SHOULD expose to platform accessibility APIs as follows:
    1) When exposing as an object attribute, expose the unknown value
 do not vet it against possible values.
    2) When exposing as a platform API Boolean state, treat "",
"undefined" or no attribute present as false. Treat any other value as
    3) Otherwise, ignore the value and treat the property as not present

Technically aria-checked is exposed as "checkable" object attribute on
IA2 and ATK what requires UA to expose unknown value per 1) (bw, it's
not clear what is unknown value because a property can contain
"unknown or disallowed value"). Role mapping requires the
role="checkbox" to be exposed with "checkable:true" attribute (per
5.4.1. Role Mapping Table) so we run into collision if
aria-checked="wrongvalue" is specified.

It sounds that "checkable:true" should be treated as API Boolean
state. So true value is "checkable:true", false value is no
"checkable" attribute. I think the wording should be changed to make
it clear.

Received on Wednesday, 4 April 2012 08:47:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:51:45 UTC