Adam Alakeli
Menu

Accessibility

Last updated August 26, 2026

This site is meant to be usable with a keyboard, a screen reader, and without motion. The target is Web Content Accessibility Guidelines (WCAG) 2.1 Level AA.

What is already in place

  • Pages declare a language and expose a skip link to the main content.
  • Primary navigation, the mobile menu, and the contact form are labeled.
  • The mobile menu uses a native dialog so focus is trapped and Escape closes it.
  • Motion is reduced when the operating system asks for it.
  • Every route is checked with axe-core against WCAG 2.0/2.1 A and AA in both light and dark themes as part of the test suite.

Known limits

Automated axe checks catch a lot and miss some things — especially screen-reader phrasing and complex interactions. The architecture diagram is readable without JavaScript; pointer enhancements load only as a progressive layer.

Report a barrier

If something on this site is hard to use, email adam@alakeli.com with the page URL and what you were trying to do. I will work to fix it.