Skip to content

Accessibility

Last updated 12 October 2026

We want Gitmayo to be usable by people with different abilities. Our target for the web application is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. We have not established full conformance or obtained accessibility certification.

What we assessed

On 11 October 2026, we reviewed the landing, accessibility, privacy, terms and contact pages in an isolated development environment. Internal checks included automated axe tests, keyboard skip-link and content focus, and reflow at 320 and 1280 pixels with reduced motion enabled. We also reviewed headings, focus styles, image alternatives and colour tokens in the source. This limited assessment is not a complete audit of the deployed application.

On 12 October 2026, we also checked the authenticated terms-agreement notice in an isolated development environment: the unchecked agreement requirement, keyboard operation, reflow at 320 pixels with reduced motion, and automated axe checks. This does not establish conformance of the complete deployed sign-in or account journeys.

Known limitations

  • The complete signed-in reporting, investor, authentication and delivery journeys still need assessment with assistive technologies.
  • Downloaded PDF and PowerPoint reports have not been assessed for complete accessibility, including reading order and tagging.
  • GitHub sign-in and other third-party pages have separate accessibility behavior.

Feedback and help

Email our published support contact at support@gitmayo.com or use the contact form to report an accessibility barrier or request help accessing a report. Include the page or task, what happened, and any browser or assistive technology details you are comfortable sharing. Please do not include passwords or private repository content.

We will update this statement as we assess more journeys and address reported barriers.