Accessibility

This site was built to be usable by as many people as possible, including anyone using a screen reader, a keyboard rather than a mouse, a magnifier, or a phone in bright Phoenix sun. This page says what has been done, what tools are on the page, and how to tell us when something does not work.

What we are aiming at, and what we are not claiming

We work to the Web Content Accessibility Guidelines — WCAG 2.1, Level AA — as the standard the site is built against. We have not had an independent accessibility audit of this site, so we do not claim conformance with it. Claiming a level nobody has tested would be worth less to you than an honest description of what is actually here, which is what follows.

The accessibility toolbar

There is an accessibility button on every page. Opening it gives you controls that change how the page is presented, applied immediately and kept as you move between pages. There are four ready-made profiles — Motor, Visual, Cognitive and Senior — which set several of the options below in one click, and every option can also be set on its own.

Text and display

• Text size, in steps up and down.
• Line height, letter spacing and word spacing opened out, which helps a lot of people get through a long paragraph.
• A dyslexia-friendly typeface.
• A reading guide and a reading spotlight, which track a line of text and dim the rest of the page.
• Read aloud, for the whole page or just the part you have selected.

Colour and vision

• High contrast and inverted colours.
• Saturation turned down or up.
• Colour-blind modes for protanopia, deuteranopia and tritanopia.

Navigation and content

• Underlined or highlighted links, so a link is obvious without relying on colour alone.
• A big cursor, in a choice of colours.
• Animations stopped, for anyone who finds movement uncomfortable.
• Images hidden, which strips a page back to its text.
• Form assistance, which makes the labelling on a form more prominent.
• A list of the headings on the page, to jump straight to a section.
• A keyboard shortcuts panel, and a reset that clears everything you have changed.
• Labels in English, Spanish or French.

Your choices are stored in your own browser, not on our server, so they survive moving between pages and coming back later on the same device. They are not sent to us and they are not used to identify you. The toolbar is provided as part of the accessibility toolkit our web agency maintains across the sites it builds.

What is built into the pages themselves

A toolbar on top of an inaccessible page is not much use, so the pages underneath it were built this way:

• A skip to content link is the first thing a keyboard reaches on every page.
• One heading structure per page, in order, so a screen reader can navigate by heading without hitting a missing level.
• Every form field has a visible label attached to it, not just placeholder text.
• A visible focus outline follows the keyboard, and it was chosen to stay visible on both the light and the dark bands of the page.
• Text and background colour combinations were measured rather than guessed, and the site's one bright colour is used for buttons rather than for text on a light background, where it would fail.
• Images carry alternative text, and decorative shapes are hidden from screen readers instead of being read out.
• The questions and answers use the browser's own expanding sections, so they open and close with the keyboard and work with JavaScript switched off.
• The coverage map on the service areas page is an enhancement, not the only route: every town is also a written link on the same page, so a blocked map does not hide where we work.
• Buttons and links are sized for a thumb, and the call and text buttons sit within reach at the bottom of a phone screen.
• If your device asks for reduced motion, the site stops animating.
• The pages print sensibly, with the phone number intact.

Where we know there is more to do

Being honest about this is more useful than a badge:

• The coverage map is third-party software. Its own controls are not something we wrote, which is why the written list of towns exists alongside it.
• The chat window is a third-party component as well, and we keep testing it with a keyboard and a screen reader rather than assuming it is fine.
• No independent audit has been carried out. If one is, what it finds gets fixed and this page gets updated.

Tell us when something does not work

If any part of this site gets in your way, please tell us. It is the fastest way for it to get fixed, and it is not a bother.

• vwleakdetectionaz@gmail.com
• (602) 830-9717 — or text us
• 4822 S 36th Dr, Phoenix, AZ 85041

What helps us most: the address of the page, what you were trying to do, what happened instead, and what you were using — phone or computer, which browser, and any assistive software. If it is easier to say out loud than to type, call and say it. We will read back or describe anything on the site over the phone, in English or in Español.

We will reply, tell you what we have found and say plainly what we can and cannot fix. We are not going to put a deadline on this page that we cannot keep.

If you need the information a different way

Anything on this website can be given to you over the phone, or sent by email as plain text. You never have to use a form, a map or a chat window to reach this business — a phone call always works.

See also the privacy policy, which explains where your accessibility settings are stored, and the terms of service.