- Assistive Technology Specialist at Southern New Hampshire University in Manchester, NH.
- Quality Assurance Tester – Section 508 Compliance in New York, NY.
- Sales Engineer for the Accessibility Management Platform at SSB Bart Group in Manchester, NH.
- Sr. Product Manager, Accessibility wanted at eBay in San Jose, CA.
- Web User Interface Analyst (direct hire) at Modis in Vienna VA.
- iOS developer at American Printing House for the Blind in Louisville, KY.
- Senior Technical Program Manager, Accessibility at Microsoft in Redmond, WA.
- Adaptive Technology Specialist at Riverside City College in Riverside CA.
- QA Accessibility Tester at Enterprise Solutions in Mountain View, CA.
- Web Accessibility Software Engineer at Apple in Santa Clara Valley, CA.
- Android Software Engineer – Mobile Accessibility at Twitter in San Francisco, CA. Can also contact @Sommer on Twitter!
Although accessibility checklists are important, testing for web accessibility requires more than that. Some testing requires tasks which can only be done by a human including testing with a screen reader. It’s best for a regular screen reader user to do the testing, but it’s also good for a developer or designer to do at least the basics (there was a big discussion on this last fall in Should Sighted Developers Use Screenreaders To Test Accessibility?).
Here are some good articles to help learn how to use a screen reader to test for web accessibility:
- Using NVDA to Evaluate Web Accessibility (WebAIM)
- Using JAWS to Evaluate Web Accessibility (WebAIM)
- Setting up a screen reader test environment (by Henny Swan)
- Easy Accessibility Testing with the NVDA Screen Reader (Yahoo)
- How to use NVDA and Firefox to test your web pages for accessibility (Marco Zehe)
- Establishing a screen reader test plan (by Henny Swan on spotlessinteractive.com)
- Testing with Screen Readers: Questions and Answers (WebAIM)
More from comments:
- Browser & Assistive Technology Tests Redux (The Paciello Group)
- Using VoiceOver to Evaluate Web Accessibility (WebAIM)
I came across the article A quick Web Accessibility Checklist (published last July) and have some feedback. Some points were great, but others needed some work. I was going to leave a comment, but thought the points would be good to share in a blog post.
- “Skip-to” links help, but wouldn’t put first on the list. Proper tag markup and ARIA are also big navigation helpers.
- Font resize widgets are unnecessary as they add weight to a site, add clutter to the screen, and the behavior should be done by the browser.
- A site map is not needed if navigation is done well and is accessible; the tip is more of a usability issue in my opinion.
- Don’t know what “links have descriptive screen text” means. If it means tool-tips (title attribute), then I highly recommend not doing most of the time.
- Yes, keyboard accessible dropdown menus are good, but remember that the whole site must be keyboard accessible.
- People still use frames? iFrames also relevant to list here, and more up-to-date.
- A good basic point missing is color; ensure sufficient color contrast, no content conveyed with color alone; etc.
Update, Jan 11:
I submitted a blog comment that linked to this page, and it did not yet get accepted.
Shortened URL to this page: http://weba.im/commquick
- Bonus! An offer to the HTML5 team to save longdesc by Vlad Alexander at XStandard
- Landmark Technology Access Bill Heads to President Obama’s Desk
- Accessibility testing tools (Steve Faulkner, The Paciello Group)
- Response to HTML5 editor on Canvas accessibility (by Rich Schwerdtfeger)
- Adobe’s Andrew Kirkpatrick interviewed on Accessibility in Government (video)
- Accessibility for web writers, part 1: Introduction
- Assistive Technologies for Online Learning
- Web Accessibility day course by RNIB in Edinburgh (Oct) & London (Nov)
- Should Sighted Developers Use Screenreaders To Test Accessibility? (great comments!)
- Using Accessible Twitter With JAWS Screen Reader
- HTML5 Canvas Accessibility in Internet Explorer 9 by@stevefaulkner
- 20 Sites Assessed For Cognitive Web Accessibility
- Top 4 Reasons Why You Need to Address Web Accessibility
- WebAIM Aids eBay Accessibility Efforts
- Blind woman sues Canadian feds over online access
- Very entertaining video explaining closed captions (YouTube)
- Does your website legally need to be accessible? (U.S.)
- Web Design Guidelines for Low Bandwidth
- Web #Accessibility, Structured Negotiations & DOJ Rulemaking
- 10 Tools for Evaluating Web Design Accessibility
- WCAG 2.0 for Usability Specialists presentation (W3C) (April 2010)
- Facebook patent for ‘social CAPTCHA’ fails on accessibility
- Accessibility and the Law: How good UX can keep you out of court (U.S.)
- Raakt – The Ruby Accessibility Analysis Kit
Response to article by @vavroom Should Sighted Developers Use Screenreaders To Test Accessibility?
Good to test with screen reader, but best to have screenreader users themselves test a web site for accessibility.