WordPress Accessibility Checklist: 10 Quick Wins for WCAG Compliance
Accessibility audits can feel overwhelming. 78 WCAG success criteria, dozens of potential issues, legal compliance concerns. Here are 10 fixes that address the most common problems and give you the biggest impact for your time.
Key Takeaways
- Most WordPress accessibility issues come from 10 common problems
- Skip links and alt text are the two most frequently failed criteria
- Color contrast failures affect more users than any other issue
- Many fixes take minutes to implement, not hours
- Automated tools catch about 30% of issues; manual testing catches the rest
Why These 10 Issues?
According to the WebAIM Million study, the same accessibility issues appear on most websites. The top 10 account for over 90% of detectable errors. Fix these, and you've addressed the majority of accessibility barriers on your site.
| Rank | Issue | % of Sites Affected | WCAG Criterion |
|---|---|---|---|
| 1 | Low contrast text | 83% | 1.4.3 Level AA |
| 2 | Missing alt text | 55% | 1.1.1 Level A |
| 3 | Empty links | 50% | 2.4.4 Level A |
| 4 | Missing form labels | 46% | 1.3.1 Level A |
| 5 | Empty buttons | 27% | 2.4.4 Level A |
| 6 | Missing document language | 18% | 3.1.1 Level A |
| 7 | Missing skip links | ~80% | 2.4.1 Level A |
| 8 | Poor heading structure | ~40% | 1.3.1 Level A |
| 9 | Missing focus indicators | ~60% | 2.4.7 Level AA |
| 10 | Keyboard traps | ~15% | 2.1.2 Level A |
The Checklist
1. Add Skip Links (WCAG 2.4.1)
The problem: Keyboard users must tab through every navigation link to reach main content. On a site with 20 nav links, that's 20 tab presses on every page.
The fix: Add a "Skip to content" link as the first focusable element. It should be visually hidden until focused.
Learn more: What Are Skip Links?
You can skip the manual coding. Skip Links Generator Pro adds WCAG-compliant skip links to any theme in 2 minutes. No code, no theme editing. $15 one-time, no subscriptions.
2. Add Alt Text to All Images (WCAG 1.1.1)
The problem: Screen readers announce "image" for images without alt text. Users have no idea what the image shows.
The fix: Add descriptive alt text to all meaningful images. Use empty alt="" for decorative images.
Learn more: The Hidden Cost of Missing Alt Text
You can prevent missing alt text at the source. Alt Text Reminder warns or blocks publishing when images lack alt text. Never publish inaccessible images again. $19 one-time, no subscriptions.
3. Fix Color Contrast (WCAG 1.4.3)
The problem: Light gray text on white backgrounds. Users with low vision can't read it.
The fix: Ensure 4.5:1 contrast ratio for normal text, 3:1 for large text. Use tools like WebAIM Contrast Checker.
Time to implement: 30 minutes to audit and update CSS
| Text Size | Minimum Contrast (AA) | Enhanced Contrast (AAA) |
|---|---|---|
| Normal text (<18px) | 4.5:1 | 7:1 |
| Large text (18px+ or 14px bold) | 3:1 | 4.5:1 |
| UI components | 3:1 | N/A |
4. Label All Form Fields (WCAG 1.3.1)
The problem: Form fields with placeholder text but no label. Screen readers don't announce what the field is for.
The fix: Add visible labels or use aria-label. Placeholder is not a substitute for labels.
Time to implement: 5 minutes per form
<!-- Wrong -->
<input type="email" placeholder="Your email">
<!-- Correct -->
<label for="email">Email Address</label>
<input type="email" id="email" placeholder="you@example.com">5. Make Links Descriptive (WCAG 2.4.4)
The problem: "Click here" and "Read more" links. Screen reader users navigating by links hear a list of meaningless phrases.
The fix: Use descriptive link text that makes sense out of context.
Time to implement: Content audit required
| Bad | Good |
|---|---|
| Click here to download | Download the 2026 report (PDF) |
| Read more | Read the full accessibility guide |
| Learn more | Learn about WCAG requirements |
6. Set Document Language (WCAG 3.1.1)
The problem: Screen readers don't know what language to use for pronunciation.
The fix: Add lang attribute to the html element. WordPress does this automatically if configured correctly.
Time to implement: 1 minute
<html lang="en">7. Use Proper Heading Structure (WCAG 1.3.1)
The problem: Skipping heading levels (H1 to H3) or using headings for styling instead of structure.
The fix: Use headings in sequential order. Each page should have one H1.
Time to implement: Content audit required
<!-- Wrong -->
<h1>Page Title</h1>
<h3>Section</h3> <!-- Skipped H2 -->
<!-- Correct -->
<h1>Page Title</h1>
<h2>Section</h2>
<h3>Subsection</h3>8. Ensure Visible Focus Indicators (WCAG 2.4.7)
The problem: CSS that removes focus outlines (outline: none) without replacement. Keyboard users can't see where they are.
The fix: Keep default focus styles or replace with visible custom styles.
Time to implement: 15 minutes CSS update
/* Don't do this without replacement */
:focus { outline: none; }
/* Better: Custom focus style */
:focus {
outline: 2px solid #005fcc;
outline-offset: 2px;
}9. Make Buttons Accessible (WCAG 2.4.4)
The problem: Icon-only buttons without text labels. Screen readers announce nothing or just "button".
The fix: Add aria-label or visually hidden text to icon buttons.
Time to implement: 5 minutes per button
<!-- Icon button with aria-label -->
<button aria-label="Close menu">
<svg>...</svg>
</button>
<!-- Icon button with hidden text -->
<button>
<svg>...</svg>
<span class="sr-only">Close menu</span>
</button>10. Avoid Keyboard Traps (WCAG 2.1.2)
The problem: Modal dialogs, embedded content, or custom widgets that trap keyboard focus. Users can't tab out.
The fix: Ensure all interactive elements can be exited with keyboard (Escape key for modals). Test by navigating your entire site with only a keyboard.
Time to implement: Varies by complexity
Testing Your Fixes
After implementing these fixes, verify with:
- Automated scan: WAVE, axe DevTools, or Lighthouse
- Keyboard test: Navigate entire site using only Tab, Enter, Escape
- Screen reader test: Use NVDA (free) or VoiceOver (Mac) to browse key pages
Automated tools catch about 30% of accessibility issues. Manual testing is required for the rest.
Priority Order
If you can only fix a few things today, prioritize by impact:
- Skip links - Affects every keyboard user on every page
- Alt text - Affects screen reader users on every image
- Color contrast - Affects users with low vision on all text
- Form labels - Affects anyone trying to complete a form
- Focus indicators - Affects keyboard navigation
Manual Fixes vs Plugin Solutions
| Issue | Manual Fix | Plugin Solution |
|---|---|---|
| Skip links | Edit theme templates, add CSS | Skip Links Generator Pro ($15, works on any theme) |
| Alt text | Audit every image, edit one by one | Alt Text Reminder ($19, prevents future issues) |
If you don't fix these issues: 67% of accessibility lawsuits cite missing skip links. 89% cite missing alt text. Beyond legal risk, you're excluding users who rely on assistive technology. And with the EAA now enforceable in the EU, the compliance deadline has passed.
Fix the #1 and #2 lawsuit triggers today
Skip links and alt text are the most commonly cited issues in accessibility lawsuits. Fix both in minutes, not hours.
Skip Links Generator - $15 Alt Text Reminder - $19
One-time payment. No subscriptions. Lifetime updates.