So, here’s my quick-start guide to get you over the hump. Cause, you know, not to nag, but you really should be doing more of this.

(I’m intentionally not going into all the how and why – I’ll leave that up to the tools or a quick google search.)

Use the WAVE Firefox Toolbar

This is a must-have tool. It even allows you to do evaluations of websites that haven’t gone live yet.

• Use “Errors, Features, and Alerts” for feedback directly on your website.
• Use “Outline” to make sure headings are logical, describe the order of content well, and are properly nested. If you aren’t using headings, you should! (It’ll also help your SEO)
• Use “Text-only” to view the order of the content. Imagine you have to read the page from beginning to end. Is the important information first? Would the page benefit from skip links?

Uh oh. My blog has 4 accessibility errors. I need to get on that.

Use the Web Developer toolbar

Great for many things and also a must-have.

• Disable Javascript to test any functionality that uses javascript. Make sure everything is still functional or offer an alternate way to do the task.

Validate your code

The web developer toolbar has these (and more) built-in or you can just go directly to the service.

• W3C CSS Validator
• W3C HTML Validator

THAT’S IT.

Ok, just a few more things. Here are some more tools and links I’ve gathered that might also be useful.

• FAE Evaluator has a very easy to read report
• WCAG/Section 508 evaluators are not as easy to read but will give a tiered evaluation to help you start with more essential fixes.
• ATRC Web Accessibility Checker

offers suggestions for fixes.

• And lots of things I’ve bookmarked in delicious!

For those that already have a set of methods, what do you do differently?

Link