RE: [aria impl] platform mappings, and role vs state for "undefined"

Specific to the example for checkable state:
I understand what you mean by undefined and state="" but wonder if it is
really necessary.
An element like a checkbox can have one of two Boolean states and one of
them can be a default for the element. So if the checkbox element is created
and exposed, it should  be created with the default state. Else the element
should not be created / 
Exposed. If the element can have more than two valid values as per the
application  logic, then perhaps it should not be defined as a checkbox. 
Sailesh Panchang
Accessibility Services Manager (Web and Software)
Deque Systems Inc. (
11130 Sunrise Valley Drive, Suite #140,
Reston VA 20191
Phone: 703-225-0380 (ext 105)
-----Original Message-----
From: [] On Behalf
Of David Bolter
Sent: Monday, January 12, 2009 9:21 AM
Subject: [aria impl] platform mappings, and role vs state

Hi All,

This is a browser implementation topic.

What about adding a section to  about conflict resolution
between role and state for platform a11y mapping? This, in addition to
inlining specific heuristics where necessary.

For example consider the checkable state (which is different from checked).
<span role="checkbox" aria-checked="undefined">

Now remember, "undefined is special" as it tells us treat the attribute
as missing or "". The role tells us that the object is checkable, and
the aria-checked="undefined" would normally indicate the object is not
checkable.  I think a good general rule is to give the role more mapping
power and to expose the checkbox with a checkable state. What do others
think? These are somewhat unusual cases (strange aria markup really), so
I don't want to make a huge deal about it.


Received on Monday, 12 January 2009 14:51:24 UTC