Remediation Guide
How to fix the most common accessibility issues found in your documents.
Overview
Remediation is the process of fixing accessibility issues found in your documents. This guide covers the most common issues and how to resolve them.
Images and Alt Text
Missing Alternative Text
WCAG 1.1.1 -- Non-text Content
Every meaningful image must have alternative text that describes its content or function.
How to fix in PDFs:
- Open the PDF in Adobe Acrobat
- Go to Accessibility > Set Alternate Text
- Add descriptive alt text to each image
- For decorative images, mark them as "Decorative"
How to fix in HTML:
<!-- Before -->
<img src="chart.png">
<!-- After -->
<img src="chart.png" alt="Bar chart showing 40% increase in compliance scores from Q1 to Q4 2025">
Tips for writing good alt text:
- Describe what the image conveys, not what it looks like
- Keep it concise (under 125 characters when possible)
- Don't start with "Image of" or "Photo of"
- For complex images like charts, provide a longer description nearby
Color and Contrast
Insufficient Color Contrast
WCAG 1.4.3 -- Contrast (Minimum)
Text must have a contrast ratio of at least 4.5:1 against its background (3:1 for large text).
How to fix:
- Use a contrast checker tool to test your color combinations
- Increase the darkness of text or lightness of backgrounds
- Avoid light gray text on white backgrounds
Information Conveyed by Color Alone
WCAG 1.4.1 -- Use of Color
Don't rely on color as the only way to convey information.
How to fix:
- Add text labels, patterns, or icons alongside color indicators
- For example, use both red color AND an "Error" label for error states
Document Structure
Missing Heading Hierarchy
WCAG 1.3.1 -- Info and Relationships
Documents must use proper heading levels (H1, H2, H3) in a logical order.
How to fix:
- Ensure every document has exactly one H1
- Don't skip heading levels (e.g., don't go from H1 to H3)
- Use headings to create a meaningful outline of the content
Missing Document Language
WCAG 3.1.1 -- Language of Page
Documents must declare their primary language.
How to fix in HTML:
<html lang="en">
How to fix in PDFs:
- Go to File > Properties > Advanced
- Set the Language field to the appropriate language
Tables
Missing Table Headers
WCAG 1.3.1 -- Info and Relationships
Data tables must have properly marked header cells.
How to fix in HTML:
<!-- Before -->
<table>
<tr><td>Name</td><td>Score</td></tr>
<tr><td>Page 1</td><td>85%</td></tr>
</table>
<!-- After -->
<table>
<tr><th scope="col">Name</th><th scope="col">Score</th></tr>
<tr><td>Page 1</td><td>85%</td></tr>
</table>
Links
Non-Descriptive Link Text
WCAG 2.4.4 -- Link Purpose
Link text must describe the link's destination. Avoid "click here" or "read more."
How to fix:
<!-- Before -->
<a href="/report">Click here</a>
<!-- After -->
<a href="/report">View your accessibility report</a>
Forms
Missing Form Labels
WCAG 1.3.1 / 4.1.2 -- Info and Relationships / Name, Role, Value
Every form input must have an associated label.
How to fix:
<!-- Before -->
<input type="email" placeholder="Email">
<!-- After -->
<label for="email">Email address</label>
<input type="email" id="email" placeholder="Email">
Need More Help?
If you encounter issues not covered here, check our FAQ or reach out through the Adaline platform.