New to ACRs? Start Here.

Many people assume an ACR is simply a document to fill out, but in reality, it's the final output of a much larger process: understanding a product, evaluating accessibility, and documenting findings.

Whether you're a UX Designer, Product Manager, Developer, QA Engineer, or Accessibility Specialist, this guide will help you understand the first steps.

What is an ACR?

An Accessibility Conformance Report (ACR) documents how well a product meets accessibility standards such as WCAG (Web Content Accessibility Guidelines), Section 508, or EN 301 549.

Think of an ACR as a summary of accessibility testing and evaluation. It explains what was assessed, what works well, and where accessibility barriers may still exist.

An ACR is not the accessibility testing itself.

It is the report that communicates the results of that testing.

Step 1: Understand What You're Evaluating

Before opening an ACR template, take a moment to understand the product you're assessing.

Ask yourself:

  • What is the product name and version?
  • Which platforms are included? (Web, mobile, desktop, etc.)
  • Are we evaluating the entire product or only specific features?
  • Which accessibility standards apply?

Getting the scope right at the beginning saves significant time later.

Step 2: Familiarize Yourself with the Structure

Most ACRs are created using a VPAT (Voluntary Product Accessibility Template).

For each accessibility requirement, you'll typically document:

Conformance Level

How well the product meets the requirement.

Common ratings include:

  • Supports
  • Partially Supports
  • Does Not Support
  • Not Applicable
  • Not Evaluated

Remarks and Explanations

The evidence that supports the rating.

This is often the most important part of the report because it explains why a particular conformance level was chosen.

Step 3: Gather Accessibility Evidence

Before writing anything, collect the information that will support your findings.

Common sources include:

  • Automated accessibility scans
  • Keyboard testing
  • Screen reader testing
  • Color contrast reviews
  • Design reviews
  • Accessibility bug reports
  • Previous accessibility assessments

A good ACR is built on evidence, not assumptions.

Step 4: Start with Simpler Accessibility Requirements

If you're new to accessibility, some requirements are easier to evaluate than others.

Good starting points include:

  • Color Contrast (WCAG 1.4.3)
  • Reflow and Responsive Layouts (WCAG 1.4.10)
  • Keyboard Access (WCAG 2.1.1)
  • Focus Indicators (WCAG 2.4.7)
  • Labels and Instructions (WCAG 3.3.2)

These often provide quick opportunities to learn how accessibility findings are documented.

Step 5: Document Findings Before Choosing Ratings

A common mistake is deciding on a conformance rating first and then trying to justify it.

Instead, start with the evidence.

Ask:

  1. What did we test?
  2. What did we observe?
  3. Were there any exceptions or issues?
  4. What rating best reflects the results?

For example:

Login, registration, and password reset workflows were tested using keyboard-only navigation. All interactive elements were reachable and operable without a mouse. No keyboard traps were identified.

From there, a rating such as Supports becomes much easier to justify.

Step 6: Track Accessibility Issues Along the Way

As issues are discovered, keep a running list.

Include:

  • WCAG criterion
  • Description of the issue
  • Impact to users
  • Affected screens or workflows
  • Severity or priority

This list will become one of your most valuable resources when completing the report.

Step 7: Learn from Existing ACRs

One of the fastest ways to improve is by reviewing completed reports from organizations with mature accessibility programs.

Look at examples from:

  • Microsoft
  • Adobe
  • Salesforce
  • ServiceNow
  • Google

Pay attention to how findings are written, how exceptions are documented, and how evidence is communicated.

Key Takeaway

The most important thing to remember is that an ACR is not a form-filling exercise.

It is the result of understanding a product, evaluating accessibility, gathering evidence, and clearly documenting findings.

If you focus on collecting good evidence first, writing the ACR becomes much easier.