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. I would appreciate your contribution to the effort.
We also need a way for the user to specify preferred types of content. What is needed for a cognitively impaired user may be entirely different from someone who is blind. Rich Rich Schwerdtfeger CTO Accessibility Software Group From: James Teh <[email protected]> To: IAccessible2 mailing list <[email protected]> Date: 12/01/2010 04:19 AM Subject: Re: [Accessibility-ia2] Object Attributes spec needs work Sent by: [email protected] 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 to describe UI more flexibly, > ideally to be able to describe anything that innovators concoct. This might be partially true, but it's also an excuse for bad design. Far too often, these situations would be better served by creating multiple related objects. For example, I'm not really sure i agree with the idea of checkable table cells. These could just as well be treated as a checkbox within a table cell. Jamie -- James Teh Vice President NV Access Inc, ABN 61773362390 Email: [email protected] Web site: http://www.nvaccess.org/ _______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
<<inline: graycol.gif>>
_______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
