On 2/12/2010 12:26 AM, David Bolter wrote: >>> More and more I see a need for accessibility solutions to rely less on >>> roles. >> 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.
> There are exceptions but in general, I would rather enhance API than > create multiple accessible objects for a single widget. If we allow this, we'll end up with checkable selectable editable text list item menu button table cells. How on earth is a user supposed to know how to interact with such things? The difficulty of identifying such compound controls aside, keyboard and mouse interaction patterns start to collide. The core problem here is what defines a "single widget". 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
