Does W3C WCAG 4.1.2 Name, Role, Value (Level A) apply to my service?

It applies when Service type — any answer; Service is likely to be accessed by children under 18; Service uses content personalization.

From when does this apply?

W3C WCAG 4.1.2 Name, Role, Value (Level A) applies from 5 October 2023. Its current status is: in force.

W3C WCAG · WCAG-4-1-NAME-ROLE

W3C WCAG 4.1.2 Name, Role, Value (Level A)

Ensure all user interface components have programmatically determinable names, roles, states, properties, and values, and that changes are communicated to assistive technologies

CRITICALRequirementDesign defaultsTechnical standardIn forceApplies from 5 October 2023

Where this comes from

Provision: 4.1.2 Name, Role, Value (Level A)

Instrument: W3C Web Content Accessibility Guidelines (WCAG) 2.2

Citation: W3C, Web Content Accessibility Guidelines (WCAG) 2.2, Success Criterion 4.1.2 Name, Role, Value, Level A, W3C Recommendation 12 December 2024 (first published 05 October 2023)

Text version: W3C Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation first published 05 October 2023; the retrieved edition is the W3C Recommendation of 12 December 2024 (https://www.w3.org/TR/2024/REC-WCAG22-20241212/, errata incorporated); retrieved from w3.org/TR/WCAG22/ on 2026-09-23.

Read the official text ↗

Who it applies to

It applies when all of these are true:

Service type — any answer
Service is likely to be accessed by children under 18
Service uses content personalization

What engineering work it implies

Sample acceptance criteria Landfall generates for this obligation:

Every custom UI component exposes an accessible name, role, and current value/state to assistive tech
Native elements are used where possible; ARIA roles/states are applied correctly for custom widgets
State changes (expanded, selected, checked, disabled) are updated programmatically as they occur
A screen-reader pass confirms name/role/value for each interactive component
Unit tests cover the core logic (aim for >80% coverage on new code)

Questions people ask

Does W3C WCAG 4.1.2 Name, Role, Value (Level A) apply to my service?: It applies when Service type — any answer; Service is likely to be accessed by children under 18; Service uses content personalization.
From when does this apply?: W3C WCAG 4.1.2 Name, Role, Value (Level A) applies from 5 October 2023. Its current status is: in force.

Find out whether this one lands on you

Landfall's pre-scan answers the applicability question above for your product in minutes, then turns every obligation that applies into traceable engineering tickets with a citation chain your auditors can follow.

Run the pre-scan All W3C WCAG obligations

Not legal advice. Landfall maps regulatory obligations to engineering work for planning purposes. Its verdicts are not legal advice and create no attorney-client relationship — verify with qualified counsel before relying on them.

What Landfall Is NOT

Critical Boundaries

Understanding these boundaries is essential before using this product. Misuse of this tool for purposes outside its scope may create legal, regulatory, or commercial risk for your organization.

NOT Legal Advice

This product does not provide legal advice and does not create an attorney-client relationship.

Interpretations are informational analysis, not legal counsel. Always consult qualified legal professionals for compliance decisions.

NOT a Risk Score

We do not quantify, calculate, or certify your compliance risk level.

No numerical risk rating, compliance percentage, or safety score. Risk assessment requires human judgment about your specific context.

NOT Runtime Enforcement

This is a planning and mapping tool, not a runtime enforcement system.

Does not integrate with your production systems. Does not block, filter, or enforce compliance in real-time. Implementation is your responsibility.

NOT Regulatory Approval

Using this tool does not mean you are compliant with any regulation.

No certification, seal of approval, or compliance guarantee. Regulators will evaluate your actual implementation, not your use of this tool.

NOT Authoritative Interpretation

Our interpretations are not binding and may differ from regulatory guidance.

Only regulators and courts provide authoritative interpretation. Our analysis reflects our reading of requirements, which may be incomplete or incorrect.

NOT a Safe Harbor

This tool does not shield you from enforcement actions or liability.

Documentation of your process is valuable, but does not constitute a legal defense. Compliance is ultimately your organization's responsibility.

NOT an AI Compliance Agent

AI features assist analysis but do not make compliance decisions for you.

AI-generated interpretations require human review and approval. Automated suggestions are starting points, not final answers.

NOT Complete Coverage

We do not cover all regulations, all obligations, or all jurisdictions.

Regulatory landscape is vast and evolving. Gaps in our coverage do not mean those requirements don't apply to you.

What This Tool IS:

A structured workflow for mapping regulatory requirements to implementation tasks
A documentation system for compliance decisions (audit trail)
A collaboration platform for compliance, legal, and engineering teams
An informational resource for understanding regulatory obligations