Skip to content

Last updated 21 November 2026

Accessibility

Where Smith stands against WCAG 2.2 AA, what we know is still missing, and how to ask for an accommodation.

1. Our target

Smith aims to meet WCAG 2.2 level AA across the marketing site and the signed-in workspace. That means text contrast of at least 4.5:1, full keyboard operation, visible focus, labelled form controls, and no content that depends on colour alone.

2. What works today

Every page has a skip link as its first focusable element, one main landmark, and headings in order. Dialogs trap focus and close on Escape. The chat, checks and settings screens can be operated without a mouse, and animated elements respect the reduced-motion preference.

3. Known gaps

Charts and status badges carry text labels, but their colour coding is not yet fully described to screen readers in every view.

Some marketing illustrations have no long description, only short alternative text.

The screenshot viewer shows a captured image of a page; the text inside that image is not machine-readable, so we always describe the finding in words next to it.

Long tables on small screens scroll horizontally rather than reflowing into cards.

4. Last review

Last reviewed 21 November 2026, covering the landing page, sign-in, onboarding, checks, incidents, chat, billing and the legal pages. We re-review after any change to navigation, forms or the chat composer.

5. Requesting an accommodation

If any part of Smith blocks you, email accessibility@smith-ops-agent.base44.app with the page and what happened. We reply within two business days, and we will give you the information or the alternative route you need while a fix is in progress.

If you are a customer with a documented need, we can also provide checks, incidents and evidence exports in a plain-text format on request.

Still have a question? Visit the help centre.