Accessibility statement

Goal

The benchmark is the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. Motion only happens while the page loads, while you scroll and with the mouse; with “reduce motion” on your system it is left out, as success criterion 2.3.3 requires.

What is in place

• All content can be reached with the keyboard, focus is visible, and a skip link leads straight to the content.
• No text is smaller than 16 pixels, including the menu, footer and form.
• The page works from a width of 320 pixels without horizontal scrolling.
• The wall of screens at the start and the light in the background are decoration. Everything important is also on the page as text.
• Nothing moves on its own without end: the project screens change when you scroll or press a button below the picture. If “reduce motion” is set on your system, the flight, the cuts and the fades are left out.
• Form fields have visible labels and clear error messages.
• At the top, “House lights” switches between the dark and a light theme. Both meet the WCAG AA contrast requirements.

How it was tested

Automatically with axe in Chromium at three widths (320, 768 and 1440 pixels), in the dark and the light theme, plus tests for font size, horizontal scrolling, third-party requests and keyboard use of the menu. Before every release the same tests also run in Safari and Firefox and on iPhone and iPad (WebKit).

Known limitations

• The case studies of Tallyroom and Evidarium are on GitHub and only available in German.
• Tests with screen readers such as VoiceOver and NVDA are still pending.

Feedback

If you run into a barrier, write to me at kontakt@adambaranyi.xyz and I will take care of it.