Accessibility
Our target
We aim for WCAG 2.2 Level AA across the site: semantic headings and landmarks, labelled form fields, visible keyboard focus, text contrast of at least 4.5:1, touch targets of at least 44 pixels, no content that depends on color alone, reduced motion respected, and every image described in alt text (with renderings identified). Tables have header rows; tools work with a keyboard and announce results.
Known limitations
The permit finder depends on a third-party geocoder; if it is unavailable the tool falls back to a ZIP-code lookup with a note. PDF downloads are not offered; the project brief prints from the page instead.
Report a barrier
Email hello@kissimmeeconcrete.com with the page URL and what happened. We respond within two business days and fix confirmed barriers in the next release.
What we have actually done
Semantic headings in a logical order on every page, with one first-level heading per page. Landmarks for the header, navigation, main content and footer, and a skip link to the main content. Every form field with a visible label tied to it. A visible focus outline with a contrast ratio that meets the requirement, rather than the browser default removed. Text contrast checked against the palette, with the gold used at a darker value for small text than for large. Touch targets of at least forty-four pixels on buttons and links in the mobile layout. Tables with header cells marked as headers. Images with alt text that describes the image, and concept renderings identified as renderings in the alt text rather than only in the caption.
Motion is minimal by design, and what there is respects the reduced-motion preference. The site works without JavaScript for reading; the calculators and the finder need it, and they say so.
Where we know it falls short
The permit finder depends on an external geocoding service, and when that service is unavailable the tool degrades to a ZIP-based answer with a notice rather than failing silently. That is a graceful fallback rather than a fix. The interactive tools produce results that are announced to screen readers, but they have not yet been tested with a range of assistive technologies by anyone other than us, so we describe them as intended to work rather than verified to.
We have not commissioned an independent accessibility audit. When we do, the findings and what we changed will go on this page. Until then, if something on this site is difficult or impossible for you to use, the contact form reaches us and we will fix confirmed barriers in the next release rather than adding them to a list.