Our commitment
Kuhn Consulting LLC wants this site to work for everyone who comes to it, including people who browse with a screen reader, navigate by keyboard, use voice control, or rely on zoom and high-contrast settings. Accessibility is part of the job, not a box we check at the end. That applies to this site and to the software we build for clients.
This statement covers kuhnconsulting.co and its subpages, including the blog.
Standard we work to
We aim for the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, published by the W3C. Those guidelines are also the yardstick most commonly used to judge whether a website meets the expectations of the Americans with Disabilities Act (ADA) and Section 508.
To be straight with you: this site is partially conformant with WCAG 2.1 AA. Most of it meets the standard, and we know of specific places that do not yet. Those are listed below rather than glossed over.
What is in place today
- Semantic HTML: real headings, real lists, and real buttons, plus navigation and footer landmarks, so assistive technology can navigate the structure.
- Text alternatives on images that carry meaning.
- Labels tied to every field on the contact form, with errors reported in text rather than by color alone.
- Keyboard operation for links, buttons, the mobile menu, and the contact form, with a visible focus indicator on form fields.
- Type that reflows and stays readable when you zoom to 200 percent or browse on a phone.
- Body copy set in dark ink on cream, which clears the AA contrast ratio with room to spare.
- Page content that reads fine with JavaScript blocked, because every page is static HTML.
Known gaps
These are the issues we are aware of and are working through:
- Pages carry no main landmark and no skip-to-content link, so keyboard and screen reader users tab through the whole navigation on every page instead of jumping straight to the content.
- The lightest gray used for small secondary text, such as form field labels, table fine print, post and case study meta lines, photo captions, and blog post navigation, sits at roughly 3.4:1 against the cream background, short of the 4.5:1 that AA asks for at that size. Body copy is not affected.
- The printable rate sheet (Kuhn_Consulting_Rate_Sheet.pdf) is not a tagged PDF, so a screen reader will handle it poorly. The same rates are available as regular web pages on the rates page.
- Several product screenshots use alternative text that names the screen without describing what it shows, which is thin if the image is the only place that detail appears.
- Three pages skip a heading level, which makes the outline read as though a section is missing: the software development and contact pages jump from the page title straight to a level three heading, and the about page drops from level two to level four in the technology list.
- On the portfolio page, the screenshot gallery opens its full size view on a mouse click only. There is no keyboard or screen reader path into it. The surrounding text describes each project, so nothing is only available inside the gallery.
- The ember accent color used for links inside blog posts and for small uppercase labels comes in at about 4.4:1 on cream, just under the same 4.5:1 line. Those links are also underlined, so they do not depend on color alone to be recognizable.
- Card links repeat the same generic labels: "LEARN MORE" appears four times across the home and services pages, "SITE" three times on the home page, and "READ ARTICLE" five times on the blog index. Listed on their own by a screen reader, those labels do not say where they go.
- A few things need JavaScript: submitting the contact form, opening the menu on a narrow screen, and stepping through the screenshot gallery on the portfolio page. With scripts off, every page still reads normally, its links still work, and the footer still points to the main sections. Email and phone reach us either way, and both are listed below.
- Content on third-party sites we link to, such as GitHub, is outside our control and follows those providers' own accessibility practices.
Browsers and assistive technology
The site is built to current web standards and works in recent versions of Chrome, Edge, Safari, and Firefox on desktop and mobile. It is meant to work with current screen readers, including NVDA, JAWS, and VoiceOver, though we have not tested every browser and screen reader combination. If yours gives you trouble, tell us and we will look at it.
Tell us about a barrier
If something on this site blocks you, please say so. A short note about the page you were on, what you were trying to do, and the browser or assistive technology you use is enough for us to act on. It also helps us fix the underlying problem for the next person.
We aim to reply within two business days. If a fix will take longer than that, we will tell you what we are doing and give you the information you were after in another format in the meantime, whether that is a plain-text version, a phone call, or an email.
How we assess this site
The assessment behind this statement is our own self-evaluation, not a third-party audit. It combines automated checks (browser accessibility audits and contrast ratio tools) with the manual passes tools cannot do for you: navigating the page with the keyboard alone, zooming to 200 percent, and reading the heading and link structure in order. New pages get the same review before they go live.
Updates to this statement
This statement is revised when the site changes or when a listed gap is closed. The date at the top reflects the last review. It was first published on August 16, 2026.