Accessibility

Last updated 12 August 2026

Cofound aims to meet WCAG 2.2 level AA. This page says what has been built and checked against that, and what is still outstanding, because a statement with an empty known-issues list is usually one nobody checked.

What is in place

• Keyboard access throughout. Every control is a real button, link or form field rather than a clickable div, so it is reachable and operable by keyboard. Focus is never removed without a visible replacement.
• Skip links. The workspace is a toolbar and three panes, so the first thing a keyboard user reaches is a link straight to the editor rather than every file in the tree.
• Dialogs behave. They trap Tab, close on Escape, return focus to whatever opened them, and are announced as dialogs.
• Landmarks and headings. Each page has one main region, navigation is labelled, and headings descend in order.
• Status is announced. Errors and agent progress use live regions so a screen reader hears them without the user hunting for the change.
• Meaning is never carried by colour alone. Warnings, failures and approval states all carry words as well as a colour.
• Reduced motion is respected. With that preference set, the pulsing progress indicator, panel transitions, cursor movement and skeleton shimmer all stop.
• Layout reflows. The workspace collapses to one column on narrow screens and is usable at 320px without horizontal scrolling; wide content such as command output scrolls inside its own region rather than the page.

What has actually been tested

Honestly: keyboard navigation, focus order, dialog behaviour and reflow have been exercised directly in a browser. The following have not been done, and saying so is more useful than implying otherwise:

• Testing with a screen reader, on any platform
• An automated audit across every page
• Contrast measurement of every colour pair against the 4.5:1 threshold
• Testing with voice control or a switch device

Known issues

• The code editor. It is CodeMirror, and its accessibility is largely CodeMirror's. Editing code in a text area is a hard problem for screen reader users generally, and Cofound has not improved on the default.
• Live cursors. Teammates' cursors are a visual feature with no non-visual equivalent. Who is present is available as text in the presence bar, but where they are pointing is not.
• The agent feed updates rapidly. During a run it changes several times a second. It is grouped so the summary is short, and a verbose screen reader setting may still be noisy.
• The local runner is a terminal program. Its approval prompt is plain text and inherits whatever your terminal provides.

If something blocks you

Email shravan.anand.2026@gmail.com and say what you were trying to do and what got in the way. An accessibility problem that stops you working is treated as a bug rather than a feature request, and you will get a reply within five working days.

Standard and scope

The target is WCAG 2.2 level AA, which is the standard referenced by the UK public sector accessibility regulations, the European standard EN 301 549, and commonly used to assess compliance with the Americans with Disabilities Act. This statement covers the Cofound web application at this deployment. It does not cover GitHub, which handles sign-in, or the content of projects that people build with it.