Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,090 of 9,090 pages
About the help in other languages
All help pages

The perceivable principle

WCAG principle 1, perceivable, explained for a public body running Exponential - what editors, designers and developers each do for text alternatives, media, adaptable structure and distinguishable presentation, and…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/government/accessibility/principle-perceivable.md

On this page

The perceivable principle

This page is for everyone on a public website team. WCAG 2.2 groups its success criteria under four principles; the first says that information and interface components must be presentable to users in ways they can perceive (https://www.w3.org/TR/WCAG22/). Below, the four guidelines of this principle, with what each role does in an Exponential project and what the administration already does.

Contents

  1. 1.1 Text alternatives
  2. 1.2 Time-based media
  3. 1.3 Adaptable
  4. 1.4 Distinguishable
  5. Related pages

1.1 Text alternatives

RoleDoes
Editorsfill Alternative image text for every informative image; describe charts in text
Administratorsswitch on "Alternative text is required" on image attributes of the classes editors use
Designersdecide how decorative images are marked; icon-only links and buttons get a name
Developersoverride the image template if decorative images must render alt="" (the standard template falls back to the object name)

Admin4: every form control has an accessible name (AdminFormLabelsTest.php). See "Alternative text for images".

1.2 Time-based media

RoleDoes
Editorscaptions for video with speech, transcripts for audio and video, no autoplay
Developersadd caption tracks in the media template if you need them (the standard template writes none)

See "Captions and media".

1.3 Adaptable

RoleDoes
Editorsreal headings in order, lists, tables with header cells and captions
Designersreading order equals visual order; no meaning by position alone
Developerslandmarks, one h1, scope on header cells, labeled form fields, autocomplete on personal fields

Admin4: landmarks, skip link, scope="col", required fields marked for screen readers, direction for right-to-left languages (AdminLandmarksTest.php, AdminRightToLeftTest.php).

1.4 Distinguishable

RoleDoes
Editorsnever color alone ("the fields in red"); no images of text
Designerstext 4.5:1, controls and focus 3:1, links distinguishable, reflow at 320 px, 200% zoom, text spacing
Developerstokens, no fixed heights that clip text, no horizontal page scrolling, respect user settings

Admin4: contrast tokens checked in light and dark mode, notices with icons as well as colors, responsive widths, forced colors and reduced motion (AdminTokenContrastTest.php, AdminNoticesTest.php, AdminResponsiveTest.php).

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x