Skip to main content

Devices and Accessibility

Accessibility and device support emerge from the configured screen: the selected component and the surrounding content. A useful review therefore includes fields, labels, actions, navigation, custom content, and layout.

WCAG and BITV in this guideline​

WCAG 2.2 is the W3C standard for accessible web content. Its success criteria use the principles perceivable, operable, understandable, and robust, and the levels A, AA, and AAA.

The German BITV 2.0 applies to public bodies within its scope. It refers to the same four principles and to harmonised standards. Each project needs to clarify its legal and contractual requirements.

warning

This guideline supports review. It is not a legal assessment or proof of WCAG, BITV, EN 301 549, or contractual conformance.

Accessibility features in ADITO​

The enableA11y UserPreference enables accessibility-related behavior for one user. It does not make views or custom functionality accessible by itself.

See Accessibility for the documented platform behavior.

Review what the customizer controls​

For each screen, the following questions can guide the review where applicable:

  • Labels, headings, and titles describe their topic or purpose.
  • Meaning is not communicated by color alone.
  • Keyboard users can reach and identify the configured controls and actions.
  • Focus remains visible while users operate the screen.
  • Icons and other non-text content that carry meaning have an equivalent text alternative through the documented component configuration.

These checks support WCAG review. They do not replace testing the complete page or client view.

Clarify device scope before designing​

Clarifying supported desktop, tablet, and mobile variants before deciding on screen content and actions creates a basis. Available space and input method affect what users can reasonably see and do, so a desktop screen is not automatically a mobile design. Reviewing each variant makes this visible.

note

The current variants are not a fully responsive design system. They combine device-specific layouts, touch behavior, and orientation assumptions.

The current design approach assumes landscape for tablet and portrait for mobile. A project that needs another orientation benefits from a separate review.

The Device-specific designs reference documents client detection, technical configuration, supported browser environments, orientation, and the test procedure.

Consult the support matrix when selecting a viewtemplate​

The device and accessibility support matrix is the component-level decision basis for device-specific and accessibility-sensitive use cases. Scope and responsibilities defines the boundary of that status.