01

What we aim for

This site is built toward 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 about how the site is built. They are not a legal guarantee that every page meets every criterion at every moment. Where the site falls short, we would rather hear about it and fix it.

02

Using this site

The main navigation, the request and contact forms, the project planner, the scope builder, the guides and blog articles, and the expandable questions are designed for keyboard and screen-reader use. Browser zoom and text resizing up to 200% should not hide content or cut off controls. Each page uses one main heading with nested subheadings, so a screen reader can be used to skim a page rather than read it end to end.

The electrical diagrams on service 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.

  • No media plays automatically
  • No pop-up traps keyboard focus
  • No advertising, social, chat, or session-recording scripts
  • Cost and comparison tables scroll inside their own container so the page never scrolls sideways
03

No accessibility overlay

This site does not use an accessibility overlay, toolbar or widget. 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.

If you use a screen reader, magnifier, voice control or any other assistive technology, this site is intended to work with the tools you already have set up.

04

Known limitations

The request and contact forms use a bot-protection challenge supplied by a third party. If that challenge is difficult or impossible for you to complete, send the same information through the contact page instead and it will be handled the same way.

Where a page links to a document produced by a utility, a state agency, or a manufacturer, we cannot guarantee that document meets the same standard as the pages around it. If you reach one and need the information another way, 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.

05

Telling us about a barrier

If any page, control, form, planner or document on this site is difficult or impossible to use, please tell us through the contact 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. 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.

06

What this statement does not cover

This statement covers this website. It does not cover the websites, offices, vehicles, printed estimates or communications of the independent electrical contractors a request may be shared with. Each of those is a separate business responsible for its own accessibility. If contact from a provider arrives in a form you cannot use, tell us and we will pass that on.

07

How this statement is maintained

Accessibility is reviewed whenever the site’s shared templates or primary interactions change, rather than on a fixed calendar, because a template change is what actually moves accessibility across many pages at once.

This statement was last reviewed on September 5, 2026. It will be revised when the site’s structure changes materially, or when a reported barrier changes what can honestly be claimed here.