Short answer
The build target is WCAG 2.1 Level AA: headings in order, real form labels, keyboard operation, sufficient contrast and text alternatives for images that carry information. No accessibility overlay runs on the site, and no page is certified to meet every criterion at every moment. If something blocks you, report the barrier using the route described below and it will be looked at and fixed.
What we aim for
The build target is the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. In practice that means a clear heading structure on every page, text that meets contrast requirements against its background, controls that can be reached and operated with a keyboard alone, links whose purpose is clear from their own wording, form fields with real labels, meaningful alternative text on images that carry information, and respect for a reduced-motion preference set in your operating system.
These are commitments, not guarantees. How the site is built follows them, but no page is certified to meet every criterion at every moment. Where the site falls short, we would rather hear about it and fix it.
Accessibility features at a glance
| Feature | What it means in practice |
|---|---|
| Keyboard operation | Navigation, forms, tools and expandable questions can be used without a mouse |
| Headings and structure | One main heading per page with nested subheadings for screen-reader navigation |
| Text and contrast | Text meets contrast requirements and resizes to 200% without hiding controls |
| Images and diagrams | Informative images have alternative text and diagrams are described in the text beside them |
| Motion | A reduced-motion preference set in your operating system is respected |
Using this site
The main navigation, the service-request form, the decision tools, the guides and blog articles, and the expandable questions are designed for keyboard and screen-reader use. Zoom and text resizing work too. Up to 200%, neither should hide content or cut off controls. Each page uses one main heading with nested subheadings, so a screen reader can skim a page instead of reading it end to end.
The diagrams on service and solution pages illustrate information that is also written out in the text beside them. No safety instruction on this site depends on being able to see an image. Rebate and cost tables are real HTML tables with header cells, and they scroll inside their own container so the page itself never scrolls sideways.
No accessibility overlay
No accessibility overlay, toolbar or widget runs on this site. Overlays are marketed as an instant fix and are widely reported by disabled users and by assistive-technology vendors to interfere with the screen readers, magnifiers and browser settings people have already configured. Building the underlying pages correctly is the approach taken here instead.
Screen readers, magnifiers, voice control and other assistive technology are all meant to keep working here, using the setup you already have.
Known limitations
The service-request form uses a bot-protection challenge supplied by a third party. Difficult or impossible to complete? Use the contact route published on the privacy page instead: the request gets handled the same way. A plumbing or heating failure is often urgent, so that route is checked just as closely as the form.
Where a page links to a document produced by a utility, a state agency, an efficiency program or a manufacturer, we cannot guarantee that document meets the same standard as the pages around it. Reach one and need the information another way? Just ask, and it will be provided directly.
Automated checks find common problems but cannot judge whether a page is genuinely usable. Feedback from real use is the part that cannot be generated automatically.
Telling us about a barrier
If any page, control, form, tool or document on this site is difficult or impossible to use, please tell us using the contact route published on the privacy page, and begin your message with the word “Accessibility”. Include the page address and what happened: what you were trying to do, what your assistive technology did, and what you expected instead. Naming that detail is what makes a report actionable.
We aim to acknowledge accessibility reports within five business days and to give you either a timeframe for a fix or another way to get the information in the same reply. Please do not include sensitive personal information in an accessibility report.
What this statement does not cover
The statement covers this website only, not the websites, offices, vehicles, printed estimates or communications of the independent plumbing and heating businesses a request may be shared with. Each of those is a separate business responsible for its own accessibility. Contact from a business that arrives in a form you cannot use? Tell us, and we will pass it on.
How this statement is maintained
Accessibility review has no fixed calendar. It happens whenever the site’s shared templates or primary interactions change, because a single template edit is what actually moves accessibility across many pages at once.
This statement was last reviewed on September 5, 2026, and will be revised when the site’s structure changes materially, or when a reported barrier changes what can honestly be claimed here.