E-mail List Archives
Re: screenreader feature comparison?
From: Hoffman, Allen
Date: Oct 29, 2010 4:09PM
- Next message: Birkir Rúnar Gunnarsson: "Re: screenreader feature comparison?"
- Previous message: Cliff Tyllick: "Re: HTML5 and new elements (was Re: Use of SAMP to highlight search results)"
- Next message in Thread: Birkir Rúnar Gunnarsson: "Re: screenreader feature comparison?"
- Previous message in Thread: Katherine Mancuso: "screenreader feature comparison?"
- View all messages in this Thread
Code to a standard, not a screen reader.
If you were comparing screen reader features like you describe you'd end
up with screen reader, version, feature. Its not that there are so
aweful many screen readers, JAWS, Windows eyes, HAL, NVDA, thunder,
cobra, Apple voiceOver, about covers it, but then you throw in versions,
JAWS 4-12, Windows eyes 5-7, HAL ??, NVDA ?? Where does it end. I
think it's a much worse proposition than browser compatability testing
is, and that is hassle enough. Then do you test browser compat and
screen reader combos?
-----Original Message-----
From: Katherine Mancuso [mailto: <EMAIL REMOVED> ]
Sent: Thursday, October 28, 2010 6:11 PM
To: <EMAIL REMOVED>
Subject: [WebAIM] screenreader feature comparison?
Anyone have a source that compares how various screenreaders interpret
pages, or screenreader features, or something like that? I need a
little
more evidence to back up the assertion "no, don't just buy JAWS and test
with it, also test with at least one other screenreader" for my
coworkers.
I thought that for sure this would be an easy google find, but it isn't.
Thanks,
Katherine
- Next message: Birkir Rúnar Gunnarsson: "Re: screenreader feature comparison?"
- Previous message: Cliff Tyllick: "Re: HTML5 and new elements (was Re: Use of SAMP to highlight search results)"
- Next message in Thread: Birkir Rúnar Gunnarsson: "Re: screenreader feature comparison?"
- Previous message in Thread: Katherine Mancuso: "screenreader feature comparison?"
- View all messages in this Thread