Accessibility

What we aim for, how we check it, what we know falls short, and how to tell us when something does not work for you.

Last updated

Our goal

We want sailfork.com to work with a keyboard, a screen reader, zoom and reduced motion. The standard we aim for is the Web Content Accessibility Guidelines (WCAG) 2.2, level AA.

We have not had an independent audit, so we do not claim that the site conforms. This page says what we do and what we know is missing.

How we check

Every page has a skip link to the main content and a visible focus outline. The code is checked for accessibility warnings before it ships.

An automated test (axe-core, WCAG 2.2 A and AA rules) runs against the public pages at desktop and phone widths: the home page, product, documentation, pricing, contact, sign-in, sign-up and legal pages. Automated tests find only part of the problems, so they do not replace trying the site with assistive technology.

What we know falls short

The signed-in app (repositories, pull requests, settings, the admin area) is not covered by the automated test, because it draws itself in the browser from live data. We have not reviewed it for accessibility to the same standard as the public pages.

We have not reviewed code and diff views or CI log output with a screen reader. Repository files you view are shown as they are written, including images that have no text description.

Tell us about a problem

If something on Sailfork is hard or impossible for you to use, send us the page, what you were trying to do and the browser or assistive technology you use. Use the contact page and pick "Something else".

We read every message and reply within one business day. We fix what blocks you first and tell you when it is fixed.

Questions about this page go through the contact page. Fenil, who runs Sailfork, reads every message.

Loading Sailfork