Accessibility Statement

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA.

WCAG 2.2 AA includes every requirement of earlier versions. Meeting it also meets:

• WCAG 2.1 Level AA, the standard named by the US Department of Justice rule under ADA Title II; and
• WCAG 2.0 Level AA, the standard incorporated by the Section 508 standards (US Rehabilitation Act).

• the firstcode.ai marketing website (also served at firstcode.dev);
• the FirstCode web app;
• the FirstCode desktop app; and
• the FirstCode mobile app (iOS and Android).

FirstCode.AI is partially conformant with WCAG 2.2 Level AA. Some parts of the content do not yet fully meet the standard.

We completed an accessibility audit of all four surfaces on 23 October 2026. Remediation is in progress, and we will update this statement as fixes ship.

These are the main issues we know about and are working on:

• Marketing website. Automated scans of every page report no serious or critical issues as of 26 October 2026, after fixes to text contrast, control names, link styling and the animated product previews, which now have a Pause button. A full manual screen-reader review of the site has not been completed yet.
• Web app. On the project, board, ticket, chat and Git-connection screens, some secondary text is below the required contrast, some controls' accessible names do not match their visible labels, some small controls are under the 24 by 24 pixel minimum, and a few drop-downs and buttons have no accessible name. The sign-up, invitation and sign-in pages had no automated findings.
• Desktop app. With a terminal open, the terminal tab strip is not exposed correctly to assistive technology (each tab contains its own close button, and the close button is smaller than the minimum target size). Some dialogs move focus automatically when they open, and some click-only areas, such as dialog backdrops, have no keyboard equivalent, although Escape closes them. Terminal output is announced through xterm.js's screen-reader mode. It turns on automatically when the operating system reports a screen reader, and you can switch it on or off under More → Screen reader mode in the terminal toolbar. To move focus out of a terminal, press Shift+Escape.
• Mobile app. Some chat controls (reaction chips, the replies link and some composer buttons) and a few buttons elsewhere are smaller than the recommended touch-target size. Some secondary text, mostly in the dark theme, is below the required contrast. Some buttons and chips have their name read twice by TalkBack and VoiceOver. Creating a project and connecting Git are completed in the web app.

Third-party content

Live captioning in Google Meet meetings used with FirstCode is provided by Google, and is outside the scope of this statement. Our marketing website does not host prerecorded or live audio or video.

• Automated testing. We scan rendered pages with axe-core against WCAG 2.0, 2.1 and 2.2 A/AA rules. We also run accessibility lint rules (eslint-plugin-jsx-a11y) as a build gate, so new violations in our web code fail the build.
• Manual testing. We check keyboard-only navigation, focus visibility, reduced-motion behaviour and colour contrast by hand. We also run a scripted screen-reader pass over the main user journey with NVDA on Windows, VoiceOver on macOS and iOS, and TalkBack on Android.

If you have trouble using any part of FirstCode.AI, or need information in a different format, please tell us:

• Email: contact@firstcode.dev. Put "Accessibility" in the subject line.

Please include the page or screen, what you were trying to do, and the browser or assistive technology you use if you can.

We aim to respond within 5 business days. If you need it, we will offer a workaround or provide the information another way while we work on a fix.

This statement was prepared on 23 October 2026, based on an audit completed the same day. It was last reviewed on 26 October 2026.