Skip to content
Nathan Zhou

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.

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.

Keyboard shortcuts§

KeysWhat it does
TabMoves 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.
↑↓EnterMoves through the palette's results, and chooses one.
EscCloses the palette, the reader settings, a game or any other panel that opened over the page.
g hHome
g bBlog
g pProjects
g gGuestbook
g cCV
g lSite lobby
g sSearch

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.

Email me