Accessibility
Built to be used by everyone
We want this site to work for you whatever you are using to read it: a screen reader, a keyboard on its own, a magnifier, voice control, or a phone in bright sunlight. This page says what we have done about that, and what we have not done yet.
Last reviewed July 25, 2026.
The standard we build to
We aim to meet WCAG 2.1 Level AA. The Web Content Accessibility Guidelines are the international rulebook for making websites usable by people with disabilities, and Level AA is the middle of its three levels. It is the level most laws and most large organizations ask for.
We say "aim to meet" on purpose. Nobody has independently audited this site, so we are describing a target and the work behind it, not claiming a certificate. Where we fall short we say so further down this page, by name.
What is in place today
None of this is a plan. Every item below is in the site you are reading right now.
Real headings and landmarks
Pages are built from ordinary HTML: one main heading per page, headings in order beneath it, and named regions for the header, the navigation, the main content, and the footer. Screen reader users can jump straight to what they came for.
A skip link
The first thing keyboard users reach on every page is a "Skip to content" link that jumps past the navigation.
Everything works from the keyboard
Every link, button, form field, and menu can be reached and operated with the Tab and Enter keys alone. No part of the site needs a mouse.
Menus close with Escape
The mobile menu and the drop-down menus in the header both close when you press Escape, and focus goes back to the link or button that opened them. A menu can never trap you.
You can always see where you are
Anything you move focus to gets a thick blue outline. We never hide the focus ring to make a design look tidier.
Contrast-checked colors
The palette was chosen against the WCAG contrast ratios rather than by eye, so body text, headings, and buttons stay readable in bright light and on older screens.
Motion respects your settings
If your device asks for reduced motion, the site turns off its transitions and its smooth scrolling. You do not have to ask us twice.
Text for anything that carries meaning
Images have alternative text. The small illustrative icons and shapes are decorative only, so they are hidden from screen readers instead of read out as noise. Nothing on this site says something in a graphic that it does not also say in words.
Forms that explain themselves
Every form field has a label attached. One of them — the newsletter box in the footer — uses a label that is hidden visually but read aloud by screen readers. Hints are wired to the field they describe, the contact form explains in words which fields are required rather than relying on the asterisk alone, and errors come from the browser so they arrive the way you already expect them to.
The calculator announces itself politely
The results panel on the ROI calculator is announced to screen readers as it changes, with a short pause built in, so it waits until you stop typing instead of interrupting every keystroke.
Sized for hands and for zoom
Primary buttons and the mobile menu controls are at least 44 pixels tall — the size recommended for touch. The layout reflows down to a small phone without side-scrolling, and text can be enlarged in the browser without the page breaking.
What is not right yet
Publishing the gaps is the honest half of an accessibility statement. These are the ones we know about.
The mobile menu does not hold focus
When the mobile menu is open, pressing Tab enough times will walk into the page behind it rather than looping inside the panel. Escape closes the menu and returns focus to the button, so nobody is stuck, but this does not yet meet the standard we want. It is on the list to fix.
Some typed numbers look wrong when they are not
A few boxes in the ROI calculator step in fives, such as the hourly rate and the percentages. If you type a figure in between, like 77, some browsers mark the box as invalid even though the calculator accepts the number and uses it. The math is right; the styling is misleading.
The guides are not documents yet
Our guides are requested by email today rather than downloaded as files. When we publish them as PDFs we will tag them properly for screen readers, and we will say so here.
We have not had an independent audit
This statement is based on our own testing with a keyboard, a screen reader, and browser tools, not on a formal audit by an outside specialist. We would rather tell you that than imply a certification we do not have.
Tools we have not added yet
There is no booking calendar and no chat window on this site at the moment. When we add them, they will come from other companies, and we will not control their code. We will test them before switching them on, and there will always be a phone number and an email address as a way around them.
If something gets in your way, tell us
This is the part we mean most. If a page will not work for you, we want to hear about it, and we would rather hear about it than have you give up and leave. You do not need to know the technical name for the problem.
It helps if you can tell us:
- The address of the page, or roughly where you were.
- What you were trying to do.
- What happened instead.
- What you were using, if you know: a browser, a phone, a screen reader.
Any of these reach a person:
- Email: Matthew@mleca.com
- Phone: 929-919-3574
- Or use the contact page.
We will reply, tell you what we found, and say when we can fix it. If a fix will take a while, we will give you another way to get what you needed in the meantime, by phone or by email. Booking the free audit never depends on being able to use this website.
See also our privacy policy and our terms of use.