Accessibility
Accessibility of this website.
We are working to WCAG 2.2 Level AA. Part of it is enforced by scripts that fail our build rather than by good intentions, so the claims below can be checked rather than taken on trust.
Chairside Solutions ("Chairside AI", "we", "us") operates this website.
Our target
We are working to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA.
We do not claim a formal audit has been carried out, because none has. What follows is what this site does today.
What is in place
Document outline
Exactly one h1 per page, so the outline of every document is unambiguous. A build script parses every built page and fails on any count other than one.
Focus indicator
Every interactive element takes a visible 2px focus ring with a 2px offset. The offset is what keeps the ring off a filled control, so it is always measured against the surface behind the element: 9.02:1 against the page background, and never below 4.5:1 against any surface the site uses.
Text contrast
Every text color clears 4.5:1 against every surface it can sit on. The lowest pairing on the site measures 5.27:1.
Control boundaries
The boundary of anything you operate — text inputs, selects, textareas, buttons, the menu control — clears 3:1 against every surface, which is what makes the control identifiable rather than merely decorated.
Target size
Every interactive target is at least 24 by 24 CSS pixels. Buttons and navigation links are 44 pixels tall, and standalone links in the footer are padded up to 30 pixels rather than left at their 15-pixel line box.
Color is never the only signal
No status or state is carried by color alone. Required form fields are labeled Required in words as well as marked in the accessibility tree. The current page in the navigation is underlined and carries aria-current, not just a different tint.
Reduced motion
Every animation on the site respects prefers-reduced-motion. With that preference set, the animated diagrams render finished and still, and the scrolling activity feed is replaced by a static list — nothing is hidden or replaced by an apology.
The mobile menu needs no script
It is a native HTML disclosure element, so it opens, closes, and takes keyboard and screen-reader interaction the way the browser intends, with no code of ours in between.
Works with scripting off
The site ships zero first-party JavaScript, so nothing here depends on script execution. With scripting disabled or blocked, every page and both contact forms still work.
Real form labels
Every field has a real label element tied to its control. Placeholder text is never used as a label, because it disappears the moment you type and is not reliably announced.
Skip to content
A skip-to-content link is the first item in the tab order on every page, hidden until it takes focus and plainly visible once it does.
Known issues
There are no conformance issues currently recorded for this site. When one is found or reported, it will be listed here along with what we are doing about it.
An empty list means nothing has been recorded — not that nothing exists.
Report a barrier
If something on this site is hard or impossible for you to use, please tell us. Say which page you were on, what you were trying to do, and what happened. If you can, tell us the browser and any assistive technology you were using — it makes the problem far quicker to reproduce.
Write to us and say your message is about accessibility.
A person reads every report and you will get a reply. We are not going to name a number of days for a fix: we would rather answer you honestly than commit to a date we cannot hold.
How this is tested
Three things are checked automatically on every build. The build fails if any of them regress.
- Color contrast — Every text, interactive-boundary, and focus-ring pairing is recomputed from the design tokens and measured against its threshold. The build fails if any gate is missed or if a token is left unclassified.
- One h1 per page — Every built page is parsed and its h1 count checked. Anything but one fails.
- Zero JavaScript — Every built page is scanned for script tags and inline styles. The one permitted exception is the spam-check loader on the contact page.
Automated checks catch regressions. They do not tell you whether the site is usable, and they do not replace testing by people — including people using screen readers, magnification, and the keyboard alone. That testing is ongoing, and this page will say what it has covered as it is done.