Accessibility Statement
Last updated: May 26, 2026
Our commitment
I want every visitor to be able to read, navigate, and contact me, regardless of ability or the assistive technology they use. This site is built with accessibility in mind and is continuously improved as standards evolve and as I learn about real barriers visitors run into.
Standards we follow
This website aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, the standard referenced by the Americans with Disabilities Act (ADA) and Section 508 of the Rehabilitation Act. I also follow general best practices from the U.S. Access Board and the ARIA Authoring Practices Guide.
What's in place today
- Semantic HTML landmarks (header, nav, main, footer) on every page.
- A single
<main>region per page so screen readers can jump straight to content. lang="en"set on the page so screen readers pronounce content correctly.- Descriptive alt text on meaningful images, and empty alt text on decorative ones.
- Accessible names on icon-only buttons (menu toggles, close buttons, logo link).
- Visible focus styles inherited from the browser and theme tokens, so keyboard users can see where they are.
- Color tokens chosen to meet WCAG AA contrast against the dark background.
- Responsive layouts that work down to small mobile widths without horizontal scrolling.
- Breadcrumb navigation with proper
aria-labeland structured-data markup on city pages. - Forms (where present) use real
<label>associations, not placeholder-only labels. - Links open in the same tab by default. External links that open in a new tab are clearly indicated.
Known limitations
I'm honest about the gaps so you know what to expect:
- Desktop mega-menus (Services and Industries) currently open on hover. I'm migrating them to a click-and-keyboard pattern with full
aria-expandedsupport. In the meantime, every link inside those menus is also reachable from the mobile menu (which works with keyboard and screen reader) and from the footer. - Older blog post images from posts dating back to 2009 may have generic or missing alt text. New posts are written with descriptive alternatives.
- Third-party embeds (YouTube, social previews, analytics widgets) inherit the accessibility of the provider and may not fully meet WCAG 2.1 AA.
Assistive technology compatibility
The site is tested with the current versions of:
- Chrome, Safari, Firefox, and Edge on desktop and mobile.
- VoiceOver on macOS and iOS.
- NVDA on Windows.
- Keyboard-only navigation (Tab, Shift+Tab, Enter, Space, Esc).
- 200% browser zoom and OS-level text scaling.
Report an accessibility issue
If you hit a barrier on this site, please tell me. I take accessibility reports seriously and aim to respond within 5 business days, with a fix or a plan to fix it shortly after.
Email: stuart@stuartcmchenry.com
Please include the page URL, what you were trying to do, what went wrong, and the assistive technology and browser you were using. Screenshots or short screen recordings help a lot.
Formal complaints
If you'd like to file a formal ADA complaint, you can do so with the U.S. Department of Justice at ada.gov/file-a-complaint. I'd appreciate the chance to fix the issue first, but it's your right.
Ongoing work
Accessibility isn't a one-and-done task. I review the site periodically with automated tooling (axe, Lighthouse) and manual keyboard + screen reader testing, and I update this statement when meaningful changes ship.
