Accessibility statement
This site should work for you whether you use a mouse, a keyboard, a screen reader, magnification, or none of those. We aim for WCAG 2.1 Level AA. Here is what has actually been checked, and what has not.
Email [email protected] or call (727) 800-1719 and tell us what page you were on and what happened. Mike reads these himself and aims to reply within 3 business days. If a fix will take longer, we will find another way to get you the information in the meantime.
What has been checked
Verified across all pages on this site, not assumed.
Structure and landmarks
Every page declares its language, has a skip-to-content link as the first focusable element, uses one h1 with headings in order beneath it, and marks up its navigation, main content and footer as landmarks a screen reader can jump between.
Images and controls
Every image carries an alt attribute. The logo marks sit inside links that already say the business name, so they use an empty alt to stay silent rather than repeat it. Every form field has a label, the menu button and embedded calendars carry names, and the FAQ toggles report whether they are open.
Colour contrast
Every text and background pairing in the design was measured against WCAG AA. Two fell short and both were corrected: the colour used for a failing check, and the small grey used for captions. All measured pairings now meet at least 4.5 to 1.
Keyboard use
The site is plain HTML with standard links, buttons and inputs, so tab order follows the page and there are no custom widgets that trap focus. The AI visibility check runs from a normal button and the address field accepts Enter.
Motion
The site honours the reduce motion setting in your operating system. If you have it switched on, the scrolling animation and the moving strip of engine names stop moving.
Not colour alone
The AI visibility check reports results with a written label as well as a colour, so a pass, a warning and a failure are told apart by the words Pass, Fix and Failing, not by red and green.
What has not been checked
known limitsWe are not claiming full WCAG 2.1 AA conformance, because that claim needs a formal audit including testing with real assistive technology, and we have not paid for one. What is above was verified by inspection and measurement. What follows has not been:
- No screen reader testing by a daily user. The markup is built correctly and checked programmatically, but nobody who relies on JAWS, NVDA or VoiceOver has sat down and worked through the site. That is the gap most likely to hide a real problem.
- The booking calendar is a third-party embed. The scheduling widget on our contact and booking pages comes from GoHighLevel. Its accessibility is theirs, not ours, and we cannot fix it directly. If it stops you booking, call (727) 800-1719 or email us and we will book the time for you. That option is not a workaround we are hiding, it is offered on the page itself.
- No formal audit report exists. If you need one for procurement or a compliance review, ask and we will tell you honestly where things stand rather than send you a badge.
We would rather list these plainly than publish a conformance claim we cannot support. If you hit something not mentioned here, telling us is genuinely useful and it gets fixed.
Why this page exists
Title III of the Americans with Disabilities Act has no small business exemption, and Florida is one of the busiest states in the country for website accessibility claims. That is a reason to build the site properly, which we have tried to do.
It is not the main reason. We build websites for other people for a living. It would be a poor advertisement to publish one that a portion of the public cannot use, and a worse one to hide that behind an overlay widget instead of fixing the markup. There is no accessibility overlay on this site. The HTML is the accessibility.
Accessibility of what we build for clients
Sites we build follow the same approach: real HTML structure, labelled controls, described images, contrast measured rather than guessed. If accessibility conformance is a specific requirement for your project, say so before we start so it can be scoped properly, because meeting a standard formally involves testing beyond what is described here.
Tell us what did not work
Page, what you were trying to do, and what happened. That is enough. If you use a screen reader or another assistive tool, saying which one helps us reproduce it.