The Ansanm™ Framework

Band 01

Sensory

How the senses meet the work: seeing, hearing, touch, and balance.

What we check: Text contrast of at least 4.5:1 (1.4.3), text alternatives for images (1.1.1), captions on video (1.2.2), no flashing (2.3.1), and motion that stops when a device asks for less.
Example: A dosage chart that still makes sense to someone using a screen reader or seeing it in grayscale.

Band 02

Physical

How bodies meet the work, and the spaces they move through.

What we check: Tap targets of at least 24 by 24 CSS pixels (WCAG 2.5.8; we design to 48), everything works with a keyboard alone (2.1.1), and at events, kiosks within reach (15 to 48 inches), routes at least 36 inches wide, and somewhere to sit.
Example: A dosing calculator someone can use one-handed on a phone, and a conference booth a wheelchair user can reach and use.

Band 03

Cognitive

How minds meet the work.

What we check: Plain language, navigation that stays put from page to page (3.2.3), and no asking for the same information twice (3.3.7).
Example: An enrollment form that remembers what you already typed.

Band 04

Emotional

How the work makes people feel, especially when they’re anxious.

What we check: No time limits without a way to extend them (2.2.1), and error messages that say how to fix the problem (3.3.3).
Example: A public health site built for first-time, high-anxiety visitors.

Band 05

Contextual

Where and when people meet the work: bright sun, a loud room, one bar of signal, a borrowed phone.

What we check: Content reflows at 320 CSS pixels without sideways scrolling (1.4.10), and works in either orientation (1.3.4).
Example: A clinic check-in finished on a cracked phone in a waiting room.

Band 06

Social

How communities and cultures meet the work.

What we check: The page declares its language (3.1.1), names and imagery reflect the people served, and content is ready for translation.
Example: Patient materials reviewed with the communities who will use them, in the languages they read.

Band 07

Technology

How your code, documents, and devices meet assistive technology, on screen and in print.

What we check: Every control has a name, role, and state a screen reader can announce (4.1.2), headings follow a real outline (1.3.1), and PDFs are tagged to PDF/UA.
Example: A refill form that announces “Prescription number, edit text” instead of “edit text, blank.”

Band 08

Purpose

Why the work exists, and whether it serves that purpose for everyone.

What we check: Success measured for the people least served, and a real feedback path in an accessibility statement.
Example: A campaign meant to drive enrollment, tested for whether everyone can actually enroll.

Ansanm review

See your work through all eight.

An Ansanm review checks a site, document, or campaign against every band and ranks what to fix first.

Request an Ansanm review Try the free self-audit

Start a project.

Tell me what you’re building and where it needs to land. I respond within 48 hours.

Plan your project

IMPORTANT ACCESSIBILITY INFORMATION

INDICATION: Design Lady is indicated for organizations whose websites, documents, and campaigns must work for every person who uses them.

Do not launch if your site has images without alt text, text contrast below 4.5:1, or form fields without labels.

SIDE EFFECTS of inaccessible design may include lost customers, failed procurement reviews, and federal lawsuits (3,117 filed in 2025, per Seyfarth Shaw).

Tell your developer if you rely on an overlay widget. In 2025, 24.9% of website accessibility lawsuits targeted sites that had one installed (EcomBack 2025 annual report).

Please see full Prescribing Information: the 5-minute self-audit