What is WCAG 4.1.2 Name, Role, Value?

Custom controls need accessible name, ARIA role, and current state. It is a Level A success criterion under WCAG 2.2.

Why does WCAG 4.1.2 matter on WordPress?

Level A criteria appear in most ADA web-accessibility lawsuits. Failing this criterion on a WordPress site exposes you to demand letters and settlements typically in the $5k-$30k range.

How do I verify the fix?

Re-run a free WCAG 2.2 AA scan on a11yping.com/scan. The issue should clear and your lawsuit-risk score should drop.

Fix guides·WordPress·WCAG 2.2 Level A

Fix WCAG 4.1.2 Name, Role, Value on WordPress

Custom controls need accessible name, ARIA role, and current state.

How to fix it

01
Open your active theme files (or use the Customizer / block editor).
02
Apply the WCAG 4.1.2 fix: Prefer native HTML elements. If using ARIA, set role + aria-label + aria-pressed/expanded.
03
Some issues require plugin updates. Avoid accessibility "overlay" plugins — they tend to make things worse.

Why it matters

WCAG 4.1.2 is a Level A success criterion. Level A failures appear in most ADA web-accessibility lawsuits — over 5,000 were filed in 2025. Typical settlements run $5,000–$30,000 plus remediation cost.

Verify the fix

Run a free scan after deploying. Issue should clear and your risk score should drop.

Run free scan

Same fix on other platforms: Shopify · Webflow · Next.js · Squarespace