Evaluating Web Sites for Accessibility with Firefox
In Evaluating Web Sites for Accessibility with Firefox, Patrick H. Lauke explains how you can use the Web Developer Toolbar extension to perform some of the manual accessibility checks that are needed after using an automated testing tool.
I regularly use the Web Developer Toolbar for evaluating accessibility, but I never realised some of the commands Patrick mentions existed. Outline Custom Elements, Linearize Page, and View Form Information are all very useful commands that I’ll be using a lot now that I’ve been made aware of them.
- Previous post: Who’s There? - an ebook about blogs
- Next post: No Mr. Ballmer, Microsoft Will not Win the Web
Subscribe / follow
Sponsors
Authentic Jobs
- Software Engineer at charity: water (New York, NY, Ne, US)
- Dev Ops Engineer @ General Things at The Sourcery (San Francisco, CA, Ca, US)
- Django Developer (Bristol) at Potato (Bristol, UK, GB)
- UI Designer at charity: water (New York City, Ne, US)
DreamHost web hosting
Use the promo code 456BEREASTREET3 to save USD 20 when you sign up for DreamHost


Comments
I regularly use Marc Guery’s HTML Validator plugin for FireFox myself which I find especially handy for making sure code is valid as I type and view it on my local web server without needing to upload the page somewhere to validate it and or go on-line.
glad you liked it roger. i have to admit that before i started devising the little article i was unaware of many functions as well…so it was a journey of discovery for me too.
Thanks to both Roger and Patrick for such a great reference. I would also like to recommend the Fangs extension (https://addons.mozilla.org/extensions/moreinfo.php?id=402). As its description says, Fangs “renders a text version of a web page similar to screen reader output”. I find it very helpful.
If anybody’s interested, I have a bookmarklet script that strips out presentational information from whatever page you’re on, revealing the page’s structure. Usually can get a pretty quick idea of standards compliance and accessibility from it.
Comments are disabled for this post (read why), but if you have spotted an error or have additional info that you think should be in this post, feel free to contact me.