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

The operable principle

WCAG principle 2, operable, for a public body running Exponential - keyboard access, enough time, seizures, navigation and input modalities, with each role's tasks and what the admin4 administration provides.

Download as PDF

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

On this page

The operable principle

This page is for everyone on a public website team. The second WCAG principle says that interface components and navigation must be operable (https://www.w3.org/TR/WCAG22/). Below, its five guidelines, with each role's tasks in an Exponential project.

Contents

  1. 2.1 Keyboard accessible
  2. 2.2 Enough time
  3. 2.3 Seizures and physical reactions
  4. 2.4 Navigable
  5. 2.5 Input modalities
  6. Related pages

2.1 Keyboard accessible

RoleDoes
Developersnative elements; menus, dialogs, sliders and embedded widgets work with the keyboard; no traps
Editorsavoid embedding third-party widgets that trap the keyboard

Admin4: tabs, tree, context menus, drag-and-drop alternative, date pickers (AdminKeyboardTest.php). See "Keyboard and focus".

2.2 Enough time

RoleDoes
Administratorsweigh session length for security against people who work slowly: site.ini [Session] SessionTimeout (31104000 s, 360 days, shipped) (13.7)
Designerssliders and carousels can be paused; no automatic page refresh
Editorsno content that moves by itself without a pause control

Expired forms show the "form expired" page (Form expired page).

2.3 Seizures and physical reactions

RoleDoes
Editorsno videos or animations that flash more than three times per second
Designersrespect prefers-reduced-motion (admin4 does in admin4.css)

2.4 Navigable

RoleDoes
Developersskip link, landmarks, descriptive <title>, logical focus order, current page marked with aria-current
Editorsclear object names (they become page titles), descriptive headings, meaningful link texts
Designersvisible focus; sticky elements that do not cover the focus (2.4.11)

Admin4: skip link, aria-current="page" in breadcrumb and top menu, one focus ring (AdminLandmarksTest.php, AdminHeaderTabOrderTest.php).

2.5 Input modalities

RoleDoes
Designerstargets at least 24 x 24 px (2.5.8); visible labels match accessible names
Developerssingle-pointer alternatives to dragging (2.5.7); no actions on pointer down only

Admin4: targets at least 24 x 24 px (admin4 styling); reordering sub items by drag also works with the keyboard and by editing the priority cells.

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