Accessibility Statement
This statement describes a conformance target and work completed so far. It is not a claim of full, verified WCAG 2.2 AA conformance. A full accessibility audit, including automated and manual testing across browsers, screen readers, and assistive technology, has not yet been completed.
Last reviewed: August 21, 2026
Our target
Maternal Development aims to conform to WCAG 2.2 Level AA. This is a target we are actively working toward, not a certification already achieved.
What is in place today
- A skip-to-content link on every page
- Verified heading structure with no skipped levels, audited and corrected across all pages
- Keyboard-operable navigation, search, and glossary filtering, including a real focus trap in the mobile menu and search dialog: keyboard focus stays inside an open dialog until it is closed, and returns to the button that opened it afterward
- Glossary term tooltips that are keyboard-operable, dismissible with Escape, hoverable without disappearing, and reachable by touch on mobile, not just mouse hover
- Live-announced search results and Join form status messages via
aria-live, so screen reader users hear results and outcomes as they happen prefers-reduced-motionsupport, so animated reveals are disabled for anyone who has requested reduced motion at the operating-system levelaria-current="page"and syncedaria-expandedstates on navigation and dialog controls, including when closed via Escape, not just by click- Form fields with associated labels, grouped checkboxes with fieldsets and legends, and a live-announced status region on the Join form
- Color contrast checked by calculation (not estimate) against the site's actual palette; several failing text colors, including the sitewide keyboard focus indicator, were identified and corrected
- Enlarged tap targets on small inline links (footnote references) that previously had none
- Responsive layout intended to work from 320px mobile through desktop widths, with overflow safeguards against long unbroken text
Known gaps
Several section labels across the site are styled to look like headings but are not marked up as real heading elements, so they do not appear in screen-reader heading navigation. This is identified and understood; it has not yet been corrected, because a sitewide fix needs a careful, dedicated pass rather than a rushed one.
Contrast has been checked by calculation for the colors in heaviest use across the site, not for every color combination that exists anywhere on it. Screen-reader behavior has not been tested end-to-end with real assistive technology (a screen reader, not just keyboard simulation), and no independent, professional accessibility audit has been performed. These remain open, not resolved, until that testing happens.
Reporting an accessibility problem
If you encounter an accessibility barrier anywhere on this site, please tell us through the Contact page. Include the page URL and, if possible, the browser or assistive technology you were using — that detail makes it much faster to find and fix.