Accessibility

We want every reader to be able to use ToolsLiving. That includes people who use a keyboard, a screen reader, screen zoom, voice control or captions. This page explains our goal, what we do to meet it, where we still fall short and how to tell us about a problem.

Our goal

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. WCAG is the main web accessibility standard. The W3C, the group that sets web standards, publishes it.

The U.S. Department of Justice also points to WCAG in its guidance on websites and the Americans with Disabilities Act.

What we build into the site

Moving around

• You can reach every link, menu, button and form with a keyboard alone.
• A clear outline shows where you are on the page as you move with the keyboard.
• A "Skip to content" link lets you jump past the menu.
• Each page has one main heading. Headings follow a clear order, so screen readers can list them.
• Buttons and links are big enough to tap, at least 24 by 24 CSS pixels, as WCAG 2.2 asks.

Reading

• Body text meets WCAG contrast rules: at least 4.5 to 1 against its background. Large text and icons meet at least 3 to 1.
• You can zoom the page to 200% without losing text or tools.
• Pages fit a phone screen without sideways scrolling.
• We don't use color alone to show meaning. Charts and tables also use labels or text.
• We write in short, plain sentences.

Images, charts and video

• Every photo that carries meaning has alt text. Photos that are only decoration are hidden from screen readers.
• Each chart has a text table or a written summary of what it shows.
• When we add video, each clip will have captions. Clips that explain steps will also have a text version on the page.

Motion and tools

• If your device is set to reduce motion, we turn off animation.
• Nothing on the site flashes.
• Our calculators work with a keyboard. Each input has a label, and results appear as text a screen reader can read.
• Forms have labels and explain errors in words.

We confirm each item above with a keyboard-only pass, a screen-reader pass and an automated check. Any item the site does not meet yet moves to the list below.

Where we still fall short

We know about these limits and are working on them:

• Older pages. We are rewriting pages from our old site. Until each one is redone, some photos may have weak alt text.
• Photos to come. Some guides don't have their step photos yet. The steps are written out in full, so no step depends on a photo.

How to report a barrier

If any part of the site is hard to use, please tell us. It helps to include:

1. The page link.
2. What you were trying to do.
3. What went wrong.
4. Your device, browser and any assistive tool you use, such as a screen reader.

Email [email protected] with "Accessibility" in the subject line.

If you can't get the information you need from a page, tell us. We will send it to you in a format that works for you, such as plain text by email.

How fast we respond

We aim to reply within a few business days. We fix confirmed barriers as soon as we can.

How we check

We check new templates with a keyboard and an automated tool before they go live. We check again after big changes, such as a new calculator.

Last reviewed

This statement was last reviewed on November 7, 2026.

Change log: Nov 6, 2026: First version for the v2 site.