Accessibility

Accessibility is one of our founding principles, so this page says plainly what has been checked on this website, what has not, and what we know is still wrong.

Our target

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. That is a target, not a claim of conformance or a certification.

What has been checked

These checks were run on 14 November 2026 by Claude, the AI agent that built this website, on a local build of the same code, using automated tools and a review of the code. They were not carried out by an independent reviewer or by disabled people.

This check found four problems that an earlier check, made by reading the code, had missed. All four were fixed the same day: the contribution chooser and the project filters showed no outline when reached by keyboard; the home and governance pages scrolled sideways slightly on the narrowest phones; the home link in the header was shorter than 24 pixels on phones; and the protocol page had two regions with the same name. We say so because a clean report is worth less than an honest one.

  • Colour contrast was measured for every text and background pair in both themes. Body text is at least 4.5:1, and control borders, focus outlines and meaningful graphics are at least 3:1.
  • All interactive parts can be used with a keyboard: the menu, the stage explorer (arrow keys), the contribution chooser, project filters and expandable sections. Every keyboard stop on every page was visited in a browser to confirm that it shows a focus outline and is not hidden behind the header.
  • Each page has one main heading, a logical heading order, labelled landmarks, a skip link and its own page title. Focus moves to the new content when you change page.
  • Icons that carry meaning have text alternatives. Links that leave the site say where they lead. Statuses use words and icons, never colour alone.
  • Animation is limited to one sequence on the home page, and it is switched off when your device asks for reduced motion.
  • Layouts were checked at widths from 320 to 1440 pixels, in light and dark themes, with no sideways scrolling, and again at 320 pixels with the wider line, letter and word spacing that WCAG asks websites to allow.
  • Links and buttons are at least 24 by 24 pixels, and most are 44 pixels or more. Links inside a sentence are the height of the text.
  • An automated scan with axe-core (WCAG 2.0, 2.1 and 2.2 rules at levels A and AA, plus best practices) found no issues on any page, in either theme, at phone and desktop widths. Automated tools catch only some problems.

What has not been checked yet

  • Testing with disabled people using their own assistive technology.
  • Manual testing with screen readers such as NVDA, JAWS, VoiceOver and TalkBack.
  • An independent accessibility audit.
  • Translations. The site is currently in English only.

Known limitations

  • The site needs JavaScript, because Base44 runs it as a JavaScript application. Without it you will see a short summary with links to the same information on GitHub.
  • Most links lead to GitHub, whose accessibility is outside our control.
  • Some project information is entered by maintainers in a data editor, so new entries may not always follow these conventions until they are reviewed.

Tell us about a problem

If something on this website is hard to use, please open an issue on GitHub describing the page, what you were trying to do and what went wrong. You need a free GitHub account, and issues are public, so please do not include personal information. If you would rather not post in public, email contact@comutability.org.

Report an accessibility problem (on GitHub)