FLUID-3671 Screen reader a11y and usability issues with Progress (esp. lack of feedback for screen reader users)

Jonathan Hung jhung at ocad.ca
Tue Sep 28 20:25:14 UTC 2010


Hi Golam,

I'm trying to understand the use case for these two modes aside from the
fact that ValueNow helps overcome a bug in NVDA.

Why would a implementor want to use valuenow over valuetext? What benefits
does it yield?

I'm trying to get an understanding so I can incorporate these two modes of
progress into the new demo.

- Jonathan.

---
Jonathan Hung / jhung at ocad.ca <jhung.utoronto at gmail.com>
IDRC - Interaction Designer / Researcher
Fax: (416) 977-9844



On Mon, Sep 27, 2010 at 4:28 PM, Chowdhury, Golam <gchowdhury at ocad.ca>wrote:

> Hi Everyone,
>
> We have address the issue for FLUID-3671 and the latest version is
> available in the trunk. Fluid Progress component now provides the option to
> the integrator to switch between aria-valuenow and aria-valuetext. By
> setting the ariaBusyText to empty string will default to aria-valuenow and
> if ariaBusyText is set to some string then aria-valuetext will be enable. I
> have included some of the tests for the new feature and please note that we
> have found some issues with our progress demo page which we are in process
> of fixing.
>
> Thanks,
>
> Golam Chowdhury
> gchowdhury at ocad.ca | 416-977-6000 ext. 3962
> Software Developer
> Inclusive Design Research Centre (IDRC)
> OCAD University
> ________________________________________
> From: Chowdhury, Golam
> Sent: Friday, September 24, 2010 12:58 PM
> To: colinbdclark at gmail.com; Justin Obara
> Cc: fluid-work at fluidproject.org
> Subject: FLUID-3671  Screen reader a11y and usability issues with Progress
> (esp. lack of feedback for screen reader users)
>
> Hi Everyone,
>
> Issues with Screen Reader:
> Current progress bar does not announce the progress bar status when using
> NVDA2010 screen reader using Fire Fox 3.5.9 and 3.6.9.
> http://issues.fluidproject.org/browse/FLUID-3671
>
> Summery of our conversation in regards to finding solution for progress
> issue:
> 1. We provide a configuration option for users(implementers) to be able to
> customize the content of the aria-valuetext for the Progress component.
> 2. If an implementor doesn't provide anything for valuetext such as empty
> string, we fall back to using aria-valuenow. The idea here is that we let
> implementers choose what experience is best for their application.
>
> Detail of our conversation:
> http://wiki.fluidproject.org/display/fluid/fluid-work+IRC+Logs-2010-09-24
>
> Please let us know your thoughts?
>
> Thanks,
>
> Golam Chowdhury
> gchowdhury at ocad.ca | 416-977-6000 ext. 3962
> Software Developer
> Inclusive Design Research Centre (IDRC)
> OCAD University
>
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://fluidproject.org/mailman/listinfo/fluid-work
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20100928/fc1ffadd/attachment.html>


More information about the fluid-work mailing list