ACR Editor cannot import documents using the 2.5-edition / WCAG 2.2 catalogs the format ships
- Dominant language
- JavaScript
- Stars
- 128
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
*(Filed here per GSA/openacr-editor#43 — "File Issues In Main Repo".)*
### Environment
ACR Editor at https://acreditor.section508.gov/ (footer: v1.0, published April 2024), tested 2026-08-12. CLI: `@openacr/openacr@0.3.8`, Node v24.13.0.
### Steps to reproduce
1. Author an ACR against `catalog: 2.5-edition-wcag-2.2-508-en` (one of the catalogs shipped in `@openacr/openacr` since the v1.0 format release) that includes a WCAG 2.2-only criterion such as 2.5.8 Target Size (Minimum).
2. Confirm it is CLI-valid: `openacr validate -f draft.yaml -c catalog/2.5-edition-wcag-2.2-508-en.yaml` → `Valid!`.
3. In the editor, use **Open report** and select the file.
### Expected
The editor imports any document that is valid against a catalog the format itself ships.
### Actual
Import is rejected criterion-by-criterion against the 2.4-edition / WCAG 2.1 catalog — for the file above the alert reads:
> criteria '2.5.8' is not included in 'Table 2: Success Criteria, Level AA'
The same document reworked onto `2.4-edition-wcag-2.1-508-en` imports cleanly (verified both directions 2026-08-12; the Level AA page header also links "Web Content Accessibility Guidelines 2.1").
### Why it matters
The format has shipped WCAG 2.2 / VPAT 2.5 catalogs since March 2024 (#352 closed for that release), but the hosted editor cannot open documents written against them — so evaluators who follow the format's current catalogs lose the editor as a finish/review surface, and may not discover why from the per-criterion alert. Either 2.5-edition catalog support in the editor, or a documented statement of the supported catalog set (import screen + docs), would close the gap.
Related history: #352 (format-side WCAG 2.2 support, closed), GSA/openacr-editor#83 (earlier WCAG-version labeling confusion in the editor, closed).
Contributor guide
Research direction
Start at the editor's Open report import path and compare its criterion validation against catalog/2.5-edition-wcag-2.2-508-en.yaml; use draft.yaml and the openacr validate command as the reproduction. Done means a valid 2.5/WCAG 2.2 document containing 2.5.8 imports successfully, or the editor's supported catalog set is explicitly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- accessibility, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100