Skip to content
WilliamAlexander.co
  • Studio
  • Work
  • Services
  • Process
  • Writing
  • Lab
  • About
  • Start a project
  1. Home
  2. Articles
  3. Website Accessibility Audit: DIY Guide
Web Strategy

Website Accessibility Audit: DIY Guide

How to identify and fix common accessibility issues

September 12, 2026 10 min read

Key Takeaways

  • Start with automated tools—they catch obvious issues quickly
  • Test with keyboard-only navigation—can you reach everything?
  • Check images for meaningful alt text
  • Verify color contrast meets minimum ratios
  • Test with a screen reader to understand the experience
Overview

Why DIY Accessibility Auditing

Accessibility can feel overwhelming—legal requirements, technical standards, specialized knowledge. Many organizations delay accessibility work because it seems too complex or expensive. But you can make meaningful progress with basic tools and systematic checking.

This guide covers how to conduct a practical accessibility audit yourself. You won't catch everything a professional auditor would, but you'll identify the most common and impactful issues. Often, fixing these basics dramatically improves the experience for users with disabilities.

Progress Over Perfection

Don't let perfect be the enemy of good. A site with obvious accessibility barriers fixed is better than a site waiting for a comprehensive professional audit. Start improving now, and continue improving over time.

Automated

Automated Testing

Free Automated Tools

  • WAVE: Browser extension showing issues visually on the page
  • axe DevTools: Chrome extension with detailed issue explanations
  • Lighthouse: Built into Chrome DevTools, includes accessibility audit
  • Pa11y: Command-line tool for automated scanning

How to Use Automated Tools

  1. Test representative pages

    Home page, content pages, forms, navigation—cover the major templates.

  2. Run multiple tools

    Different tools catch different issues. Use at least two.

  3. Review findings critically

    Not every flagged issue is equally important. Prioritize.

  4. Document and track

    Record findings and track fixes. This helps measure progress.

What Automated Tools Miss

  • Whether alt text is actually meaningful
  • Logical reading order of content
  • Whether error messages make sense
  • Focus management in dynamic content
  • Video caption quality

Automated Limitations

A "passing" automated scan doesn't mean a site is accessible. It means the obvious machine-detectable issues are addressed. Many real-world accessibility problems require human testing.
Keyboard

Keyboard Testing

Many users navigate without a mouse. Test your site with keyboard only.

Basic Keyboard Test

  • Start at the address bar and Tab through the page
  • Can you reach every interactive element?
  • Is the focus indicator visible?
  • Does Tab order follow visual layout?
  • Can you access dropdown menus with keyboard?
  • Can you close modals with Escape?

Key Combinations

Action Key What to Test
Next focusable element Tab Can reach all controls
Previous element Shift + Tab Can navigate backward
Activate button/link Enter Buttons and links work
Toggle checkbox Space Forms are operable
Close dialog Escape Modals can be dismissed
Navigate options Arrow keys Menus and selects work

Common Keyboard Issues

  • Focus gets trapped in elements
  • No visible focus indicator
  • Skip links missing or non-functional
  • Interactive elements unreachable by Tab
  • Custom controls missing keyboard support
Visual

Visual Testing

Color Contrast

Text must have sufficient contrast with its background:

  • Normal text: 4.5:1 minimum ratio
  • Large text (18pt+): 3:1 minimum ratio
  • UI components: 3:1 minimum ratio

Use tools like WebAIM Contrast Checker or browser extensions to verify.

Images and Alt Text

Check every image:

  • Does it have alt text?
  • Is the alt text meaningful? ("Photo of team meeting" not "image123.jpg")
  • Decorative images should have empty alt (alt="")
  • Complex images (charts, diagrams) need longer descriptions

Text Resizing

  • Zoom browser to 200%
  • Is content still readable?
  • Does layout break?
  • Is horizontal scrolling minimized?

Don't Rely on Color Alone

Information conveyed by color (error states, required fields, links) should also have another indicator. Users who can't distinguish colors need alternative cues.

Motion and Animation

Provide ways to pause, stop, or hide moving content. Some users have vestibular disorders triggered by motion. Respect prefers-reduced-motion settings.

Screen Reader

Screen Reader Testing

Test with an actual screen reader to understand the experience.

Getting Started

  • VoiceOver (Mac): Built-in, Cmd+F5 to start
  • NVDA (Windows): Free download
  • JAWS (Windows): Professional tool, paid
  • TalkBack (Android): Built-in for mobile testing

What to Test

  • Are headings announced and in logical order?
  • Do images have meaningful descriptions read?
  • Are form fields properly labeled?
  • Are links descriptive? ("Read more" vs. "Read more about our services")
  • Is dynamic content announced?

Common Screen Reader Issues

  • Missing or improper heading structure
  • Form inputs not associated with labels
  • Links that say "click here" or "read more"
  • Tables without proper headers
  • Content that changes without announcement

Start Simple

Screen reader testing takes practice. Start with a few pages and basic tasks. Listen to how your content sounds. Even brief testing reveals issues you'd never notice visually.
Forms

Forms and Errors

Form Accessibility Checklist

  • Every input has an associated label
  • Required fields are indicated (not just by color)
  • Input purpose is clear (use autocomplete attributes)
  • Error messages are specific and helpful
  • Errors are announced to screen readers
  • Focus moves to error messages

Common Form Issues

  • Placeholder text used instead of labels
  • Validation errors not associated with fields
  • Required indicator only shown by asterisk color
  • Custom selects not keyboard accessible
Prioritization

Prioritizing Fixes

High Priority (Fix First)

  • Keyboard access blocked
  • Form fields without labels
  • Images without alt text
  • Videos without captions
  • Insufficient color contrast on key content

Medium Priority

  • Heading structure issues
  • Link text clarity
  • Focus indicator visibility
  • Error message improvements

Lower Priority

  • Decorative images with non-empty alt
  • Minor contrast issues on non-essential elements
  • Optimization of already-functional features

Impact-Based Prioritization

Prioritize by impact: How many users affected? How severely? Focus on issues that completely block access before refining issues that merely inconvenience.

Conclusion

Start Your Audit

You now have the tools and approach to conduct a basic accessibility audit. Start with automated testing, verify with keyboard and visual testing, and experience your site through a screen reader. Document what you find, prioritize fixes, and iterate.

Remember: accessibility isn't a one-time project. Build it into your ongoing development process. Every improvement makes your site usable by more people.

Frequently Asked Questions

What accessibility standard should I follow?

WCAG 2.1 Level AA is the current practical standard. It's referenced in most legal requirements and covers the essential accessibility needs. Level AAA is aspirational but often impractical for full compliance.

Can automated tools catch all accessibility issues?

No. Automated tools catch about 30-40% of issues—important ones, but not all. Many issues require human judgment: Is this alt text meaningful? Is the reading order logical? Does this error message make sense? Use automated tools as a starting point, not a complete solution.

How often should I audit for accessibility?

Audit significant pages after major updates or redesigns. For ongoing sites, quarterly checks of key pages catch regression. Make accessibility part of your development process, not just periodic audits.

Do I need to hire a professional auditor?

For legal compliance or certification, yes. For practical improvement, you can accomplish a lot yourself. Start with DIY auditing to fix obvious issues, then consider professional auditing for comprehensive compliance review.
Accessibility Web Strategy Compliance Best Practices UX
William Alexander

William Alexander

Senior Web Developer

25+ years of web development experience spanning higher education and small business. Currently Senior Web Developer at Wake Forest University.

Related Articles

Web Strategy

Website Launch Checklist: What Most People Miss

11 min read
Web Strategy

Mobile-First Design: Beyond Responsive

10 min read

Need help with website accessibility?

I help businesses identify and fix accessibility issues. Let's discuss how to make your website work for everyone.

Let's talk about your project.

Send a few sentences about what you're working on. Start a project →

Practice

  • Work
  • Services
  • Web design
  • Process
  • Start a project

Read & explore

  • Writing
  • Lab
  • About
  • Resume

Elsewhere

  • LinkedIn
  • GitHub
  • Email

Based

Roanoke, Virginia
Working in Eastern Time

Selectively available, Q3 2026

© 2026 William Alexander. Built by hand in Roanoke, Virginia.

Set in Inter and Bitter. Running on WordPress, hosted on Flywheel.