Accessibility Statement

Last updated: 2026-05-02

DRYCE is built so that anyone in the United States can read, save, and share its public information — including people who use screen readers, keyboard-only navigation, magnification, voice control, or reduced motion.

Conformance target

We target Web Content Accessibility Guidelines (WCAG) 2.2, Level AA Opens in a new tab. across all public pages on dryce.app: the apex page, this statement, the privacy / terms / risk / support pages, and every page under /resourceguides/.

What we verify

Every page declares a language, has one <h1> heading, and uses headings in order.
Every page exposes a single main landmark, a Skip to main content link, and a contentinfo footer.
External links open in a new tab with rel="noopener noreferrer", referrerpolicy="strict-origin-when-cross-origin", and a screen-reader-only "Opens in a new tab" hint.
Decorative images use empty alt=""; meaningful logos carry an accessible name on the wrapping link.
Color uses a dark theme tuned for AA contrast on body text and links; focus styles are visible without relying on color alone.
Touch targets on the SCI Camp Hill guide are sized for one-handed use and the layout reflows down to small portrait widths.

Known limits

Some external destinations we link to (government PDFs, vendor apps) are not under our control and may not meet WCAG 2.2 AA. We summarize the same information in HTML on /resourceguides/ wherever we can.
The native DRYCE iOS app is governed by Apple's accessibility surface (VoiceOver, Dynamic Type, Reduce Motion); this statement covers the public web only.
We don't currently provide audio descriptions or sign-language versions of pages. Email us if that would help — we will prioritize.

Report a barrier

If something on a public DRYCE page is hard to use with your assistive technology, email senja@dryce.app with "Accessibility" in the subject line and, if possible, the page URL and a short description of what blocked you. We try to acknowledge within two business days and to fix verified barriers in the next deploy.

Compatibility

Tested with current versions of VoiceOver on macOS / iOS, TalkBack on Android, NVDA on Windows, Safari, Chrome, and Firefox. Pages are designed to work without JavaScript wherever the content is informational.

Standards we reference

WCAG 2.2 (W3C); ARIA Authoring Practices Guide; the U.S. Section 508 Refresh as informative guidance. This is a self-assessment, not a third-party audit.