Accessibility
Accessibility Statement
This site is built and tested against WCAG 2.2 Level AA. Below is what that covers, what the site does for you, where it still asks more of you than it should, and how to tell us when something does not work.
Last reviewed
20+
Years Experience
All Makes
& Models
Licensed
BUS2025-11907
5.0
on GoogleResidential
& Commercial
The Standard We Build To
WCAG 2.2 Level AA — the Web Content Accessibility Guidelines published by the W3C, at the middle of their three conformance levels — is what every page here is designed and checked against.
That describes how the site is built. It is not a certificate that it succeeds. Nobody outside this project has assessed the result, automated testing catches a great deal and cannot catch everything, and we would rather say so than imply an audit we have not had. Where the site falls short of the standard, that is a defect, and the fastest way one gets found is somebody telling us about it.
What the Site Does
What that looks like in practice.
- A skip link — first in the tab order everywhere, hidden until it takes focus, and it jumps past the header straight to the page content.
- Focus follows the page — when you move from one page to another, focus moves to the main content region rather than staying up in the navigation, so a screen reader starts on the page you asked for instead of the menu you left.
- A visible focus ring — on everything you can operate: two pixels, offset by three. It is drawn in the deeper of the two brand oranges because the lighter one measured 2.82:1 against one of the page grounds it had to sit on, under the 3:1 that WCAG 1.4.11 asks of a focus indicator. The deeper one measures between 4.77:1 and 5.67:1 across all four light grounds, and on the dark sections the ring switches to pale blue.
- Menus you can drive from the keyboard — the desktop dropdowns open on Enter, move on the arrow keys, and close on Escape with focus returning to the button that opened them. The mobile menu is a modal dialog: focus is trapped inside while it is open, Escape closes it, focus goes back to the button, and the page behind it stops scrolling.
- Targets of at least 44 by 44 pixels — for every button, link and field on a phone, apart from links that sit inside a sentence.
- Motion that stops when you ask — if your system is set to reduce motion, animation and transitions across the site collapse to nothing.
- A review belt you can pause — the scrolling band of Google reviews carries a visible Pause button, pauses while you hover it or while focus is anywhere inside it, and under reduced motion does not move at all: it becomes a strip you scroll by hand.
- A map that waits to be asked — the Google Maps embed on the service-areas page does not load until you press the button for it, so the page it sits on stays light and quiet until you want it.
How It Is Tested
This site ships with a verification script that covers every built page. It loads the site in a real browser and scans it with axe-core against the WCAG 2.0, 2.1 and 2.2 A and AA rule sets — at a 390-pixel phone width on every built page, and again at 1280 on the homepage and the two service hubs.
The same run checks the things a rule engine will not catch on its own: that each page carries exactly one top-level heading and never skips a heading level, that no tap target falls under 44 by 44 pixels on a phone, that the navigation dropdowns and the mobile menu can be opened, traversed and closed from the keyboard with focus landing where it should, and that a reduced-motion preference genuinely stops the motion.
That is an automated suite and a keyboard. It is not an audit: no third party has assessed this site, there is no VPAT and no certificate, and we are not claiming conformance on the strength of our own testing.
Known limits
Where the Site Still Needs JavaScript
Every page here is generated as finished HTML before it is published, so the words, the headings, the links, the phone number and the structured data are all in the page before a single script runs. If JavaScript is blocked, switched off, or simply fails, the content is still there to read.
The interactive parts are not. The search on our FAQ page, the dropdown panels in the desktop navigation, and the button that opens the menu on a phone all need JavaScript to work. None of them is the only way through: every service, town and article those menus reach is also a plain link in the footer of every page, and every FAQ answer is on the page whether or not the search runs. But without JavaScript you have to navigate rather than search, and we would rather name that than let you find it.
The coverage map is a Google Maps embed. It loads only when you press the button that asks for it, and once it does, the controls inside the frame are Google's rather than ours.
Nothing on this site is reachable only through a menu that needs a script.
Report a problem
If Something Here Does Not Work
Tell us the page you were on, what you were trying to do, and what happened instead. If you know the browser and any assistive technology you were using, include that too — it is usually enough for us to reproduce the problem.
Phone
The direct route, and the one that reaches a person rather than an inbox.
316-807-1713Email
Better if you want to attach a screenshot, or paste what a screen reader announced.
jesse@arrowheatandair.comContact form
The form on our contact page, if that is easier than either of the above.
Go to the contact page
A barrier on this site is a defect, not a feature request.
Get started
Let's Get Your Comfort Back
Tell us what your system is doing and we'll tell you what it needs.
Or just call
316-807-1713- Monday–Friday
- 7:00 a.m.–6:00 p.m.
- Saturday
- By appointment only
- Sunday
- Closed
Arrow Heating and Air Conditioning, LLC · License# BUS2025-11907