Accessibility

Last reviewed 2026-04-28

Our commitment

Simply Polished targets conformance with Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. This applies to our marketing site, quote request form, client portal, and owner dashboard. Accessibility is a continuous practice, not a one-time audit; we test with real assistive technology before features ship and run automated accessibility checks on every change to the codebase.

What this looks like in practice

  • Keyboard navigation: every interactive element reachable via Tab, with a visible focus ring on the Warm Taupe Light background.
  • Screen reader support: semantic HTML landmarks, descriptive labels on form controls, and ARIA attributes where native semantics are not sufficient. Tested with VoiceOver (macOS, iOS) and TalkBack (Android).
  • Color contrast: body text on background meets AA at 4.5:1. Headings meet AA at 3:1. See our brand notes for the color tokens and their measured contrast ratios.
  • Responsive text: nothing is locked to a single font size. Browser zoom to 200% keeps the full layout usable without horizontal scrolling on mobile-first widths.
  • Respects your preferences: we honor prefers-reduced-motion and prefers-color-scheme. Our cookie banner respects DNT headers.

Known issues

We are honest about where we fall short. Current known gaps:

  • The owner calendar drag-to-reschedule UI (Phase 4) has not been keyboard-tested yet. It will ship with keyboard + screen reader support before it goes live.
  • Photo upload UI on the quote request form does not yet surface upload progress to screen readers. File size and mime-type errors are announced but progress is not.
  • Some legal documents contain fine-print tables. These pass automated contrast checks but the information density can be hard to parse at small widths. A summary view is a future-pass improvement.

Report an accessibility issue

Found a barrier? Let us know; we treat accessibility reports as priority fixes, not feature requests. Expect a response within two business days.

When reporting, if you can share the page URL, the assistive technology you were using, and what you were trying to do, it helps us reproduce the issue faster. If that’s too much to gather, just tell us what happened; we’ll take it from there.

Assistive technology compatibility

We develop against and test with:

  • macOS / iOS: VoiceOver (latest Safari + Chrome).
  • Android: TalkBack (latest Chrome).
  • Windows: JAWS + NVDA (latest Firefox + Chrome + Edge).

Older browsers and ATs may work but are not part of our active test matrix. If you use one not listed and hit an issue, please let us know; we expand the matrix based on real reports.

What this statement is not

This statement is a snapshot of our current posture. It is not a legal guarantee of conformance. Accessibility is a moving target because standards, assistive technology, and our code all change over time. We review and update this page as the codebase and the guidelines evolve; the “last reviewed” date at the top of this page reflects the most recent check.