DisabilityWiki is built by and for disabled people. Accessibility isn't an add-on feature—it's foundational to everything we do.
We design for the widest possible range of abilities, technologies, and circumstances. We test with actual assistive technologies. We prioritize making critical pages (crisis resources, rights, benefits, healthcare) fully accessible. When we fall short, we want to know so we can fix it.
Every page uses semantic HTML structure with proper heading hierarchy. H1 titles identify each page, H2 marks major sections, and H3 marks subsections. We never skip heading levels.
All images include descriptive alt text explaining content and context. Decorative images are marked to be skipped by screen readers. Link text describes destinations, never generic phrases like "click here."
Data tables include header rows for column context. Complex tables include row headers where needed. We use actual HTML tables, not visual table layouts made from other elements.
Every interactive element is reachable by keyboard. Tab order follows logical reading order. Focus indicators remain visible so you can see where you are. No functionality requires a mouse.
Text maintains sufficient color contrast against backgrounds. We don't rely on color alone to convey meaning. Text can be resized up to 200% without breaking layouts. The wiki works in high contrast mode and with user-defined color schemes.
We write in plain language, aiming for 8th grade reading level on complex topics. Jargon and acronyms are defined on first use. Paragraphs stay short and scannable. Every page follows consistent structure so you can predict where information will be.
Related information is chunked into clear sections. Navigation is predictable across the wiki. Important information appears near the top of pages.
The wiki responds to different screen sizes without losing functionality. Touch targets are large enough for varied motor abilities. We avoid hover-only interactions that don't work on touch devices.
Pages load without requiring heavy JavaScript. Critical content is accessible on slow connections. We minimize large media files and provide alternatives where needed.
Pages discussing potentially distressing topics include content warnings at the top. This includes pages covering abuse, violence, medical trauma, institutionalization, self-harm, and state violence. Warnings allow readers to prepare or skip sections as needed.
We present information in multiple ways where possible: text explanations, structured lists, tables for comparisons. Critical resources include phone numbers, websites, and addresses rather than relying on only one contact method.
We explain complex systems (benefits, legal rights, healthcare navigation) in accessible language without losing accuracy. Technical terms are defined. Legal or medical jargon is translated into plain language with original terms provided for those who need them.
We aim to be honest about our limitations.
Some older pages have not yet been updated to current accessibility standards. We're working through them systematically, prioritizing crisis and essential resources.
PDF documents linked from external sources may not be accessible. We note this where relevant and provide alternative formats when available.
Video content from external sources may lack captions or audio description. We prioritize embedding accessible videos and noting when external content has gaps.
Complex interactive elements on some pages may have inconsistent keyboard support. We're standardizing these.
Global South content is less developed than US/Western content. We're actively expanding coverage and seeking contributors from underrepresented regions.
Some pages have dense information that could be better chunked for cognitive accessibility. We're revising these as we update sections.
Translation and multilingual support is limited. This is a priority for future development.
We test with real assistive technologies, not just automated checkers. Our testing includes:
Screen readers: NVDA (Windows), JAWS (Windows), VoiceOver (macOS and iOS), TalkBack (Android).
Magnification: Windows Magnifier, macOS Zoom, browser zoom up to 200%.
Keyboard navigation: Tab, arrow keys, Enter, Escape, and common shortcuts.
Speech recognition: Dragon NaturallySpeaking, Voice Control (macOS/iOS).
Mobile assistive tech: VoiceOver, TalkBack, Switch Control.
If you use assistive technology we haven't tested with, we want to hear about your experience.
We work toward WCAG 2.1 Level AA compliance as a baseline. We often exceed this standard based on community feedback about what actually works for disabled people.
WCAG provides technical guidelines, but real accessibility comes from understanding how disabled people actually use technology. Compliance doesn't equal usability. When WCAG guidelines conflict with what disabled community members tell us works, we listen to disabled people.
If something doesn't work for you, please tell us. Your feedback directly shapes how the wiki evolves.
What helps us fix issues faster:
How to reach us: Use our contact form or the feedback link at the bottom of any page.
What we commit to: Your feedback will be read by disabled maintainers. We prioritize issues that block access to critical pages. We update this statement as we make fixes.
We prioritize based on impact and community feedback. Pages that help people in crisis or navigate essential systems get fixed first.
We balance quick fixes against long-term structural changes. Some issues can be fixed immediately; others require rebuilding page architecture.
Our capacity is limited. We're honest when things will take time to fix. We'd rather be transparent about timelines than promise immediate fixes we can't deliver.
Want to help make DisabilityWiki more accessible?
Test with your technology: Let us know how pages work with your assistive tech, browser, or device.
Report specific problems: Detailed reports help us fix issues faster.
Share your needs: What formats, features, or approaches would help you most?
Contribute accessibility expertise: See How to Contribute for ways to get involved.
This accessibility statement reflects DisabilityWiki's ongoing commitment to disabled people's access. We update it as we make improvements and identify new challenges. Last reviewed: December 2025.