accessibility

Last reviewed 2026-10-09.

The target for this site is the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. Its pages are plain HTML and CSS, each with a skip link, landmarks and one first-level heading. Prose and code are HTML text, links are underlined or set apart in the header, and each figure in a paper has a table of its numbers that opens under it.

how it was checked

On 2026-10-09 every page was checked in Chromium three ways: with axe-core 4.10.3 against its WCAG 2.2 level A and AA rules at 1000 px wide, for horizontal scrolling at 390 px wide, and with JavaScript turned off. That run found the known issues below.

without JavaScript

Every page reads without JavaScript. Running a program needs JavaScript: the Run box on each paper and the workspace on the examples page load a Python runtime, about 12 MB, on the first run. Without JavaScript, each program link still opens the program's source as text, and each paper still gives its results in text and tables.

known issues

• The examples page is a code editor built for a keyboard and a pointer. Its file tree and tabs have targets smaller than 24 by 24 px, its list of open files does not yet follow the ARIA tab pattern, and the line numbers in its gutter have less than 4.5:1 contrast.
• Without JavaScript on a narrow screen, the examples page shows its empty editor rather than its list of programs. On a wide screen the list appears, and each entry opens the program's source.
• On the releases and news pages, the headings skip the second level below the page title.

report a problem

Write to i64systems@proton.me with the address of the page and the problem you met. The author reads mail weekly.