VPATFast.com

Home / Guides / How to write ACR remarks: examples and common mistakes

Guide · Updated November 21, 2026

How to write ACR remarks: examples and common mistakes

How to write the Remarks and Explanations column of a VPAT 2.5 ACR: location, issue, impact and workaround, with eight sample remarks and wording to avoid.

The last column of every row in an ACR is "Remarks and Explanations." The conformance level tells the buyer how much of the criterion you meet. The remark tells them where you fall short, who is affected and how to work around it. Of two reports that both say Partially Supports, the one with clear remarks passes review more easily.

A good remark covers four things

  1. Location: which page, module or component.
  2. Issue: exactly which behavior fails the criterion, not "some issues exist."
  3. Extent: how much meets the criterion and how much does not.
  4. Workaround: if there is an equivalent way to complete the same task, say so.

Remarks are usually written in English, because most buyers read ACRs in English. Use short sentences in the present tense, state facts, and leave out marketing language.

Eight examples

These examples show the style only. Replace the content with the actual test results for your own product.

1.1.1 Non-text Content · Partially Supports

Most images have text alternatives. Charts on the Reports dashboard do not have a text alternative; the same data is available in the table below each chart.

States the location (the Reports dashboard), the issue (charts have no text alternative) and the workaround (the table below).

1.4.3 Contrast (Minimum) · Partially Supports

Body text and controls meet the 4.5:1 ratio. Placeholder text in form fields and the timestamp text in the activity feed do not.

Says what meets the criterion first, then names the specific elements that do not.

2.1.1 Keyboard · Partially Supports

All functions can be operated with a keyboard except reordering cards by drag and drop in Board view. List view offers the same reordering with keyboard support.

Drag and drop is a common keyboard problem, so it matters to spell out the equivalent keyboard path.

2.4.7 Focus Visible · Supports

All interactive elements show a visible focus indicator.

A Supports remark can be short, but it is better not to leave it blank.

1.2.2 Captions (Prerecorded) · Not Applicable

The product does not contain prerecorded video with audio.

Write this only if there really is no video. If tutorial videos in the help center are within the report's scope, this is not Not Applicable.

2.5.8 Target Size (Minimum) · Partially Supports

Icon buttons in the table toolbar are 20 by 20 CSS pixels and are placed without enough spacing. Other targets meet the requirement.

A criterion new in WCAG 2.2: targets must be at least 24 by 24 CSS pixels or have enough spacing around them.

3.3.8 Accessible Authentication (Minimum) · Does Not Support

The sign-in form blocks pasting into the password field, so password managers cannot fill it. No alternative sign-in method is offered.

Blocking paste in the password field is a common reason for failing 3.3.8.

4.1.2 Name, Role, Value · Partially Supports

Standard controls expose names and roles. The custom date picker and the toggle switches in Settings do not expose their state to assistive technology.

Custom components cause most 4.1.2 issues. Naming the components is more useful than a vague "some components."

Wording to avoid

  • "Fully compliant" or "100% accessible." No test can back up absolute claims like these, and they easily contradict the levels in other rows.
  • "Some issues may exist." Too vague; the buyer cannot judge the impact.
  • Fix promises with specific dates. Once "Will be fixed by Q2" slips, it becomes an issue in the next review. Write "A fix is planned" and keep dates in a separate roadmap.
  • Repeating the test methods in every row. Test tools and methods belong in the "Evaluation Methods Used" section at the top of the report. Each remark states only the conclusion for that row.
  • Copying remarks from another product. Buyers compare remarks with the actual interface. A remark that mentions a feature your product does not have damages your credibility right away.

Remarks and levels must match

If a remark describes an issue, the level cannot be Supports. If the level is Partially Supports, the remark must say which part fails. For how to choose a level, see how to choose VPAT conformance levels.

Next step

In the .docx you download from the generator, every criterion comes with a placeholder remark based on its level. Replace each one with your product's actual test results, using the structure above.

Ready to draft your ACR?

The preview is free. US$49 one-time per product to download the ACR and the statement.

Open the generator