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 Next.js?

Level A criteria appear in most ADA web-accessibility lawsuits. Failing this criterion on a Next.js 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·Next.js·WCAG 2.2 Level A

Fix WCAG 4.1.2 Name, Role, Value on Next.js

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

How to fix it

01
Locate the React component rendering the affected element.
02
Apply the WCAG 4.1.2 fix: Prefer native HTML elements. If using ARIA, set role + aria-label + aria-pressed/expanded.
03
Add an automated test with @axe-core/react in dev to catch regressions.

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 · WordPress · Webflow · Squarespace