Accessibility
Accessibility at happier IT
Built to be used by everyone, and tested to prove it.
This site is built to WCAG 2.2 Level AA, the Web Content Accessibility Guidelines, the international standard for making web pages usable by people with disabilities. Every page template has been checked with automated accessibility testing and returns zero violations. Below is what was actually done, what that testing does not cover, and how to tell us if something does not work for you.
The standard
WCAG 2.2 AA, and why that one.
WCAG stands for the Web Content Accessibility Guidelines. It is the standard most accessibility law around the world points at, including Canadian federal and provincial requirements. Version 2.2 is the current one, and Level AA is the tier those laws generally require.
In plain terms it asks that a page can be perceived, operated and understood by people who are not using it the way a designer imagined: with a screen reader, with a keyboard and no mouse, at four times the normal text size, with low vision, with limited fine motor control, or simply on a poor connection.
For happier IT this is not a compliance checkbox. The company exists to take mental load off people. A website that quietly excludes some of those people would contradict the first thing we say about ourselves.
If something here does not work
Email [email protected] and describe what you were trying to do, what happened, and what you were using.
Or call: service 1 (888) 974-2779, sales 1 (888) 897-3611.
What was actually done
Specifics, not a statement of intent.
An accessibility page that only says 'we are committed to accessibility' tells you nothing. Here is what is true of the pages you are reading.
-
Semantic HTML, not a pile of divs
Headings are real headings in order, lists are lists, buttons are buttons and links are links. Assistive technology gets structure it can navigate rather than a flat wall of text.
-
Visible focus, everywhere
Every interactive element has a focus state you can actually see. Nothing is styled to disappear when you tab to it, and nothing traps the keyboard.
-
Contrast checked, not assumed
Body text meets or exceeds the 4.5:1 contrast ratio the standard asks for, and large text meets its own threshold. Verified by testing rather than by eye.
-
A menu that works without JavaScript
The navigation is keyboard-operable and still works with JavaScript disabled. If a script fails to load, the site does not become unusable.
-
FAQ answers always present
Question and answer panels use native HTML, so every answer is in the page whether it looks open or closed. Nothing is hidden from search or from a screen reader by a script.
-
Motion you can turn off
Animation is slight, and the prefers-reduced-motion setting in your operating system is respected. Nothing moves, flashes or auto-advances on its own.
-
Fonts served from here
Typefaces are self-hosted, so text renders quickly and predictably rather than shifting position part-way through a page load.
-
No interruptions
No auto-playing video or audio, no pop-up offers, no chat window that opens itself, no cookie banner, because there are no cookies to consent to.
How it was tested
Automated testing, on every template.
Every page template on this site was tested with axe, the standard automated accessibility testing engine, checking against the WCAG 2.2 AA rule set. Every template returns zero violations.
Testing runs against the templates rather than a sample of pages, because pages here are generated from shared components. One template covers dozens of pages, so a fix in one place is a fix everywhere, and a regression in one place would be a regression everywhere, which is why this is checked as part of the build rather than once at the end.
Keyboard navigation, focus order and the site working with JavaScript disabled were checked by hand as well, because automated tools cannot judge whether a focus order makes sense to a person.
What we test with
axe automated testing against WCAG 2.2 AA, across every page template, as part of the build. Plus manual keyboard and no-JavaScript checks.
Last reviewed: 3 September 2026.
The honest limit
Automated testing is not the same as real people.
Zero automated violations is worth having. It is not the same as this site being genuinely pleasant to use with a screen reader, and we are not going to blur that distinction.
Automated tools catch missing labels, poor contrast, broken structure and invalid markup. They cannot tell you whether a heading actually describes what follows it, whether link text makes sense out of context, or whether getting to the phone number takes four steps or forty.
This site has not yet been tested with people who use assistive technology daily. That is the difference between passing a test and being usable, and it is the next thing to do rather than something we consider already handled.
Until then, the people best placed to find what the tools missed are the people using this site. Which is why the paragraph below is a genuine request rather than a formality.
Not covered by this statement
This page describes this site. Documents we send you, third-party systems such as the client portal, and software your organization already runs are not covered here.
If you hit a barrier in something we sent you, tell us and we will provide it in a format that works for you.
Telling us
Report a barrier, and we will fix it.
This is a commitment, not a form of words. Accessibility problems are treated as defects, not as feature requests.
Email [email protected]. Call service on 1 (888) 974-2779 or sales on 1 (888) 897-3611. Or use the contact form, which is itself keyboard-operable and labelled.
Useful things to include, if you can: the page address, what you were trying to do, what happened instead, and which browser, device or assistive technology you were using. Any one of those helps. None of them are required, a sentence saying "the menu will not open for me" is enough to start.
We will acknowledge the report, tell you what we found, and say plainly when it is fixed or why it will take longer. If you would rather not use email, say so and we will arrange another way.
Related: privacy.
Want IT that works for everyone on your team?
The same thinking applies to the systems we run for clients. A 30-minute call, no slides, no obligation.