Accessibility
Accessibility statement
I want everyone to be able to read this site, whatever their device, browser or assistive technology. This page says what it aims for, what has been checked, and how to tell me when something gets in the way.
Target
The site aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. It is a small static site: three pages, no forms, no video, no third-party widgets.
What is in place
- Keyboard. Every page can be used without a mouse. A "Skip to content" link appears on the first Tab and focus is always visible; both were checked in the browser. The theme button and the expandable work history are native HTML buttons and disclosure widgets, so they respond to Enter and Space, and nothing traps focus.
- Structure and names. Landmarks (header, navigation, main, footer), heading order, and link and button names were reviewed in the browser's accessibility tree. Each page has one
h1and a declared language. The animated line under my name is hidden from assistive technology and replaced by a static list of the same words. - Colour contrast, light and dark theme. Every visible text element on every page was measured against its actual background, in both themes. All pass the 4.5:1 minimum; the lowest is 4.75:1 and body text is above 10:1.
- Colour is never the only signal. For example, the current page in the navigation is underlined as well as coloured.
- Motion. When the operating system asks for reduced motion, animations and hover movements are switched off and the typing effect stays still. Without JavaScript the content stays fully visible: the typing line shows its first role and the work history works as plain disclosure widgets.
Known limitations
- The site has not yet been tested with a screen reader such as VoiceOver or NVDA. The review so far used the browser's accessibility tree.
- The short line under my name contains emoji; screen readers announce their names.
- External links open in a new tab, which is stated by the browser rather than in the link text.
Tell me about a problem
If something on this site is hard to use, I would like to know. Reach me on LinkedIn or GitHub, and say which page and what you were trying to do. I will answer and fix what I can.
Last reviewed on 2026-10-28.