Loading…
Last updated · 2026-04-23
An editorial listing is only as good as the number of people who can read it. We design Savvy to meet the Web Content Accessibility Guidelines 2.2 at Level AA — the current benchmark under the ADA and Title III jurisprudence — and we publish the gaps we know about along with a timeline for fixing them.
Every interactive element on Savvy is reachable with the Tab key, operable with Enter or Space, and exits modals with Escape. Focus indicators are visible against both the cream and navy palettes.
Pages use semantic HTML5 landmarks (header, nav, main, footer) and ARIA labels on interactive regions that don't have a text label. Listing galleries carry alt text you wrote, not generic filenames.
Body text on cream backgrounds runs at a measured 11:1 contrast ratio. Navy-on-gold accent chips run at 7:1. Every text-color pair on the platform exceeds WCAG AA thresholds and most exceed AAA.
The anchored parallax hero, ken-burns image drift, and fade-in sections all honor the prefers-reduced-motion media query. If your OS has motion disabled, the platform renders statically.
Text scales fluidly from 360px mobile to 1920px desktop using a modular scale. Long-form text caps line-length at 66 characters for readability and honors browser zoom up to 200% without layout breakage.
Every form field has a persistent label (not a disappearing placeholder), every required field is marked both visually and via aria-required, and errors are announced to screen readers in real time.
An honest disclosure is worth more than a perfect one. The following areas are not yet fully compliant; we are actively working on each.
The interactive territory map (agent dashboard) uses Mapbox GL, which has partial keyboard support. We're building a tabular fallback view for agents who prefer to avoid the canvas interface; ETA summer 2026.
Legacy listings uploaded before April 2026 may still have auto-generated alt text rather than owner-provided descriptions. We are backfilling manually and new listings prompt for real alt text at upload.
Embedded third-party PDFs (Florida seller disclosures, lead-paint addenda) come directly from state and federal sources. We have raised accessibility concerns with the issuing agencies and provide plain-text summaries alongside each PDF.
Automated scans run against every deploy using axe-core and Lighthouse; no merge lands with a new violation. Quarterly we run manual audits with VoiceOver (macOS, iOS), NVDA (Windows), and TalkBack (Android). An external firm performs a full WCAG 2.2 AA audit annually.
Our last external audit: March 2026. Findings and remediations are tracked publicly in our engineering retro notes.
If you encounter a page, interaction, or document that is difficult or impossible to use with your assistive technology, please tell us. We treat accessibility bugs as priority-1 and typically respond within two business days with a target fix date.
Email accessibility@savvyfsbo.com, or use our contact form and select the “Other” topic.