On 2010-02-24, at 4:56 PM, Sambhavi Chandrashekar wrote:
Hi Everett,
Are there any issues not covered in the list below?
Sam
On Wed, Feb 24, 2010 at 4:49 PM, Sambhavi Chandrashekar <[email protected]
> wrote:
Hi James,
Here is a list of design considerations for future versions of
Engage Mobile. This is based on feedback from recent QA testing with
VoiceOver.
http://wiki.fluidproject.org/display/fluid/Accessibility+considerations+for+design+(for+0.3)
* I took a quick look at the list on the page. The only consideration
that I noticed was missing is that users must be given an opportunity
to adjust the timing or pause events like animations, transitions, or
page redirects. For page redirects this would only be if the user
didn't explicitly request the new page. I.e. once an artifact number
is entered on the Object Code page the user is redirected to the
artifact page, even though they did not request this. Addin the
status message will help this (and is covered in the list), but the
timing may still be to short for some users to make the required
adjustment to the object code before they are redirected.
HTH,
Everett
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
