What we design for
Pages use semantic headings and landmarks, visible keyboard focus, descriptive links, responsive layouts, sufficient contrast, and motion that respects the reduced-motion preference. Interactive examples use the library’s real focus and dialog behavior.
How we test
Automated accessibility scans, keyboard interaction tests, narrow viewport checks, and browser tests run in the project suite. Manual assistive-technology and physical-device checks remain a separate release sign-off because automated scans cannot verify the complete screen-reader experience.
Known limitations
This statement does not claim formal WCAG conformance. Browser and assistive-technology combinations can announce dynamic dialogs differently, and code samples may require horizontal scrolling at high zoom. Findings are tracked and fixed through the public issue workflow.
Report a barrier
Open an accessibility issue on GitHub or email office@nipesolutions.com. Include the page, task, browser, device, and assistive technology when possible.