Our target
We use the Web Content Accessibility Guidelines, WCAG 2.2 Level AA, as the design and testing target for the public web application. This is a continuing product commitment, not a claim of formal certification or perfect compatibility with every device or assistive technology.
Design and interaction practices
Complex tables, charts, editors, wallet interfaces, third-party content, and newly released workflows receive additional review because they can introduce accessibility barriers.
- Semantic headings, landmarks, labels, and accessible names.
- Keyboard navigation and visible focus for interactive controls.
- Readable contrast and status information that does not rely on color alone.
- Responsive layouts from small phones through desktop screens.
- Support for browser zoom and reflow without hiding core actions.
- Reduced-motion behavior where animation is not essential.
- Alternative text or accessible labels for meaningful visual content.
How we test
Testing combines automated accessibility checks with keyboard, responsive-layout, zoom, and screen-reader-oriented review on representative journeys. Automated tests help identify common issues, but they do not replace human evaluation.
Third-party authentication, wallet, media, and embedded experiences can have accessibility behavior outside Dapping's direct control. We work to provide an accessible surrounding flow and raise issues when a provider blocks completion.
Report an accessibility barrier
Email [email protected] with the page URL, the task you were trying to complete, the barrier you encountered, and your browser or assistive technology if you are comfortable sharing it.
Do not include passwords, private keys, seed phrases, verification codes, or unnecessary personal information. We will use the report to understand the barrier and prioritize an appropriate correction.