Accessibility Statement
Accessibility practices for Web Design Tampa Florida. We target WCAG 2.1 AA, the legal compliance bar. What that means, what we’ve fixed, what’s still in progress.
This site targets WCAG 2.1 AA compliance — the legal standard for ADA accessibility in the United States. That isn’t a marketing line. It’s the bar Tampa Bay healthcare, legal, government, and education clients get sued for missing, and we won’t ship a site that doesn’t meet it. Here’s what that means for webdesigntampaflorida.org, what we’ve already verified, what’s still being improved, and how to report a problem if you find one.
What WCAG 2.1 AA means
The Web Content Accessibility Guidelines (WCAG) 2.1 AA is the international accessibility standard cited by the U.S. Department of Justice, most state attorneys general, and the courts in ADA Title III cases. Compliance is checked across four pillars:
- Perceivable — content can be presented in ways users can perceive (alt text on images, captions on video, sufficient color contrast)
- Operable — navigation works via keyboard alone, no time traps, no flashing content that triggers seizures
- Understandable — content reads clearly, forms include labels and error guidance, navigation is predictable
- Robust — content works across assistive technologies (screen readers, voice control, switch devices)
AA is the middle tier (A < AA < AAA). It's the level the courts and federal agencies treat as the de facto legal floor. AAA is aspirational; A is incomplete.
What we’ve verified on this site
The following have been audited and pass WCAG 2.1 AA at the time of this writing:
- Color contrast — every text/background combination meets the 4.5:1 ratio for body text and 3:1 for large text. Tested with axe DevTools and WebAIM Contrast Checker.
- Keyboard navigation — every interactive element (links, buttons, form fields, megamenu dropdowns) is reachable with the Tab key. Focus indicators are visible and have at least 3:1 contrast with their background.
- Heading hierarchy — every page has exactly one H1, then logical H2/H3/H4 progression. We don’t skip levels.
- Alt text — every meaningful image has descriptive alt text. Decorative images have empty
alt=""attributes (per WCAG best practice). - Form labels — every form field has a visible
element associated viafor=/id=. Error messages reference the field by name. - Skip-to-content link — first focusable element on every page jumps past the header nav.
- Page titles — every page has a unique, descriptive
tag. - Language declaration — every page declares
lang="en-US"on theelement. - ARIA landmarks —
,,,,are semantic; ARIA landmarks are used where semantic HTML can’t carry the meaning.
What’s still in progress
We’re honest about this part:
- Video captions — if we add video content in the future (we don’t currently embed any), every video will ship with captions and a text transcript.
- Mobile screen-reader testing — we’ve verified VoiceOver on desktop Safari and NVDA on Windows. Mobile VoiceOver (iOS) and TalkBack (Android) testing is in our quarterly QA cycle, not every release.
- Color-blind variant testing — primary brand colors test clean for Deuteranopia and Protanopia. Tritanopia testing is pending.
How we test
Three layers:
- Automated tools — axe DevTools, WAVE, and Lighthouse Accessibility in our pre-launch QA. Catches ~30-50% of issues.
- Manual keyboard + screen-reader testing — we Tab through every page and read the first three sections aloud with NVDA before launch.
- Color contrast spot-checks — WebAIM contrast checker on every text/background combination in the design system.
We don’t claim 100% perfection. We claim a documented process, a published statement, and a fast response when problems are reported.
Found a problem? Tell us.
If you encounter any accessibility barrier on this site — anything that prevents you from using a page, reading content, or completing a form — we want to know.
Email: hello@webdesigntampaflorida.com (subject line: “Accessibility”) Response window: One business day for acknowledgment; remediation timeline depends on severity (critical issues fixed within 5 business days, non-critical within 30 days).
When reporting, include if you can:
- The URL where the problem occurred
- Your browser, operating system, and assistive technology (if any)
- A description of what went wrong (or what you expected to happen)
We treat accessibility reports as bug reports, not customer service complaints. They go straight to the engineering queue.
Third-party content
We use third-party services that have their own accessibility commitments:
- Google Analytics — admin-only; never shown to public visitors
- Gravity Forms — form fields meet WCAG 2.1 AA when configured correctly; we configure them that way
- Google Fonts — we self-host critical fonts via
display=swapso screen readers don’t wait
We monitor these dependencies; if a third-party update introduces an accessibility regression, we work around it or replace the dependency.
Our broader accessibility practice
This statement isn’t just about our own site. We offer a WCAG 2.1 AA accessibility audit and fix service for Tampa Bay businesses — particularly healthcare, legal, government, and education clients who face direct ADA exposure. If you’re a Tampa Bay business that wants to know whether your current site meets the bar, send us a 5-minute brief or get the $500 SEO audit (which includes an accessibility scan).
This statement was last updated 2026-05-14.
Want this applied to your Tampa business?
If you’re working through this for a real Tampa project, get a written diagnostic instead of guessing. The $500 SEO audit is refundable against any build engagement.