Keyboard accessibility: changing tab order
colinbdclark at gmail.com
Wed Jan 27 20:08:56 UTC 2010
Yes, I completely agree that focus should follow the visual flow of the page. It can be so confusing for everyone when the tab order bounces around the page incomprehensibly.
As for the target platform for Decapod: the command line image processing routines at the heart of Decapod are built and tested on Linux. For a local client/server installation, we'll assume Linux with a modern, capable browser. That probably means Firefox, but as with everything Fluidic, we're trying to support a good range of A-grade browsers.
Thanks again for your feedback on all of this, it's super-invaluable. Keep it up!
On 2010-01-27, at 2:39 PM, E.J. Zufelt wrote:
> One thing to note here, which may not be relevant, is that it is important, as much as it is possible, to make sure that focus follows the visual flow of the page. This reduces the burden of finding the focused item that can sometimes be placed on keyboard only users.
> On a somewhat related note, what platform (OS / browser) will the Decapod UI be running on, and has / will the UI be tested with assistive technology available for that platform?
Technical Lead, Fluid Project
More information about the fluid-work