Accessibility.

This site aims to meet WCAG 2.2 at level AA. What I checked, what isn't in my hands, and how to tell me when something doesn't work for you.

Last checked .

Where the site stands

As far as my checks reach, this site meets the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. That is my own assessment. Nobody else has audited the site.

What I checked

On 1 November 2026 I checked all 29 pages: the home page, About, Skills, the blog index, all 19 posts, the five project pages and this one.

  • Automated tests. axe-core 4.11 with its rules for WCAG 2.0, 2.1 and 2.2 at levels A and AA, in the light and the dark theme, 1440 and 390 pixels wide. No violations.
  • Keyboard. Every page with the Tab key only. The first stop is a link that skips to the content. Every stop has a visible focus ring, none is hidden behind the fixed navigation, and the order follows the page from top to bottom.
  • Small screens and zoom. At 320 pixels wide, which is what a 1280 pixel screen shows at 400 percent zoom, no page scrolls sideways.
  • Text spacing. With the line, paragraph, letter and word spacing from WCAG 1.4.12, no text is cut off.
  • Target size. Links and buttons outside running text are at least 24 by 24 pixels.
  • Motion. With reduced motion switched on in the system settings, nothing moves. Without it, the entrance animations take under a second, and nothing blinks or loops.
  • Language. Every page is marked as English. German and French quotes in the posts carry their own language, so a screen reader switches its pronunciation for them.
  • Screen reader. Tested with VoiceOver on macOS.

What the site does

  • The theme follows your system setting. The button in the navigation switches between light and dark, and the site remembers your choice.
  • Every page works without JavaScript. Only the theme button needs it.
  • Screenshots have text alternatives. Illustrations that only decorate are hidden from screen readers.

What isn't in my hands

Many posts link to laws, court decisions and studies, often as PDFs. I don't control those documents and can't vouch for their accessibility. If a source doesn't work for you, write to me and I'll tell you what it says.

Tell me when something doesn't work

Write to hello@danielkosbab.com. Say which page and what happened. Your browser and assistive technology help me reproduce it, if you want to share them.

Why this page exists

This is a personal site. The European Accessibility Act and the German BFSG cover products and services for consumers, and the EU's Web Accessibility Directive covers public bodies. No law asks me for this statement. I write about other people's sites, though, so mine should be open to the same questions.

Technical details

The site is built with Next.js and served as static HTML. It relies on HTML, CSS and WAI-ARIA. I tested in Chromium on macOS, the engine behind Chrome and Edge.