What we test,
and what we have not.

Where we stand

We want this site to work for everyone who wants to read it, including people using a screen reader, a keyboard alone, magnification, or a browser set to larger text or reduced motion.

We measure this rather than assert it. Every page of this site is tested against WCAG 2.2 Level AA on every single build, and the build fails if a page regresses. The result of that test is what this page reports.

Conformance status

This site is partially conformant with WCAG 2.2 Level AA. Partially conformant means most of the standard is met and we are not claiming all of it, because some of the standard cannot be verified by an automated test and we would rather tell you that than imply a clean bill of health.

What we can state precisely: an automated audit of all 32 pages, run on 19 September 2026, reports zero violations of the WCAG 2.2 A and AA rules it is able to check, heading order, image alternatives, form labelling and programmatic error association, landmark structure, reflow to 320px, and every text and interface color measured against the 4.5:1 minimum.

What that does not cover: automated testing catches a minority of accessibility problems. It cannot tell you whether alternative text is meaningful, whether the order you tab through a page makes sense, whether an error message is understandable, or whether a screen reader announces something confusingly. Those need people, and we have not completed a full manual or assistive-technology audit of this site. Until we have, we will not claim full conformance.

What is built in

• A skip link to jump straight to the main content.
• Landmarks and headings in a real order, so a screen reader can navigate by structure.
• Every form field has a visible, associated label, and errors are announced rather than only shown in color.
• Text and interface colors are tested against the 4.5:1 contrast minimum on every build.
• The opening animation and every scroll animation stop when your browser or system asks for reduced motion.
• The site works without JavaScript for reading. Forms need it, because the anti-spam check does, and each one carries a phone number and email address for that reason.
• Keyboard focus is visible, and no part of the site traps focus.
• On 27 August 2026, a manual pass through every form’s error states found that an invalid field was announced to screen readers, but not linked to the visible reason why. That gap is now closed, on every form on the site.

What we know is not done

• No full manual audit with a screen reader has been completed. That is the gap between “zero automated violations” and full conformance, and it is the honest reason this page says partially conformant.
• The forms cannot be submitted without JavaScript, because the bot check requires it. Anyone affected can call or text (954) 952-3611 or email alexalligan@suncoastdigital.us and get the same result from a person.
• Some decorative motion is present by default for visitors who have not expressed a motion preference.

If something does not work for you

Tell us and we will fix it. Email alexalligan@suncoastdigital.us or call or text (954) 952-3611, and say which page and what happened.

We aim to reply within one business day. If something on this site is blocking you from getting an answer, that is our failure, and in the meantime a person on that number will do whatever the page was supposed to do for you.