DOFIW TOOL DIRECTORY

Accessibility Tools

Find the focused check that matches your current task. Search by topic or filter the directory, then open the tool without registration or a remote analysis API.

10 working tools3 clear categoriesLocal input processing
Illustration of focused color, structure, form, image, table, and caption checks moving toward human verification
Focused checks support—but do not replace—human accessibility evaluation.
FIND A TOOL

Search all ten accessibility tools

Enter a task such as “contrast,” “form,” “alt text,” “table,” or “caption.” You can also narrow the directory by category. Every tool appears once.

Showing 10 tools

01Color

Color Contrast Checker

Calculate and interpret the contrast ratio between one foreground and background.

Use when: reviewing a specific text, icon, or component color pair.

Open the checker
02Color

Color Palette Accessibility Checker

Compare usable foreground-background relationships across several palette colors.

Use when: assigning text and surface roles in a palette or design system.

Open the checker
03Color

Accessible Color Suggestion Tool

Explore nearby color candidates that reach a selected contrast target.

Use when: one side of a failing color pair should remain fixed.

Open the tool
04HTML

Heading Structure Checker

Extract an HTML outline and flag patterns that deserve structural review.

Use when: visual heading sizes hide the page’s semantic hierarchy.

Open the checker
05HTML

Form Label Checker

Review how supplied form controls receive visible and programmatic names.

Use when: checking labels, IDs, placeholders, or ARIA naming references.

Open the checker
06Navigation

Link Text Checker

Inventory link names and destinations for common clarity problems.

Use when: links may be empty, generic, repeated, or unclear out of context.

Open the checker
07Images

Alt Attribute Checker

Inventory alternative-text patterns before reviewing each image’s purpose.

Use when: supplied HTML contains missing, empty, generic, or functional image alternatives.

Open the checker
08Data

Accessible Table Generator

Create semantic HTML for a straightforward data table.

Use when: building a table with a caption, column headers, scopes, and optional row headers.

Open the generator
09Content

Readability and Plain Language Checker

Review English readability indicators and language patterns that may need editing.

Use when: a passage feels dense and you need focused editorial signals.

Open the checker
10Media

Caption Reading Speed Calculator

Calculate characters per second and words per minute for one caption cue.

Use when: checking whether a cue provides enough reading time.

Open the calculator
A CLEAR WORKFLOW

From question to verified repair

The directory helps you select a focused check. The complete accessibility decision still belongs to the final page and the people using it.

Choose the smallest questionIdentify the exact pair, markup sample, passage, table, or caption cue involved.
Read beyond the badgeUnderstand what the result establishes, its assumptions, and its stated limitations.
Test the published experienceVerify the repair with keyboard, zoom, browsers, assistive technology, and representative users.
RESPONSIBLE USE

Focused evidence is not a website certificate

A ratio, warning, outline, generated table, writing indicator, or timing calculation can answer a narrow question. No result on this page independently establishes complete WCAG conformance, legal compliance, or usability for every person.

Use the Accessibility Guides when you need standards context, examples, exceptions, and repair choices.

COMMON QUESTIONS

Before opening a tool

Are all ten tools free?

Yes. They are available without registration or a paid analysis API.

Can the directory scan a live website?

No. Each tool works with focused values, markup, text, or timing that you provide. This keeps its result explainable and avoids presenting a partial scan as a complete audit.

Why are HTML tools grouped together?

Headings, labels, links, image alternatives, and tables all depend on semantic relationships in markup, even though they support different user tasks.

Does a passing result prove accessibility?

No. It means the provided input met the specific rule described by that tool. Other requirements and real-user barriers may remain.

Need help interpreting a result?

Read the topic-specific guides for requirements, practical examples, repair decisions, and the manual checks that follow automation.

Browse Accessibility Guides