On Tuesday 11 March 2008 10:56:02 Connor, Adam wrote: > Do you wireframe two versions of the screens (one for users with > javascript enabled and one for those without)? What about storyboards?
If there are major differences between the accessible version, we will create a new wireframe. If it is just a single element, we might just add a callout or footnote with just a mockup of the element which is different. > What other accessibility related concerns/issues/items do you find > impacting your workflow, deliverables, etc, and how do you handle them? The company I work for does a big mix of industry and government related work. For those who work in the government sector, you're probably already aware of the requirements for 508, and that enforcement is becoming stricter. Accessibility is often a goal for our industry clients, but only on a small scale and not on a system-wide level. On a recent project, we had issues creating a simple multi-threaded survey for a government client. A lot of the simple validation and notification techniques we had used for industry clients weren't accessible because of Javascript or what not, and we had to do server-side validation instead. It wasn't a simple conversion between "do this with Javascript" versus "do the same thing on the server", and we had to rethink workflows and how error messages appear on the page because of things like the screen repainting on reload and resetting the window position. -- Celeste 'seele' Paul www.obso1337.org ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
