Experience Helpdesk Member Resources/Accessibility Audit Guide

Accessibility Audit Guide

A practical, checklist-driven approach to making your website work for everyone—including the 1.3 billion people worldwide with disabilities

The $13 Trillion Wake-Up Call

Domino's Pizza spent three years fighting a lawsuit over their inaccessible website. They lost. The Supreme Court refused to hear their appeal. Now they're redesigning everything from scratch, spending millions more than if they'd just built it right the first time.
Here's what Domino's didn't understand: A blind customer named Guillermo Robles couldn't order a pizza from their website using his screen reader. He sued under the Americans with Disabilities Act. And he won, because websites are places of public accommodation, just like physical stores.
But forget the legal threats for a second. Let's talk money. The disability community controls $13 trillion in annual disposable income globally, according to Return on Disability research. And Nielsen Norman Group found that when you improve accessibility, you improve usability for everyone—mobile users, people in bright sunlight, parents holding babies, anyone dealing with temporary limitations.
Accessibility isn't charity. It's business.

Why Your "Pretty" Website Is Probably Broken

I recently audited a boutique hotel website that won design awards. Gorgeous parallax scrolling, artistic typography, subtle animations. It was also completely unusable for anyone with even mild vision issues. The light gray text on white backgrounds had a 1.8:1 contrast ratio—WCAG standards require 4.5:1 minimum. Their stylish custom font was unreadable at mobile sizes. Their booking form relied entirely on placeholder text that disappeared when you started typing.
This is what happens when we design for designers instead of humans.
WebAIM's annual analysis of the top one million websites found that 96.8% have detectable WCAG failures. The average site has 50.8 errors on the homepage alone. Each error represents someone who can't use your site, can't buy from you, can't engage with your mission.

The Four Pillars of Web Accessibility

The Web Content Accessibility Guidelines (WCAG) organize everything around four principles. Your site must be:
Perceivable: People need to perceive the information. If they can't see it, they need to hear it. If they can't hear it, they need to read it.
Operable: People need to operate the interface. Not everyone uses a mouse. Some people navigate entirely by keyboard. Others use voice commands.
Understandable: People need to understand the information and interface. Clear language, predictable navigation, helpful error messages.
Robust: Content must work across different assistive technologies, browsers, and devices.
Miss any pillar, and your site crumbles for someone.

Your Complete Accessibility Audit Checklist

Visual Accessibility

Color Contrast Testing

This is your biggest quick win. Poor contrast is the most common accessibility failure, appearing on 83.9% of homepages according to WebAIM.
How to check this off:
  1. Install the free WAVE browser extension from WebAIM
  1. Run it on every page template (homepage, product page, contact page, etc.)
  1. Look for contrast errors (they'll be marked in red)
  1. For each error, you need to adjust either the text color or background color until you hit these ratios:
      • Normal text: 4.5:1 minimum
      • Large text (18pt or 14pt bold): 3:1 minimum
      • UI components and graphics: 3:1 minimum
Don't guess at colors. Use WebAIM's Color Contrast Checker to test specific combinations. Input your text color hex code, your background color hex code, and it tells you exactly whether you pass or fail.
If your brand colors don't meet standards, you have three options: darken the text, lighten the background, or increase font weight and size to qualify for the lower ratio. Most designers resist changing brand colors, but here's the thing—slightly darkening your gray from #999 to #767676 is invisible to most users but makes your content readable for millions more.
Platform-specific fixes:
  • WordPress: Use the Accessibility Checker plugin for automated scanning
  • Squarespace: Access Design > Site Styles to globally adjust color values
  • Wix: Use their built-in Accessibility Wizard, but verify with external tools
  • Shopify: Edit your theme.scss.liquid file to update color variables globally
Trusted resource: WebAIM Color Contrast Checker: https://webaim.org/resources/contrastchecker/

Images and Alt Text Audit

Screen readers can't see images. They read alt text aloud instead. Missing or poor alt text leaves blind users guessing.
How to check this off:
  1. Open your site's HTML (right-click > Inspect)
  1. Search for <img tags
  1. Check every image for alt attributes
  1. Evaluate the quality of existing alt text
Good alt text describes the image's purpose, not just its content. For a photo of your CEO at a podium, bad alt text is "Photo." Better is "CEO speaking at podium." Best is "CEO Jane Smith announcing new sustainability initiative at company conference."
Decision tree for alt text:
  • Decorative image? Use empty alt text: alt=""
  • Informative image? Describe what info it conveys
  • Functional image (like a button)? Describe what it does, not what it looks like
  • Complex image (chart/graph)? Provide brief alt text plus longer description nearby
Platform implementations:
  • WordPress: Use alt text field in Media Library
  • Squarespace: Click image > Design tab > Image Alt Text
  • Wix: Select image > Settings > What's in the image?
  • Shopify: Products > All products > Edit product > Add alt text to images
Trusted resource: Nielsen Norman Group's Alt Text Guide: https://www.nngroup.com/articles/alt-text/

Font and Typography Testing

Fancy fonts kill readability. According to the Interaction Design Foundation, decorative fonts reduce reading speed by up to 30% and comprehension by 15%.
How to check this off:
  1. Set your browser to 200% zoom
  1. Navigate your entire site
  1. Check if all text remains readable
  1. Look for text overlapping, cutting off, or becoming illegible
  1. Test on an actual phone, not just browser mobile view
Readability requirements:
  • Body text: minimum 16px (1rem)
  • Line height: 1.5x minimum for body text
  • Paragraph width: 45-75 characters ideal
  • Font choice: Avoid ultra-thin weights (below 400)
  • Letter spacing: Default or slightly increased, never decreased
The 5-second senior test: Show any page to someone over 65. If they squint, lean forward, or mention the text size, you have a problem. Fix it.
Trusted resource: IxDF Typography in Design Systems: https://www.interaction-design.org/literature/topics/typography

Keyboard Navigation

The Tab Test

Put your mouse in a drawer. Now try to use your website with only the keyboard. This is daily reality for users with motor disabilities.
How to check this off:
  1. Go to your homepage
  1. Press Tab repeatedly
  1. You should see focus indicators (outlines) moving through interactive elements
  1. Can you reach every link, button, and form field?
  1. Can you activate them with Enter or Space?
  1. Can you escape from popups with Esc key?
What you're looking for:
  • Visible focus indicators: Users must see where they are
  • Logical tab order: Left to right, top to bottom
  • No keyboard traps: Users can tab in AND out of all elements
  • Skip links: "Skip to main content" should be first tab stop
  • All interactive elements reachable: Including dropdowns and modals
Common failures to fix:
  • Custom dropdowns that only work on click
  • Carousels without keyboard controls
  • Modal popups you can't escape from
  • Videos without keyboard controls
  • Removing focus outlines for "aesthetic" reasons (never do this)
Quick implementation:
Add this CSS to ensure focus indicators are always visible:
*:focus { outline: 2px solid #0066cc; outline-offset: 2px; }
Trusted resource: WebAIM Keyboard Accessibility Guide: https://webaim.org/articles/keyboard/
 

Form Keyboard Navigation

Forms are where keyboard navigation usually breaks. One broken form field can mean losing a customer forever.
How to check this off:
  1. Tab through every form on your site
  1. Fill them out using only keyboard
  1. Submit with Enter key
  1. Verify error messages are announced
  1. Confirm you can fix errors without mouse
Essential form requirements:
  • Tab order matches visual order
  • Radio buttons arrow through options
  • Checkboxes work with spacebar
  • Dropdowns open with spacebar/enter
  • Error messages link to problem fields
  • Submit works with Enter key

Screen Reader Compatibility

Semantic HTML Structure

Screen readers navigate by headings, landmarks, and links. Without proper structure, your site becomes an incomprehensible wall of text.
How to check this off:
  1. Install NVDA (free Windows) or use VoiceOver (built into Mac/iPhone)
  1. Turn it on and close your eyes
  1. Try to understand your page structure
  1. Navigate by headings (H key in NVDA)
  1. Check if the structure makes sense
Proper heading hierarchy:
  • One H1 per page (the main topic)
  • H2s for major sections
  • H3s for subsections
  • Never skip levels (no H1 to H3)
  • Never use headings for styling—use CSS instead
Example of good structure:
<h1>Product Name</h1> <h2>Features</h2> <h3>Feature 1</h3> <h3>Feature 2</h3> <h2>Pricing</h2> <h2>Reviews</h2>
Trusted resource: WebAIM Screen Reader Testing: https://webaim.org/articles/screenreader_testing/

Link Context Testing

Screen reader users often navigate by pulling up a list of all links. "Click here" and "Read more" become meaningless out of context.
How to check this off:
  1. List all link text on your page
  1. Remove surrounding context
  1. Can you understand where each link goes?
Bad link text:
  • Click here
  • Read more
  • Learn more
  • Download
  • Link
Good link text:
  • Download 2024 annual report (PDF)
  • Read more about accessibility standards
  • Contact customer service
  • View pricing plans
Quick fix for "Read more" links:
Add screen reader-only context:
<a href="/article">Read more<span class="sr-only"> about accessibility compliance</span></a>
CSS for screen reader-only text:
.sr-only { position: absolute; width: 1px; height: 1px; padding: 0; margin: -1px; overflow: hidden; clip: rect(0,0,0,0); border: 0; }

Cognitive Accessibility

Plain Language Audit

The average American reads at a 7th-grade level. Complex language excludes people with cognitive disabilities, non-native speakers, and anyone in a hurry.
How to check this off:
  1. Copy your main pages into Hemingway Editor (free online)
  1. Aim for Grade 8 or below
  1. Eliminate jargon and acronyms
  1. Break up long sentences
  1. Use common words
Before: "Utilize our comprehensive enterprise resource planning solution to optimize operational efficiency."
After: "Our software helps you run your business better."
Simple language checklist:
  • Sentences under 20 words
  • Paragraphs under 5 sentences
  • Active voice instead of passive
  • Concrete words instead of abstract
  • Examples to explain concepts
Trusted resource: Plain Language Guidelines: https://www.plainlanguage.gov/guidelines/

Error Message Clarity

Confusing error messages cause more abandonments than any other form issue. Baymard found that 28% of users abandon after encountering unclear error messages.
How to check this off:
  1. Intentionally trigger every error on your site
  1. Document the message shown
  1. Evaluate against these criteria:
      • Says what went wrong
      • Says how to fix it
      • Shows where the error is
      • Uses plain language
      • Avoids technical codes
Bad error: "Error 400: Invalid input"
Good error: "Please enter a valid email address (like name@example.com)"
Error message formula:
  1. What went wrong
  1. Where it went wrong
  1. How to fix it
  1. Example of correct format
 

Mobile and Touch Accessibility

Touch Target Testing

Nielsen Norman Group research shows that 1 in 4 mobile taps miss their target. For users with motor disabilities, this number doubles.
How to check this off:
  1. Open your site on an actual phone
  1. Try to tap every link and button
  1. Count your misses
  1. Measure target sizes with browser tools
Minimum sizes (WCAG 2.5.5):
  • Touch targets: 44x44 CSS pixels minimum
  • Space between targets: 8px minimum
  • Exception: Inline text links
Common failures:
  • Social media icons too small
  • Close buttons on popups (the tiny X)
  • Stacked navigation links
  • Form radio buttons and checkboxes
  • Footer links crammed together
Platform fixes:
  • Add CSS padding to increase tap area without changing visual size
  • Use flexbox gap property for consistent spacing
  • Make entire card/row clickable, not just the link
Trusted resource: Nielsen Norman Group Touch Targets: https://www.nngroup.com/articles/touch-target-size/

Document and Media Accessibility

PDF Accessibility Check

PDFs are accessibility nightmares. Most are just images of text, completely invisible to screen readers.
How to check this off:
  1. Download every PDF from your site
  1. Open in Adobe Reader
  1. Try to select and copy text
  1. If you can't, it's an image PDF (inaccessible)
  1. Use Read Out Loud feature to test screen reader compatibility
Making PDFs accessible:
  • Create from source document (Word/Google Docs), not scans
  • Add proper headings in source document
  • Include alt text for images
  • Use built-in accessibility checkers
  • Provide HTML alternative when possible
Better approach: Convert PDFs to web pages. HTML is inherently more accessible than PDF.

Video Captions and Transcripts

Netflix was sued for lacking captions. They settled for millions and now caption everything. Learn from their expensive mistake.
How to check this off:
  1. List every video on your site
  1. Check for captions (CC button)
  1. Check caption quality and synchronization
  1. Look for transcript availability
  1. Verify audio descriptions for visual content
Requirements:
  • Captions for all speech and relevant sounds
  • Transcripts for audio-only content
  • Audio descriptions for visual information (when budget allows)
  • Player has keyboard controls
Free captioning tools:
  • YouTube auto-captions (edit for accuracy)
  • Rev.com for professional captions ($1.25/minute)
Trusted resource: W3C Making Audio and Video Media Accessible: https://www.w3.org/WAI/media/av/

The Business Case You Need

Still think accessibility is optional? Let me give you the numbers:
Legal Risk:
  • 4,605 ADA web accessibility lawsuits filed in 2023
  • Average settlement: $20,000-50,000
  • Legal fees: $100,000+ to defend
  • Remediation costs: $10,000-50,000
Market Opportunity:
  • 26% of US adults have a disability
  • $13 trillion global spending power
  • 73% will leave your site for a competitor's if they can't use it
  • Their networks amplify impact—one bad experience reaches hundreds
SEO Benefits:
Google's algorithms favor accessible sites:
  • Alt text helps image search
  • Proper headings improve content understanding
  • Good structure enhances crawlability
  • Captions increase video engagement 12%
Universal Benefits:
Curb-cut effect—accessibility improvements help everyone:
  • Captions help in noisy environments
  • Good contrast helps in bright sunlight
  • Keyboard navigation helps power users
  • Simple language helps non-native speakers
  • Large touch targets help on mobile

Platform-Specific Implementation Guides

WordPress Accessibility

Essential plugins:
  • WP Accessibility by Joe Dolson (free)
  • Accessibility Checker by Equalize Digital
  • One Click Accessibility (basic fixes)
Theme selection:
Only use themes tagged "accessibility-ready." These pass WordPress accessibility review.
Common WordPress issues:
  • Theme removes keyboard focus indicators
  • Plugins inject inaccessible content
  • Page builders create div soup instead of semantic HTML
  • Custom forms lack proper labels

Squarespace Accessibility

Squarespace is generally good but has limitations:
Built-in features:
  • Automatic heading hierarchy
  • Alt text fields for all images
  • Keyboard navigation support
  • Focus indicators included
You must manually add:
  • Skip links (via Code Injection)
  • ARIA labels for complex interactions
  • Transcript blocks for videos
  • Alt text for background images

Wix Accessibility

Wix has an Accessibility Wizard but don't rely on it alone:
Use the wizard for:
  • Basic contrast checking
  • Alt text reminders
  • Heading structure
Manually verify:
  • Keyboard navigation (often broken)
  • Form labels (frequently missing)
  • Focus indicators (sometimes removed)
  • Reading order (can be wrong)

Shopify Accessibility

Choose accessible themes:
  • Dawn (Shopify's accessible flagship)
  • Debut
  • Brooklyn
  • Simple
Avoid themes with heavy animations, parallax effects, or custom cursors.
App caution:
Every app can break accessibility. Test after each installation.
 

Your 30-Day Accessibility Action Plan

Week 1: Baseline and Quick Wins

Day 1-2: Run automated testing
  • Install WAVE extension
  • Scan all page templates
  • Document all errors
  • Create priority list
Day 3-5: Fix contrast issues
  • Adjust all failing color combinations
  • Test fixes on mobile
  • Update style guide
Day 6-7: Alt text sprint
  • Audit all images
  • Write missing alt text
  • Fix decorative images

Week 2: Keyboard and Structure

Day 8-10: Keyboard navigation
  • Complete tab test
  • Fix focus indicators
  • Add skip links
  • Test all forms
Day 11-14: Semantic structure
  • Fix heading hierarchy
  • Add landmark regions
  • Improve link text
  • Structure navigation

Week 3: Content and Media

Day 15-17: Simplify language
  • Run readability tests
  • Rewrite complex sections
  • Fix error messages
  • Add instructions
Day 18-21: Media accessibility
  • Caption all videos
  • Add transcripts
  • Fix PDFs or convert to HTML
  • Test with screen reader

Week 4: Testing and Documentation

Day 22-24: User testing
  • Recruit users with disabilities (if possible)
  • Or test with simulation tools
  • Document remaining issues
  • Create fix timeline
Day 25-27: Create maintenance plan
  • Document accessibility standards
  • Train content creators
  • Set up monitoring
  • Create checklist for new content
Day 28-30: Final verification
  • Rerun automated tests
  • Verify all fixes
  • Test on multiple devices
  • Celebrate progress

The Hard Truths About Accessibility

Truth 1: You'll never be 100% accessible
Perfection is impossible. But 80% accessible is infinitely better than 20%.
Truth 2: Automated tools only catch 30% of issues
They're a starting point, not a solution. Human testing is irreplaceable.
Truth 3: Retrofitting costs 10x more than building right
That beautiful carousel? Might need complete replacement.
Truth 4: Your team will resist
"But it looks better without focus indicators!" You'll hear this. Stand firm.
Truth 5: It's an ongoing process
Every update, every new piece of content, every third-party integration can break accessibility.

Red Flags Requiring Immediate Action

Fix these TODAY if present:
  1. Keyboard traps - Users literally can't escape
  1. Missing form labels - Forms become unusable
  1. Auto-playing audio - Screen readers become inaudible
  1. Seizure triggers - Flashing over 3 times per second
  1. Time limits without warning - Sessions expire mid-task
  1. CAPTCHAs without alternatives - Completely blocks some users
  1. PDF-only content - No HTML alternative
  1. Videos without controls - Can't pause, stop, or adjust
  1. Infinite scroll - Footer content unreachable
  1. Text in images only - Invisible to screen readers

Tools You Actually Need

Free essentials:
  • WAVE browser extension
  • Lighthouse (built into Chrome)
  • NVDA screen reader (Windows)
  • VoiceOver (Mac/iOS built-in)
  • Hemingway Editor
  • Color contrast analyzers
Worth paying for:
  • axe DevTools ($0-40/month)
  • JAWS screen reader (industry standard)
  • Dragon NaturallySpeaking (voice control testing)
  • UserWay or AudioEye (monitoring services)

The Email You'll Send Tomorrow

Here's what you'll tell your team/client/boss:
"I've completed an accessibility audit of our website. We have [number] critical issues that potentially exclude 26% of our visitors and expose us to legal risk.
The good news: We can fix 80% of these issues in the next 30 days without redesigning anything.
Top 3 priorities:
  1. [Biggest issue] - affecting [impact] - 2 hours to fix
  1. [Second issue] - affecting [impact] - 4 hours to fix
  1. [Third issue] - affecting [impact] - 1 day to fix
I've created a complete action plan. When can we discuss implementation?"

Your Accessibility Commitment

Here's what separates good intentions from actual change: Public commitment.
Add this to your website:
"We're committed to digital accessibility. We're actively working to improve our website's accessibility using WCAG 2.1 Level AA standards. Found a barrier? Email accessibility@[yourdomain.com]. We'll respond within 48 hours."
Then actually respond. Actually fix things. Actually care.
Because here's the truth—every accessibility improvement makes your site better for everyone. That's not feel-good rhetoric. That's data-proven fact. The curb cuts that help wheelchairs also help strollers, delivery carts, and skateboards. Your website's accessibility features help far more than the disability community.
But even if they didn't—even if accessibility only helped that 26%—wouldn't that be enough?
Start with contrast. Add alt text. Fix your forms. One improvement at a time.
Your future customers—all of them—are waiting.

Need expert guidance on accessibility compliance? Your UX Helpdesk membership includes consultation on accessibility issues and solutions. Access your member portal for personalized support.