Accessibility

The standard we aim at

The target is WCAG 2.2 Level AA. That is a target, not an achievement: no independent audit and no assistive-technology test pass has been carried out. The statements below are limited to what has been verified directly.

What has been checked

• Text contrast on the public site. Measured against the page background: body text 18.4:1, secondary text 7.2:1, links 9.3:1. All exceed the 4.5:1 required at AA for normal text.
• Keyboard operation of the public site. The primary navigation is plain HTML links. The “More” menu and the mobile navigation are disclosure buttons that open on Enter, Space or click and close on Escape, returning focus to the button they came from — reachable by keyboard and touch alike, with no hover-only traps. The home page’s view selector is a standard tab widget you move through with the arrow keys. A “skip to content” link is the first thing focused on every page, and there are no focus traps.
• Reduced motion. The stylesheet honours prefers-reduced-motion: the animated indicators stop and hold a legible static state rather than continuing to move.
• Structure. Pages use one h1, ordered headings, landmark elements, and labelled navigation regions. Documentation headings carry stable ids so they can be linked and navigated directly.
• Zoom and reflow. Layout is fluid and text resizes. Wide content — tables, code blocks and diagrams in the documentation — scrolls inside its own container so the page itself never scrolls sideways.
• Images. The home page’s visualizations are live SVG, each exposed to assistive technology as a single labelled image — a role="img" element with a text label describing what it shows — rather than a tangle of unnamed shapes. Decorative marks are hidden from assistive technology rather than announced as meaningless graphics.

Known limitations

These are real and currently unresolved. They are listed rather than omitted.

• The 3D world view is not accessible. The city is rendered to a canvas. It exposes no text alternative, cannot be navigated by keyboard, and is unusable with a screen reader. Anyone who cannot use a pointer and see the canvas cannot use that view. It is the single largest gap here.
• Dark theme only. There is no light mode and no high-contrast theme. The interface does not currently respond to prefers-color-scheme or forced-colours modes.
• Small text in the console. The operator console uses type as small as 10px, some of it at reduced opacity measuring roughly 3.2:1 to 4:1 against the background — below the AA threshold. The public site does not do this; the console does.
• No assistive-technology testing. The site has not been tested with screen readers, voice control or switch access.
• Documentation is unedited. The published notes were written for the author, not for a general reader. Some rely on dense tables and notation.

Reporting a problem

If something here blocks you, write to Cognithamus@proton.me and describe what you were trying to do and what stopped you. Reports about the limitations already listed above are still worth sending — knowing which ones actually block real people is what decides the order they get fixed in.

There is no formal response-time commitment, and it would be dishonest to publish one for a project run by a single person.