[Contrib: Evaluation System] ADA compliance and EVALSYS

[Silverio, Gonzalo]

Something like this.

	http://www.umich.edu/~gsilver/evalsys-work/screen-read-lickert

Click on link "Show as screen reader would read" to see. This would be very easy to implement. 

Some caveats:

1) Newer versions of JAWS would be required.
2) Most of EVALSYS radio groupings rely on the superimposition of a "real" group over a "fake" group. Not sure why this is, but this would need to be addressed as well. The fake one needs to be made invisible to screen readers.
3) An actual screen reader user would need to be consulted. I would hire the grad student Ellen mentions in a flash.

I will not have time to work on this but would gladly assist a bit if needed.

	-Gonzalo

On Aug 24, 2010, at 7:34 AM, gsilver at umich.edu wrote:

> In that case we would need some text for those labels. I was thinking something along these lines:
> 
> Before each radio group a screen reader message that says: "Choose an option where 0 is (left label) and n is (right label)" and then adding screen reader labels 1 through n.
> 
> If your school has screen reader users  who would be interested in testing I would urge you to have them do so for love or money. Even with the WC3 WCAG by heart and the best intentions there is no substitute to knowing how actual screen reader users actually interact with the web app. 
> 
> 
>        - Gonzalo
> 
> ------------------------------
> 
> On Aug 24, 2010, at 6:06 AM, Adam Marshall <adam.marshall at oucs.ox.ac.uk> wrote:
> 
>> 
>> 
>> | -----Original Message-----
>> | From: evaluation-bounces at collab.sakaiproject.org [mailto:evaluation-
>> | bounces at collab.sakaiproject.org] On Behalf Of Silverio, Gonzalo
>> | Sent: 23 August 2010 16:41
>> | To: Ellen Yu Borkowski
>> | Cc: evaluation at collab.sakaiproject.org
>> | Subject: Re: [Contrib: Evaluation System] ADA compliance and EVALSYS
>> | 
>> | Hi Ellen.
>> | 
>> | I did a fairly extensive accessibility check of EVALSYS three years ago
>> | and checked the major user facing screens again this year. Without more
>> | details it would be hard to know what is going on here. Important
>> | information would consist of:
>> | 
>> | 1) JAWS version
>> | 2) EVALSYS version
>> | 3) Specific element types that the user had problems with
>> | 
>> | Quite a bit of the work I did on EVALSYS-635, EVALSYS-426, EVALSYS-425,
>> | etc. involved rearranging the elements so that labels and inputs were
>> | consonant. In order to do this with some of the elements I had to
>> | resort to scripting, which would need a newer version of JAWS to work.
>> | 
>> | Some elements do not have labels - or if they do have a label, no text
>> | inside of it. This is by design (Lickert-like scales, for example just
>> | have a left and right label). Other elements like grouped elements did
>> | not not have explicit labels till I re-instrumented them recently. In
>> | any case - more information is needed, I would gladly take a look.
>> 
>> Maybe the lickhert scales should have hidden labels (class="skip") for accessibility purposes.
>> 
>> adam