> For the complete documentation index, see [llms.txt](https://docs.acpt.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acpt.io/general/accessibility.md).

# Accessibility (WCAG 2.1 AA)

WCAG 2.1 AA accessibility support in ACPT — current status and scope.

{% hint style="warning" %}
WCAG 2.1 AA support was introduced in ACPT 2.1.0. This page reflects a **vendor self-assessment** — it has not been independently audited by a third party.
{% endhint %}

ACPT is working toward [WCAG 2.1](https://www.w3.org/TR/WCAG21/) Level AA conformance across the parts of the plugin it controls: the React-based admin interface, the meta-box fields rendered in the WordPress post editor, and the front-end forms ACPT generates.

## What's covered today

* **The React admin UI** (post type, taxonomy, meta field, form, and Custom Content Type screens) — automated `axe-core` scans (all WCAG 2.1 A/AA rules, all impact levels) run as a blocking check on every change, alongside `eslint-plugin-jsx-a11y` static analysis and manual keyboard-only testing of shared page templates and custom widgets (modals, dropdowns, drag-and-drop builders, the permissions matrix).
* **Meta box fields** — all 53 field types rendered in the post editor (text, media, relational, repeater/flexible content, and Custom Content Type fields) are individually tested against `axe-core`.
* **Front-end forms** — the fields ACPT's form builder renders on the public side of your site have the same style of automated coverage.

## What isn't covered yet

* Independent third-party audit or formal certification.
* Screen reader testing (NVDA/JAWS/VoiceOver) — current verification relies on automated tooling and computed accessible-name/keyboard-interaction checks, not direct assistive-technology observation.
* Non-desktop viewport sizes, browser zoom, and text-resize behavior.
* Content you control yourself — for example, captions for videos you upload through a Media field are your responsibility; ACPT can't generate them for you.
* Third-party integrations (page builders, Gutenberg's own editor chrome, embedded third-party UI) are outside ACPT's control and not covered by this assessment.

## Need the full technical report?

If you need a detailed, criterion-by-criterion conformance report (VPAT-style) for a procurement or compliance review, [open a support ticket](/general/how-to-open-a-ticket.md) and we'll share it with you.

{% hint style="info" %}
Found an accessibility issue? We'd like to know — [open a support ticket](/general/how-to-open-a-ticket.md) with a description and, if possible, the page/field type involved.
{% endhint %}