E-mail List Archives
Thread: how to create accessibility test cases?
Number of posts in this thread: 2 (In chronological order)
From: Shrirang Sahasrabudhe
Date: Tue, Jul 18 2006 10:40PM
Subject: how to create accessibility test cases?
No previous message | Next message →
Hi,
I have created a small web application and now would like to test it for accessibility.
Normally for functional testing I create test cases according to functionality of the app.
But in case of accessibility how should the test cases be?
Any pointers would be appreciated
Thanks
Shri
wi with your guidance so far
Jon Gunderson < = EMAIL ADDRESS REMOVED = > wrote: I would recommend using CSS aboslute positioning and position
the label off screen. Screen readers are more more honoring
"display: none" and "visibility: hiddeen" so this may cause
problems in the future or with other screen readers.
Suggested markup:
...
This will render the label off screen, but it still
technically visible, even though a graphical browser rendering
will not render it.
Jon
---- Original message ----
>Date: Thu, 13 Jul 2006 21:21:31 -0700 (PDT)
>From: Shrirang Sahasrabudhe
>Subject: [WebAIM] want to know/understand the impact due to
usage of hidden labels.
>To: = EMAIL ADDRESS REMOVED =
>
>Hi,
> I have created a form with a specific layout..
> every form field is put inside a table having 1 row and 3
columns.
> The first column contains the label,
> the second column contains ‘*’ in case of mandatory fields
> and the last column contains the input box…
> the label is appropriately associated with the input box
using ‘for’ attribute..
> as the ‘*’ is not the part of text on the label it is not
read by JAWS..
> in order to fix the problem; I used a hidden label and
placed it in the first column; the text on the hidden label
includes ‘*’ wherever appropriate.
> This solution is working..
> I would like to know whether this technique is fine or has
any side effects?
>
>
>
>
> user name*
>
> user name
> *
> [input]
>
>
>
> password
> < div id="password0" style="width: 0px; height: 0px;
visibility: hidden">
> password*
>
>
> *
> [input]
>
>
> thanks
>
>
>
>***********************************************************
>If you try, you risk failure. If you don't, you ensure
it....I try.
>Shrirang Sahasrabudhe,
>Pune, India.
>Phone: 0091-020-4227558.
>
>---------------------------------
>Yahoo! Music Unlimited - Access over 1 million songs.Try it
free.
>
>
>
Jon Gunderson, Ph.D.
Director of IT Accessibility Services
Campus Information Technologies and Educational Services (CITES)
and
Coordinator of Assistive Communication and Information Technology
Disability Resources and Education Services (DRES)
Voice: (217) 244-5870
Fax: (217) 333-0248
Cell: (217) 714-6313
E-mail: = EMAIL ADDRESS REMOVED =
WWW: http://cita.rehab.uiuc.edu/
WWW: https://netfiles.uiuc.edu/jongund/www/
***********************************************************
If you try, you risk failure. If you don't, you ensure it....I try.
Shrirang Sahasrabudhe,
Pune, India.
Phone: 0091-020-4227558.
---------------------------------
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail Beta.
From: Moore, Michael
Date: Wed, Jul 19 2006 8:00AM
Subject: RE: how to create accessibility test cases?
← Previous message | No next message
In addition to running through the general accessibility checklists, 508 and/or WCAG, I recommend developing use/case scenarios and testing those through all of the platforms where the application is intended to run. This should include using a variety of assistive technologies. For internal applications here at DARS we have a closed set of assistive technologies that are standard throughout the agency, but for external applications things get a bit trickier. Typical platforms should include screen readers, screen magnifiers (the issues are different with the two), keyboard only operation without a screen reader, and speech to text interfaces.
Mike