Accessibility considerations for design (for Engage 0.3)
Sambhavi Chandrashekar
sambhavic at gmail.com
Thu Feb 25 00:16:10 UTC 2010
Hi Everett,
> 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.
I have added the above to the list.
For any user, the current design does not give an opportunity to rectify an
error made in entering the second digit of the object code. Even as they are
'tsk-tsk'ing, the artifact page opens with the artifact corresponding to the
unintended number.
A solution could be to have an extra 'GO' step where the user explicitly
invokes the artifact screen after verifying the number. I am not sure how
this will affect the intended aesthetics of the process.
Sam
On Wed, Feb 24, 2010 at 5:06 PM, E.J. Zufelt <everett at zufelt.ca> wrote:
> 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 <
> sambhavic at gmail.com> 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)<http://wiki.fluidproject.org/display/fluid/Accessibility+considerations+for+design+%28for+0.3%29>
>>
>> * 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20100224/a52549bb/attachment.html>
More information about the fluid-work
mailing list