The handoff should be usable by more people.
Our accessibility goals, the current product expectations, and how to report a barrier.
Our intent
0xRouter aims to make discovery, licensing, seller controls, receipts, and API documentation usable with a keyboard, assistive technology, readable contrast, clear focus states, and plain language.
Current product practices
- Use semantic headings, labels, links, and status messages.
- Keep payment, rights, price, network, and delivery information visible rather than hiding it behind hover-only UI.
- Provide text alternatives for meaningful previews and avoid treating an image as the only product explanation.
- Keep legal and transaction copy available as readable text, not only as an image or downloadable file.
Known limits
Wallet extensions, third-party authentication, embedded previews, network prompts, and external provider screens may not meet the same accessibility standard. Some product-uploaded content can also be inaccessible or lack a complete description.
Report a barrier
Share the page, action, device or assistive technology, and the barrier you encountered through the deployment's support channel. Do not include private credentials or personal information that is not needed to reproduce the issue.