E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 7 (In chronological order)

From: Mohith BP
Date: Sun, Apr 23 2017 9:48AM
Subject: Tips on totally blind testing for the low vision accessibility
No previous message | Next message →

Hi Team,

I would like to know the methodologies totally blind accessibility
auditors follow to test the low vision criterias.
As there are number of tools for color contrast, I mainly would like
to know how do you tackle:
1. Keyboard focus indicator.
2. Zoom (200%) does not break the visibility of the content.
3. High contrast does not break particular elements.

I usually get these test cases tested by my sighted counter parts.


Thanks & Regards,
Mohith B. P.

From: JP Jamous
Date: Sun, Apr 23 2017 10:42AM
Subject: Re: Tips on totally blind testing for the low visionaccessibility
← Previous message | Next message →

Keep doing it this way for the best experience possible. No other tools can detect those better than the human eye.

In fact, you might get some information from automated tools but not enough to cover them all. Plus, those are for sighted people to test. They are the experts on them just like we are the experts on blind matters.

From: Ryan E. Benson
Date: Sun, Apr 23 2017 10:53AM
Subject: Re: Tips on totally blind testing for the low vision accessibility
← Previous message | Next message →

For the keyboard focus indicator, you should know that all browsers have
some sort of indicator built in, which is usually an 1 pixel black dotted
outline. A person who is blind could skim through the CSS to see if
anything is removing that rule, though I know it wouldn't be a fun task.

Ryan E. Benson

On Apr 23, 2017 11:48, "Mohith BP" < = EMAIL ADDRESS REMOVED = > wrote:

Hi Team,

I would like to know the methodologies totally blind accessibility
auditors follow to test the low vision criterias.
As there are number of tools for color contrast, I mainly would like
to know how do you tackle:
1. Keyboard focus indicator.
2. Zoom (200%) does not break the visibility of the content.
3. High contrast does not break particular elements.

I usually get these test cases tested by my sighted counter parts.


Thanks & Regards,
Mohith B. P.

From: Jim Homme
Date: Mon, May 01 2017 8:57AM
Subject: Re: Tips on totally blind testing for the low visionaccessibility
← Previous message | Next message →

Hi,
This would not cover dynamic style changes.

Thanks.

Jim


=========Jim Homme,
Team Lead and Accessibility Consultant,
Bender HighTest Accessibility Team
Bender Consulting Services, Inc.,
412-787-8567,
= EMAIL ADDRESS REMOVED =
http://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions
E+R=O

From: Guy Hickling
Date: Tue, May 02 2017 12:25PM
Subject: Re: Tips on totally blind testing for the low visionaccessibility
← Previous message | Next message →

This is something I have been thinking about these last two or three weeks
because I am training up a blind consultant. We are currently going through
various common accessibility issues to work out which ones he can report on
his own and which ones he can't.

In answer to the original question, yes, many visual issues have to be left
to sighted people. The most obvious one is probably colour contrast, which
can only be tested by a sighted person and is very fiddly as well.

But there are others where a sighted person could test, perhaps under his
instruction, and briefly tell him what is wrong, then he takes notes and
can provide the proper comments and recommendations in his audit report.

We are dividing the issues up into three categories:

- screen reader issues he can report solely on his own
- ones that must be left for a sighted colleague
- and a third category in between where he can report them with
assistance from an assistant who is computer literate, but not one
necessarily versed in accessibility.

The third category comes about because he is based in the UK where (and I
don't know if there is an equivalent in the States) he can get social
funding for a paid support worker for a certain amount of hours each week.
It is ideal work, of course, for a computer programming student or similar
wanting the extra cash, though it isn't always possible to find someone
like that. But some people in a similar position may be able to get help
from family members or such.

Quite soon we are going to be considering image alt texts. A sighted person
could tell him what images a page has, where they are, and whether they are
decorative or not. He can then listen to the alt texts, if any, in his
screen reader and report them appropriately. We are also experimenting with
browser debugging tools to see how easily he can get round them (they have
rather complex interfaces).
It's early days in this journey at the moment, but it seems to be working
out well for him.

Regards,
Guy Hickling
Accessibility Consultant
http://www.enigmaticweb.com

From: Tim Harshbarger
Date: Tue, May 02 2017 2:28PM
Subject: Re: Tips on totally blind testing for the lowvision accessibility
← Previous message | Next message →

When possible, I try to use this as an opportunity. I am totally blind. I have also worked with colleagues who are blind.

Sometimes, I use my need for sighted assistance as a way to help train other people on accessibility. I might ask them a series of questions about a design diagram or walk them through how to test for color contrast. I get the help I need and the other person ends up more knowledgeable.

AT one point, I use to print out copies of the designs and I would take those copies (along with highlighter pens) to meetings with the project team. I would hand out the highlighters and the copies. I would have them walk through the design and interactions and have them use pen, pencil, and highlighters to mark up the designs. For example, I would walk them through finding and marking the headings on the page along with a heading level. I might have them outline or highlight sections where they could use landmarks. I think that ended up being quite educational for the project teams when we could do that.

I just mention it as an example of possibly how to turn a potential problem into an advantage--in case it might be useful.

From: Mohith BP
Date: Tue, May 02 2017 10:10PM
Subject: Re: Tips on totally blind testing for the low vision accessibility
← Previous message | No next message

Hi All,

Thank you for the response. I usually follow the methodology suggested
by Guy Hickling. Most of the times I usually worked directly with
design, development and content team.

Thanks & Regards,
Mohith B. P.

On 5/3/17, Tim Harshbarger < = EMAIL ADDRESS REMOVED = > wrote:
> When possible, I try to use this as an opportunity. I am totally blind. I
> have also worked with colleagues who are blind.
>
> Sometimes, I use my need for sighted assistance as a way to help train other
> people on accessibility. I might ask them a series of questions about a
> design diagram or walk them through how to test for color contrast. I get
> the help I need and the other person ends up more knowledgeable.
>
> AT one point, I use to print out copies of the designs and I would take
> those copies (along with highlighter pens) to meetings with the project
> team. I would hand out the highlighters and the copies. I would have them
> walk through the design and interactions and have them use pen, pencil, and
> highlighters to mark up the designs. For example, I would walk them through
> finding and marking the headings on the page along with a heading level. I
> might have them outline or highlight sections where they could use
> landmarks. I think that ended up being quite educational for the project
> teams when we could do that.
>
> I just mention it as an example of possibly how to turn a potential problem
> into an advantage--in case it might be useful.
>
>