01. What I am aiming for
I build websites for a living. Running one that people cannot use would be poor form.
The target here is WCAG 2.2 at Level AA. That is the Web Content Accessibility Guidelines, and it is what regulators and clients almost always mean when they say "accessible".
02. How this site measures up
Partially conformant with WCAG 2.2 Level AA. Partially conformant means most of the site meets the standard and some of it does not. Section 04 names the parts that do not. I would rather publish that list than claim a clean sheet I have not earned.
03. What has been done
- You can use the whole site with a keyboard. Every link, button, and form field is reachable by tabbing, in an order that follows the page.
- Focus is always visible. Whatever you have tabbed to gets a solid terracotta outline, set far enough out that the element's own border does not swallow it.
- There is a skip link. Press Tab on the home page and the first thing you reach is "Skip to content", which jumps past the navigation.
- The markup describes itself. Headings run in order without skipping a level, and the page uses real landmarks and real lists rather than styled divs.
- Decoration stays quiet. The fake browser chrome around the screenshots, the green status dot, and the "MC" mark are all hidden from screen readers instead of being read out as noise.
- Images carry real alternative text. Both screenshots are described by what they show rather than by their filename.
- Every form field has a visible label joined to its input, so clicking the label focuses the field and a screen reader announces it. Fields also say what they expect, which lets your browser fill in your name and email for you.
- Text contrast meets AA. I calculated the ratios for body text, muted text, and the terracotta accent against the exact backgrounds they sit on. None of it was eyeballed.
- Animation can be switched off. Set your device to reduce motion and the fade-ins, the smooth scrolling, and the hover movements all stop. Content appears immediately instead.
- The page survives zooming. Text is sized in relative units and the layout reflows, so zooming to 200% cuts nothing off and forces no sideways scrolling.
- Nothing moves, flashes, or plays on its own. No carousel, no autoplaying video, no pop-up, no timed interruption.
04. Where it falls short
- The forms on the home page do not submit. Both the domain check form and the contact form throw away what you type. That fails everyone equally, and I am fixing it. Until it is done, email john@mundroffcomputers.com. That address works and I read it.
- Those forms have no status messages. Past the browser's own "please fill in this field" prompts, nothing announces success or failure to a screen reader. I will add that when I wire the forms up.
- Dark mode ignores your system setting. The site opens in its light theme for everyone and only goes dark when you press the toggle at the bottom right. That is deliberate, but it does mean an operating system set to dark will not carry over, and the toggle is missing from the policy pages.
- The policy pages are plainer than the home page. This page, the privacy policy, and the terms have no skip link and no theme toggle. They are single-column documents, so a skip link would save you very little, but the difference is worth stating.
- Nobody independent has checked any of this. Section 05 explains what that means for how much weight to put on section 03.
05. How this was tested
By me, on this site. Keyboard-only navigation, browser zoom, the automated checks built into Chrome, and contrast ratios worked out by hand from the actual palette values.
No independent accessibility specialist has audited it. Nobody who uses JAWS, NVDA, or VoiceOver daily has sat down and worked through it end to end. And automated tools miss most of what matters: a checker can tell you alternative text exists, but not whether it describes anything useful.
So read section 03 as a careful self-assessment. It is not certification, and I am not going to dress it up as one.
06. Tell me if something does not work
If any part of this site is hard or impossible for you to use, email john@mundroffcomputers.com. Tell me which page you were on, what you were trying to do, and what stopped you. Your browser, device, or assistive software helps if you know it, but do not let not knowing stop you writing.
I aim to reply within two business days. Quick fixes I will simply make, then tell you when they are live. Anything slower and I will tell you what I am doing and roughly when to expect it.
Need something here in another format, such as the terms as plain text? Ask and I will send it.
07. Accessibility in the sites I build
Client work gets the same treatment. Semantic markup, keyboard operability, visible focus, labeled forms, contrast calculated rather than assumed, and alternative text written during the build instead of bolted on at the end.
Two things I will not sell you. I will not guarantee legal compliance, and I will not install an accessibility overlay widget. Overlays load after the page does and try to patch problems from the outside with JavaScript, which is why they so often break the screen readers they claim to help. Fixing the markup costs about the same and actually works.
If your business has a legal obligation to meet a specific standard, budget for an independent audit on top of the build. I will build to the standard and then work through whatever the audit turns up.
08. Changes to this statement
I review this page whenever the site changes in a way that matters, and at least once a year. Revisions get posted here with a new "last updated" date.
When something in section 04 gets fixed it moves up to section 03. Nothing quietly disappears.