Accessibility
How we test and improve access to VoidPaste. This is a statement of current practice, not a certification.
Our target
VoidPaste aims to meet WCAG 2.2 Level AA across paste creation and viewing, account and administration screens, documentation, and tools. We prioritize keyboard access, clear focus, screen-reader semantics, sufficient contrast, reduced motion, responsive layouts, and practical touch targets.
What we test
Automated checks use axe-core in Chromium against representative public, authenticated, editor, viewer, dialog, error, and mobile states. CI fails on serious or critical WCAG A/AA violations. We also encode keyboard, focus-return, reduced-motion, 320-pixel reflow, and touch-target checks where browser automation is reliable.
The current baseline was tested with Chromium and keyboard automation. Manual screen-reader testing and browser coverage beyond Chromium remain ongoing work.
Known limitations
- The advanced Monaco code editor has its own accessibility mode and keyboard model. A labeled lightweight textarea is available on touch devices and through the editor mode control.
- Large data tables scroll horizontally at narrow widths to preserve their relationships; the page itself should not scroll horizontally.
- Automated tools cannot prove every WCAG success criterion. Assistive technology and usability reviews will continue alongside CI checks.
Feedback
If an accessibility barrier prevents you from creating, reading, or managing a paste, email [email protected]. Include the page, what you were trying to do, and your browser or assistive technology if you are comfortable sharing it.