#screenreaders (29 links)
- Aural UI of HTML elements thepaciellogroup.github.io
How HTML elements are supported by screen readers Typical support patterns of HTML elements by screen readers: Identification of an element by role as the user…
- NVDA – a free, open source screen reader | 456 Berea Street 456bereastreet.com
Hadn't come across this one.
Good analysis of the recent WebAIM screen reader survey. Use <Hn> tags, think hard about accesskeys, use skip links, know your audience.
- WebAIM: Screen Reader Survey Results webaim.org
In December 2008 through January 2009, WebAIM conducted a survey of preferences of screen reader users. We received 1121 valid responses to the screen reader survey, which was conducted Dec. 2008 - Jan. 2009. The response was amazing.
"Some tips on how to configure your development environment for screen reader testing." Although getting a dev to play with a screenreader can lead to a false sense of security; no substitute for proper testing.
- Stop using Ajax! - Opera Developer Community dev.opera.com
Or, at least, think more carefully about when and how you use it.
- WebAnywhere - A screen reader on the go webinsight.cs.washington.edu
A web-based screen reader. It requires no special software to be installed on the client machine and, therefore, enables blind people to access the web from any computer they happen to have access to that has a sound card.
VoiceOver, the screen reader for Apple’s OS X, has undergone a major update. This article looks at the new functions, and what that means for people browsing websites.
Now that I have an Intel-based Mac with Parallels and Boot Camp for running Windows, I have found the perfect screen reader testing system.
- Fire Vox: A Screen Reading Extension for Firefox firevox.clcworld.net
An open source, freely available talking browser extension for the Firefox web browser. Think of it as a screen reader that is designed especially for Firefox.
- f berriman / blog fberriman.com
Last Monday I had the opportunity to visit the Test Partners, after an invite by Steve Green, to attend an afternoon of screen reader demonstration. I’m exceptionally glad I went
- Juicy Studio: Improving Ajax applications for JAWS users juicystudio.com
" Popular screen readers use a virtual buffer to allow users to interact with web content. This article uncovers undocumented behaviour in JAWS 7.1 and later, which allows web developers to build Ajax applications that update the virtual buffer without a
- Juicy Studio: Using the title Attribute juicystudio.com
Current user agents provide very poor access to title text information, and what access they do provide is typically inaccessible for people with disabilities.
- Juicy Studio: Making Ajax Work with Screen Readers juicystudio.com
The accessibility community is understandably concerned about the accessibility of client-side scripting, in particular using Asynchronous JavaScript and XML (Ajax) to produce Rich Internet Applications.
Ajax accessibility. I knew nothing about it, so I ran some user tests and presented original research.
"For all of the excitement and hype, still very little has been said on the subject of AJAX and accessibility.
"Although many of us web professionals just 'kinda know' that AJAX is bad for web accessibility, when pushed many would not be able to say exactly why or how certain screen readers cope with content that's been changed using AJAX (or using DOM Scripting m
- JAWS for Windows 7.10 Public Beta freedomscientific.com
The seven easy tips below will drastically improve a site's usability for screen reader users, as well as all other visitors.
One of the prime reasons for going to @media was to learn more from recognised experts in the field, and yet I came away confused and disillusioned.
Readspeaker makes websites talk. It is easy to use and easy to implement. No backend reprogramming required and no plugins or software needed for the visitor.
- PhpLondonWiki : RnibVisit2005March3 phplondon.org
Lynn Holdsworth, our RNIB web savvy demonstrator, [demolished] several well known sites like amazon.co.uk (which no one really liked anyway) and google.com (which nearly everyone liked a lot).
- Guidelines for Accessible and Usable Web Sites: Observing Users Who Work With Screen Readers redish.net · Archived on
Conducting usability testing with people with disabilities, specifically blind and lowvision users