Screen Reader Tester?

Is there a screen reader website that can test to see if a website is screen reader friendly?

Got Chrome? This one will open your eyes ears. :ear:

ChromeVox

1 Like

Depends on what you mean by screen? A mobile screen is completely different than an iPad screen, and an iPad screen is completely different from a laptop screen, and a laptop screen is completely different than a desktop screen.

You see where I’m going with this…

So what screen size are you testing for?

Google has good tools, and since Google is pretty much the authority on everything, you know their feedback is trustworthy.

Here’s their tool for mobile: Google Mobile-Friendly Tester

@webdev32 the OP is referring to a screen reader, not a screen.

It would kinda be nice if there were, like, a pool of professional testers you could submit your page/snippet/site/app to for testing. So far as I know, there isn’t.

Testing your page with SR’s requires… testing your page with SR’s. Like browser testing used to be back when it was very likely a few browsers would completely puke on your CSS (esp, but not limited to, IE).

Unlike testing in browsers, testing in SR’s kinda requires the tester to be familiar with them, and know what they should do vs what’s a bug (and then whether the bug is from the browser or from the SR).

I would suggest you do a few things:

Whatever platform you have, there’s a screen reader for it (although honestly even though I’m a Linux person, I don’t use the Gnome-Orca screen reader as my screen-reader testing SR). For Windows, NVDA is a major screen reader (after JAWS) and unlike JAWS, is free. Unlike JAWS (who works best with IE), NVDA works best with Firefox. I think because Firefox is open sourced.

On any OSX or iOS, you’ve got VoiceOver built in. If you have a Mac or iThing, go find it and turn it on and play with it. Learn how it works. Unlike the two big Windows screen readers, VoiceOver doesn’t create a virtual buffer that you the user interacts with. It’s pretty direct with the page.

There’s TalkBack for Android but all I hear is that it’s still crap. But they’re working on it.

Finally, I’d recommend:

  • Writing to web standards and WCAG standards (this will mean most or all of your site will JustWork in screen readers (and lots of other Access Technology!) even if you don’t test in them)
  • Check out Tenon.io. Like SauceLabs or BrowserStack, it’s sort of a Testing-As-A-Service thing. You can try out a free version I think (where you’re limited to like 50 calls to the service), otherwise it’s like less than 20 dollars a month. You send either code snippets or a URL to the Tenon service, it runs a bunch of tests, sends you results back.

Tenon is automatic testing only. Automatic testing is very limited, but will catch stupid stuff: it can alert you that you didn’t add an alt attribute. However it cannot tell you if your alt text makes sense to any human beings anywhere. That’s where you need to do your own testing.

3 Likes

That’s some information, Stomme_poes. Information I’ll likely be researching on my own, since I have a site that will require some screen reader friendliness.

Thank you!

I said earlier:
“It would kinda be nice if there were, like, a pool of professional testers you could submit your page/snippet/site/app to for testing. So far as I know, there isn’t.”

There is something now: http://www.access-works.knowbility.org/index.php

This is a working-together of Knowability.org and remote-user-testing-service Loop11.

3 Likes

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.