Accessibility statement

Suitcast aims to meet the Web Content Accessibility Guidelines, WCAG, version 2.1 at level AA on every public page of suitcast.com, in the logged-in dashboard and in the emails it sends.

• Every public page is tested with axe-core, the same open-source engine the Suitcast scanner uses, against WCAG 2.0 and 2.1 A and AA rules, as part of the checks run before a release.
• The tests run at six screen widths, from a 360px phone to a 1440px desktop, and also check for sideways scrolling, touch targets smaller than 44px, form fields that are too small to read on a phone, and skipped heading levels.
• Text contrast is measured against the colours actually painted on screen, including over gradients.

• Every page can be used with a keyboard alone, with a visible focus outline and a Skip to content link as the first tab stop.
• Pages have one main heading and a heading order without gaps, so a screen reader's headings list reads as an outline.
• Charts, the state map and bar lists have text equivalents, and every table has a caption and header cells.
• Links inside sentences are underlined, so they do not depend on colour.
• Animation is reduced to nothing when your device asks for reduced motion.
• The site loads no third-party scripts, so no outside widget can add a barrier.

• PDF reports are generated as tagged PDFs with an outline, but their reading order has not yet been reviewed with a screen reader.
• Checkout and the billing portal are run by Polar, the merchant of record. Their accessibility is outside Suitcast's control; if they block you, email support and a plan can be set up another way.
• Automated tests cannot catch everything, such as whether alternative text is meaningful. Those parts rely on manual review, which may miss issues.

If anything on suitcast.com is hard or impossible to use, email support@suitcast.com with the page address and what happened. Reports are read by the founder. If you need a report or any content in another format, ask at the same address.

HTML, CSS, WAI-ARIA and JavaScript. Core content, including the lawsuit data, the guides and the policies, is rendered on the server and readable without JavaScript; the scan form needs it.

This statement was last reviewed on the date at the top of the page, using the automated tests and manual checks described above. It is updated whenever the testing or the known limitations change.