WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Visually indicating accessibility error as a screen reader user

for

From: Tony Olivero
Date: Mar 27, 2013 11:35AM

Birkir,

I know the reports we often get from sighted testers have screenshots
with annotations.

One possibility, and I'm admittedly just throwing this out it is
untested, if you can use the browser's javascript console to somehow
add the callout to the page then it would be uncluded in a screenshot.
You'd have to figure out a way to do this, but maybe adding a layer on
a positive Z access with a style rule, changing the background to a
pronounced color, and making the text a number? You'd have to either
prepend or append this to the element in question. That way you could
use the same number in your report to call out the error visually.

Just my immediate thoughts. I've wondered about this from time to time
myself though so perhaps we can find a solution.

Tony

On 3/27/13, Birkir R. Gunnarsson < <EMAIL REMOVED> > wrote:
> Good morning, yea clan of the webwise.
>
> I was working on an accessibility audit last night (yes, it happens,
> occasionally, may be more than I'd like to admit).
> I found myself writing 2 or 3 sentences describing the location of a
> link that did not have keyboard support (well, a div to be
> semantically correct).
> Of course I had to describe it from a screen reader perspective, i.e.
> part of this list with these other objects/links, I could not visually
> describe or indicate it, as I do not know where or how it appears on
> the screen visually without sighted assistance, as far as I know,
> which sometimes is not very far.
> It made me wonder what sighted testers do in this situation and if
> there is a tool or method that could replicate this for the
> zero-sighted.
> Do you take a screen shot indicating problematic areas, either by
> color or label (I create case numbers in a spreadsheet and it would be
> ideal to be able to add those to a screenshot).
> Is there another/better way to do this?
> Is there a screen reader accessible best practice in this scenario?
>
> We certainly do have to improvize sometimes. One of these days it
> would be fun to try and start a website with tips, tricks,
> accessibility evaluation of tools and other info for blind web
> accessibility testers, but that's a whole other can of worms, when I
> have a little bit more time to spare. :)
> Cheers
> -B
> > > >