E-mail List Archives
Thread: How to test for web accessibility as a visually impaired
Number of posts in this thread: 5 (In chronological order)
From: Rakesh Chowdary Paladugula
Date: Wed, Feb 04 2009 2:40AM
Subject: How to test for web accessibility as a visually impaired
No previous message | Next message →
Respected list members,
I am a visually impaired working as a web accessibility tester in a
company. I am using jaws and doing my work.
I am testing by exploring myself. The tool I am using for automated
testing is eval access. When I speak about mannual testing I am
checking weather a handicapped can use the website without any
difficulty.
To know more about the procedure of testing and generating reports of
testing I want experts help.
I hope beloved members will help in this regard.
--
Thanks & regards
Rakesh Paladugula
Web accessibility tester & advisor.
Iridiuminteractive software solutions PVT LTD
Mobile: 09966346422
Website: rakeshpaladugula.blog.co.in
skype:prakesh369
From: smithj7@peoplepc.com
Date: Wed, Feb 04 2009 6:00AM
Subject: Re: How to test for web accessibility as a visually impaired
← Previous message | Next message →
Hi Rakesh. I work for blind services. First, to address your question with a question. Are you looking for some automated evalution tools? I like FAE and my co-worker likes WAVE, we both also have browers with accessiblity checkers. this page has a nice list http://www.w3.org/WAI/ER/tools/
Next, I have a question for you, if you don't mind. Do you work with a sighted person initially when testing web pages. I work for blind services we discovered that some items on a page that have no focuss (works only with mouse) has been ignored by both JAWS and at least two software evaluation tools. Basically it was passed. Because blind services knows this happens we often have a sighted person and blind person go over the page initially together. Also, I've learned items like flash often do this kind of thing and when I ask a blind person to check the page I'll tell them how menu visual elements of such items are and if they are functional (e.g. flash advert with 3 hyperlink to pages.)
----- Original Message -----
From: Rakesh Chowdary Paladugula
To: = EMAIL ADDRESS REMOVED =
Sent: Wednesday, February 04, 2009 4:36 AM
Subject: [WebAIM] How to test for web accessibility as a visually impaired
Respected list members,
I am a visually impaired working as a web accessibility tester in a
company. I am using jaws and doing my work.
I am testing by exploring myself. The tool I am using for automated
testing is eval access. When I speak about mannual testing I am
checking weather a handicapped can use the website without any
difficulty.
To know more about the procedure of testing and generating reports of
testing I want experts help.
I hope beloved members will help in this regard.
--
Thanks & regards
Rakesh Paladugula
Web accessibility tester & advisor.
Iridiuminteractive software solutions PVT LTD
Mobile: 09966346422
Website: rakeshpaladugula.blog.co.in
skype:prakesh369
From: Rakesh Chowdary Paladugula
Date: Thu, Feb 05 2009 3:05AM
Subject: Re: How to test for web accessibility as a visually impaired
← Previous message | Next message →
Dear Smith,
Yes, initially I used to take the help of a sited to look weather
there is any flash content in the web page. But I recognised that my
vision is enough to check weather there is any flash in the web page
or not.
The URL provided by you is very helpful.
--
Thanks & regards
Rakesh Paladugula
Web accessibility tester & advisor.
Iridiuminteractive software solutions PVT LTD
Mobile: 09966346422
Website: rakeshpaladugula.blog.co.in
skype:prakesh369
From: Janna Cameron
Date: Thu, Feb 05 2009 7:05AM
Subject: Re: How to test for web accessibility as a visually impaired
← Previous message | Next message →
Rakesh,
If haven't done this already, I would suggest that you compile a list of
specific tasks that can be accomplished with the software. This will ensure
that you focus on the core features of the software. For this type of
testing, you could record the following
* Whether you were able or not able to accomplish each task. Record
details about what you tried for tasks you were unable to complete.
* Time it took to accomplish each task. I'd add a subjective
judgement about whether this time was acceptable or not.
* Number of steps it took to complete tasks. This is pretty
time-consuming, I'd just do this for things that took too many steps.
Janna
-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Rakesh Chowdary
Paladugula
Sent: Wednesday, February 04, 2009 4:37 AM
To: = EMAIL ADDRESS REMOVED =
Subject: [WebAIM] How to test for web accessibility as a visually impaired
Respected list members,
I am a visually impaired working as a web accessibility tester in a
company. I am using jaws and doing my work.
I am testing by exploring myself. The tool I am using for automated
testing is eval access. When I speak about mannual testing I am
checking weather a handicapped can use the website without any
difficulty.
To know more about the procedure of testing and generating reports of
testing I want experts help.
I hope beloved members will help in this regard.
--
Thanks & regards
Rakesh Paladugula
Web accessibility tester & advisor.
Iridiuminteractive software solutions PVT LTD
Mobile: 09966346422
Website: rakeshpaladugula.blog.co.in
skype:prakesh369
From: Cliff Tyllick
Date: Thu, Feb 05 2009 1:10PM
Subject: Re: How to test for web accessibility as a visuallyimpaired
← Previous message | No next message
Rakesh, in case this helps, I will add to a couple of points that Janna made.
Her first point was to record whether you were able or not able to accomplish each task. I find it helpful when the person testing the software doesn't know exactly what "accomplishing the task" means. So it's helpful to me to hear not only whether the tester thinks they succeeded but also what they think success is. For example, assume that the "task" is to get a license, and that to do that you must submit a form and pay a fee. If the Web page or software leads you to believe that you are done before you have paid the fee, I would need to know that. So "Task accomplished: submitted license application form" would be different from "Task accomplished: submitted license application form and paid application fee" would be two different results.
Then for the time it took to accomplish each task, Janna suggested that you add a subjective judgement about whether this time was acceptable or not. It's especially important to note whether the task (or any one step) took so long that you would have quit if you weren't focused on testing the whole process. To me, deciding that you have to make a phone call for help is a form of quitting.
Finally, whenever you are confused by the software you are testing, it is also helpful to note what you were expecting to find. For a silly example, imagine that after you finish filling out a form, you find three buttons labeled "Red," "Yellow," and "Blue." If that confuses you because you expect to find buttons labeled "Save," "Clear," and "Submit," then it would help me to know not only that you got stuck, but also what you were expecting to find and would have chosen had you found it.
The bottom line is to remember that you cannot fail. If you grow confused, the Web page or application has failed, and its designers need to know that.
Good luck!
Cliff Tyllick
Web development coordinator
Agency Communications Division
Texas Commission on Environmental Quality
512-239-4516
= EMAIL ADDRESS REMOVED =
>>> "Janna Cameron" < = EMAIL ADDRESS REMOVED = > 2/5/2009 8:02 AM >>>
Rakesh,
If haven't done this already, I would suggest that you compile a list of
specific tasks that can be accomplished with the software. This will ensure
that you focus on the core features of the software. For this type of
testing, you could record the following
* Whether you were able or not able to accomplish each task. Record
details about what you tried for tasks you were unable to complete.
* Time it took to accomplish each task. I'd add a subjective
judgement about whether this time was acceptable or not.
* Number of steps it took to complete tasks. This is pretty
time-consuming, I'd just do this for things that took too many steps.
Janna
-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Rakesh Chowdary
Paladugula
Sent: Wednesday, February 04, 2009 4:37 AM
To: = EMAIL ADDRESS REMOVED =
Subject: [WebAIM] How to test for web accessibility as a visually impaired
Respected list members,
I am a visually impaired working as a web accessibility tester in a
company. I am using jaws and doing my work.
I am testing by exploring myself. The tool I am using for automated
testing is eval access. When I speak about mannual testing I am
checking weather a handicapped can use the website without any
difficulty.
To know more about the procedure of testing and generating reports of
testing I want experts help.
I hope beloved members will help in this regard.
--
Thanks & regards
Rakesh Paladugula
Web accessibility tester & advisor.
Iridiuminteractive software solutions PVT LTD
Mobile: 09966346422
Website: rakeshpaladugula.blog.co.in
skype:prakesh369