Developer Playground

20+ Free Tools · Privacy First

Success Criterion · WCAG 3.1.2

Language of Parts

The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.

Level AAWCAG 2.0Understandable3.1 · Readable

Success criterion

What WCAG 3.1.2 requires

Summarized directly from the official Understanding document so teams can quote the requirement accurately.

All non-text content that is presented to users must expose an equivalent text-based alternative unless a documented exception applies.

View Understanding 3.1.2 Open QuickRef techniques

Overview

Use this space to describe how your product interprets this success criterion, list ownership, and capture implementation decisions for future audits.

Reference: All summaries and highlights originate from Understanding WCAG 3.1.2 and the W3C quick reference.

Read the Understanding doc View sufficient techniques

Fast facts

Conformance level: Level AA
WCAG version introduced: WCAG 2.0
Principle: Understandable
Guideline: 3.1 · Readable

Implementation checklist

Capture progress and blockers

Document how this criterion impacts your product and note any exceptions.
Describe the user experience goal in plain language for designers and engineers.
List the components, templates, or workflows that must meet this requirement.
Capture manual and automated testing steps for future audits.

Testing ideas

Prove conformance with evidence

Pair automated linting with human review to verify visual, auditory, or temporal aspects.
Use assistive technology walkthroughs (screen reader, keyboard, switch, voice) to validate behavior.
Capture screenshots or recordings that demonstrate pass/fail conditions.

Related success criteria