Accessibility statement.
We want this site to work for everybody who lands on it, including people using a screen reader, a keyboard on its own, magnification, or a browser turned up to a much larger text size than we designed at. This page sets out the standard we build to, where we currently fall short, and how to tell us when something is broken.
The standard we build to.
There is no certificate for this, and anyone selling you one is selling you something else.
We aim to meet WCAG 2.1 Level AA, the Web Content Accessibility Guidelines published by the W3C. It is the benchmark that courts, regulators and settlement agreements in the United States consistently point at, and in April 2024 the Department of Justice adopted it formally for state and local government websites under Title II of the ADA. That rule does not bind private businesses like ours, but it is the same standard we would be measured against, so it is the one we work to.
No government body certifies a website as accessible, and no plugin, widget or overlay can make an inaccessible site conformant, which is why this site does not use one. Accessibility is a property of the underlying markup, colour and behaviour of the page. So rather than claim a badge, we test, we publish what we find, and we fix it.
Conformance is something you work at continuously, not a box you tick once. This page gets updated when the site does.
What we actually do.
The measures already in place, not a list of intentions.
Semantic, hand-written markup
Every page is built by hand rather than assembled by a page builder. Headings, lists, landmarks and form labels describe real structure, so a screen reader reads the page in an order that makes sense.
Keyboard operable throughout
Navigation, the mega menu, tabs, accordions and forms can all be reached and operated with a keyboard alone, and a visible focus outline follows you as you go.
Colour contrast tested, not eyeballed
We audit contrast with axe-core against the WCAG 2.1 AA thresholds — 4.5:1 for normal text, 3:1 for large text and interface components — and treat a failure as a bug rather than a design preference.
Links that do not depend on colour
Links inside body copy carry a persistent underline, so they stay identifiable to anyone who cannot pick them out by colour alone.
Text alternatives and sensible zoom
Meaningful images carry alternative text and decorative ones are hidden from assistive technology. Layouts are fluid, so the page reflows rather than breaking when text is enlarged.
Automated auditing on an ongoing basis
We run axe-core and Lighthouse across the site and re-run them after design changes, because the usual way a site regresses is quietly, one edit at a time.
Where we currently fall short.
Publishing the gaps is more use to you than claiming there are none.
Automated testing only catches part of it. Tools like axe-core and Lighthouse reliably find perhaps a third to a half of WCAG issues. A page can return zero automated errors and still be awkward to complete with a screen reader. We treat a clean automated run as a floor rather than as proof, and we are working through manual keyboard and screen reader passes.
Third-party components. Parts of this site are provided by outside services — the cookie consent banner, embedded legal policies, analytics. We do not control their markup, and some of them do not fully meet the contrast and keyboard expectations we hold our own code to. Where a third-party component blocks you from doing something, tell us and we will give you another way to do it.
Older content. Some material published before we tightened this process may not yet meet the standard. We are working back through it.
Tell us what is not working.
A real person reads these, and you will get an answer.
If any part of this site stops you getting what you came for, we want to hear about it. Use the form, email hello@cre8mysite.com, or text 985-981-6256, whichever is easiest for you. It helps if you can tell us the page, what you were trying to do, and what you browse with, but send it either way if that is a hassle.
We aim to acknowledge every report within two business days and to tell you what we are going to do about it and roughly when, or to say plainly if it is a third-party component we cannot fix directly. If something is blocking you right now, we will find another way to get you the information or complete the job for you over the phone.
If the form itself gives you trouble, that is a problem we want to hear about too. Email or text instead.
This statement applies to www.cre8mysite.com. Last reviewed September 11, 2026. Prepared by Cre8 My Site on the basis of our own testing with axe-core and Lighthouse.