Accessibility
What this site aims for, how to change how it looks and moves, and where it still falls short.
What it aims for§
I want every page to work for everyone who visits, whether they use a mouse, a keyboard, a phone, a screen reader or a zoomed-in window. The target is WCAG 2.2 level AA, the web's accessibility standard, and the pages are checked against it (see what was tested below).
This is a personal site built and looked after by one person, and it has not had an audit by an outside specialist. Where it falls short, the limitations section says where.
Reader settings§
The Aa button in the header opens a panel that changes how every page looks and moves. You can also open it from the command palette (press Ctrl or ⌘ and K, then type “reader”). Each choice applies the moment you make it, and a Reset button puts them all back.
- Text size: four steps, from the default to half as large again. Everything on the site grows with it, and pages reflow instead of scrolling sideways.
- Line spacing: normal or relaxed, with a little more room between words and letters in running text.
- Easier-to-read font: sets the text in Atkinson Hyperlegible, a typeface from the Braille Institute designed so that letters that look alike, such as b and d, or I and l and 1, can be told apart. Chinese text keeps your device's own font.
- Reduce motion: stops the moving ink behind the pages, the fades between pages and the animations in the interface. The site already follows your device's reduce-motion setting; this switch is a second, site-only way to ask.
- Higher contrast: a stronger palette in both the light and dark themes. Text meets the AAA level (7 to 1 or better), borders are easy to see, backgrounds are plain, and the moving ink is switched off.
- Underline all links: every link is underlined, not only when you point at it.
Where the settings are kept§
Your choices are kept on your device only: in the browser's storage and in a small cookie named prefs, which holds nothing but the choices (for example text=large) and is used so the server can draw the first page already set, with no flash of the default. Nothing identifies you, and nothing is sent anywhere else. Clearing your browser's site data removes them. The light and dark theme, and the language, are kept the same way.
Your device's own settings§
The site also follows your device: light or dark appearance, reduced motion, reduced transparency and more contrast. A choice made in the reader settings goes on top of them.
What was tested, and when§
Every public page, the demos included, is run through axe-core, an automatic accessibility checker, in a real browser: in English and Chinese, in the light and dark themes, at desktop and phone width, and again with higher contrast and the largest text. The script is scripts/a11y-audit.mjs in the site's code, and the results at the last run were clean apart from the notes below.
Automatic checks find only some of the problems a person would meet. I have also checked by hand that the main pages work with a keyboard alone, that the reader settings take effect on them, and that nothing scrolls sideways on a 390 pixel wide phone screen at the largest text size. I have not tested every page with a screen reader.
Known limitations§
These are the places where the site is not fully accessible, and I would rather say so than leave you to find out.
- Squash and the other arcade games are drawn on a canvas and played in real time. They take keyboard keys as well as the mouse or touch, but a screen reader cannot follow the ball, so they are not playable without sight.
- Pong is drawn on a canvas and is a real-time game. It can be played from the keyboard, but a screen reader only hears the score, not the ball.
- Pool is drawn on a canvas. It can be played from the keyboard (the arrow keys aim and set the power, Enter shoots) and announces what is happening, but it is much harder without sight.
- “You draw, I guess” needs a pointer to draw. The person guessing can play with a keyboard and a screen reader.
- The other board and card games (Chess, Connect Four, Reversi, Battleship, Monopoly, UNO, Dou Dizhu, Wordle, Word Search, Werewolf) are built from ordinary buttons and text, but I have not tested them with a screen reader, and games that deal many cards or squares may be tiring to move through. At the largest text size on a phone, Battleship's squares are a little smaller than the 24 pixels the standard asks for.
- The Aethalides homework planner lets you drag blocks between days. Every block can also be moved a day at a time from the keyboard, but the drag and drop itself is for a pointer.
- The Odysseus demo imitates a Windows feature that is made for a mouse; it is a demonstration, not something you need to use the site.
- The Datacenter Tracker map is a picture of campuses on a map. The same figures are on the page as text, but the map itself is not explorable with a keyboard or screen reader.
- Screenshots in project write-ups have a short description, not a full transcript of what they show. Videos have a short description but no captions.
- The Chinese pages use the Chinese fonts already on your device, so how they look depends on your system. The easier-to-read font setting does not change them.
Keyboard shortcuts§
| Keys | What it does |
|---|---|
| Tab | Moves to the next link or button. Shift and Tab goes back. The first stop on every page is a “Skip to content” link. |
| Ctrl K⌘ K/ | Opens the command palette: jump to a page, search the site, change the theme, language or reader settings, and more. |
| ? | Opens the palette on this list of keys. |
| ↑↓Enter | Moves through the palette's results, and chooses one. |
| Esc | Closes the palette, the reader settings, a game or any other panel that opened over the page. |
| g h | Home |
| g b | Blog |
| g p | Projects |
| g g | Guestbook |
| g c | CV |
| g l | Site lobby |
| g s | Search |
Go to a page without opening the palette: press g, then a letter. This does not work on the home page, where typing plays with the avatar, or while you are in a text field.
Reporting a problem
If something on the site is hard or impossible to use, I want to know. Tell me the page, what you were trying to do, and what got in the way; the device, browser and assistive technology help if you know them. I will reply and fix what I can.