Accessibility at Dropura
Dropura is designed to be usable by everyone, regardless of how they interact with the web. This statement explains where we stand today and how to reach us if something gets in your way.
Conformance
Dropura aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA and uses the Accessible Perceptual Contrast Algorithm (APCA) as the contrast model for the dark visual theme. As of the audit date below, the app is partially conformant: every Critical and Serious issue surfaced by the Phase 8.4 audit has been resolved. A small number of Moderate / Minor items remain — see Known limitations below.
What we have built in
- Skip-to-content link on every page, visible on keyboard focus.
- Logical landmarks:
<header>,<nav>,<main>,<footer>on every route. - Keyboard-only operability across every interactive control, with visible focus rings that pass APCA Lc ≥ 35 against their backgrounds.
- Forms with explicit
<label>,aria-invalid, andaria-describedbyerror wiring; required fields are marked with both an asterisk and screen-reader-only text. - Status changes (filters, toasts, copy confirmations) announced through
aria-liveregions. - Modal dialogs that trap focus while open and return focus to the element that opened them when they close. ESC closes every dialog except the destructive deletion dialog, which requires explicit Cancel to avoid accidental dismissal.
- Reduced-motion support — every animation and transition is gated
behind
@media (prefers-reduced-motion: reduce). - Touch targets sized to at least 24×24 CSS px (WCAG 2.2 SC 2.5.8), and at least 44×44 on coarse pointers for primary actions.
- Windows High-Contrast (forced-colors) overrides that keep outlines, links, and buttons distinguishable when the OS replaces our palette.
Known limitations
- Cognitive-accessibility deep dive (plain-language passes, reading-level scoring) is planned but not yet shipped.
- The interface is currently English-only — no language alternatives or right-to-left mirroring yet.
- Some Moderate-level decorative gradients (brand title, hero wash) fall back to system colors under forced-colors but are not individually contrast-graded.
- Real-screen-reader testing (NVDA / JAWS / VoiceOver) is deferred to Phase 9; the current audit relies on automated axe-core checks plus manual DOM review.
Tools used in the audit
- axe-core
via
@axe-core/playwright(Phase 8.2 E2E harness). - APCA-W3
contrast computation (
scripts/apca-audit.mjs). - Manual keyboard-only and screen-reader-DOM review using Playwright and Chromium accessibility tree snapshots.
Report an accessibility issue
Found something that is hard to use, hear, or read? Please tell us and we will fix it. Email [email protected] and include the page URL, the device and assistive technology you were using, and what went wrong. We aim to acknowledge every report within five business days.