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 <[email protected]> To: James Teh <[email protected]> Cc: IAccessible2 mailing list <[email protected]> Date: 12/01/2010 08:29 AM Subject: Re: [Accessibility-ia2] Object Attributes spec needs work Sent by: [email protected] 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 >> 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. > There are exceptions but in general, I would rather enhance API than create multiple accessible objects for a single widget. I'm interested to hear what others think. I think it is important to discuss this, especially before ARIA.next design begins. Cheers, David _______________________________________________ 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
