On 1/12/2010 2:51 AM, David Bolter wrote:
More and more I see a need for accessibility solutions to rely less on
roles. We see some pretty interesting UI on the web, and the kinds of
assumptions that could historically be made on the desktop, can no
longer be made. I think we need to be able
James,
We are going to need a more flexible way of supporting custom components
for the Web. Properties and states need to be discoverable and processable
- and so do custom roles. I think roles will end up becoming identifiers
for common design patterns. This will part of the work in ARIA 2.0.
On 01/12/10 5:18 AM, James Teh wrote:
On 1/12/2010 2:51 AM, David Bolter wrote:
More and more I see a need for accessibility solutions to rely less on
roles. We see some pretty interesting UI on the web, and the kinds of
assumptions that could historically be made on the desktop, can no
We also need to start collecting new common design patterns on the Web and
ensure we are moving in the right direction on the infrastructure.
Rich Schwerdtfeger
CTO Accessibility Software Group
From: David Bolter david.bol...@gmail.com
To: James Teh ja...@nvaccess.org
Cc:
...this state is necessary in those cases where an object has a role which is
not one of the previously mentioned roles but does have the behavior of
having two states...
I'd lax the two state conditions, since there are things like 3state check
boxes, which one could think of as
