How accessible this site is, and what to do if it is not

What we do

• Body text is 18px or larger, and 20px on the accessible living pages.
• Every control can be reached and used with a keyboard, including the file dropzone and the permission matrix.
• Every interactive element is at least 48×48px — twice what AA asks for.
• Nothing important is explained by colour alone, and nothing is revealed only on hover.
• Every input has a visible label that stays visible, and errors say how to fix the problem.
• The site is tested automatically on every change with axe-core, in light and dark, at 390, 768, 1024 and 1440 pixels wide.

What we know is not perfect

10 known shortfalls, all of them the same kind of problem: some smaller grey text sits slightly below the 4.5:1 contrast ratio the standard asks for. We have kept the brand colours as designed and accepted these rather than change them, and we would rather say so than let you find out.

• Captions, timestamps and helper text on the page backgroundMeasured at 4.32:1, against a target of 4.5:1.
• Tinted bands, the portal rail and table headersMeasured at 4.01:1, against a target of 4.5:1.
• Metadata inside filled cardsMeasured at 3.76:1, against a target of 4.5:1.
• Inline links and the current-stage labelMeasured at 2.96:1, against a target of 4.5:1.
• Inline links inside cardsMeasured at 2.58:1, against a target of 4.5:1.
• The primary button — "Book a call" — on every pageMeasured at 3.12:1, against a target of 4.5:1.
• Success alertsMeasured at 2.89:1, against a target of 4.5:1.
• Quota warnings and the unsaved-changes bannerMeasured at 2.07:1, against a target of 4.5:1.
• Failed uploads and destructive confirmationsMeasured at 3.93:1, against a target of 4.5:1.
• Helper text in modals, popovers and widget edit modeMeasured at 4.1:1, against a target of 4.5:1.

Everything else on the site meets the target, and any new contrast problem fails the build rather than reaching you.

Tell me and I will fix it

If something here stops you doing what you came to do, that is a bug and it gets treated like one.

Email admin@smarty-pads.com.

How this was tested

Automated testing with axe-core runs on every change, covering every public page in both themes at four screen widths. A build cannot ship with a new accessibility violation.

Automated testing catches a good share of problems, not all of them. A manual review with assistive technology is planned before launch and this statement will be updated with its date and findings.