Accessibility

Accessibility statement.

Deniable is designed so people can browse the catalogue, understand the service, manage an account, and contact support using different devices and ways of navigating.

Our commitment

We use the Web Content Accessibility Guidelines (WCAG) 2.2 as our accessibility reference and work toward Level AA practices. Accessibility is part of the product work, not a separate visual layer. We continue to test pages, forms, account flows, documentation, and checkout journeys as they change.

What we currently provide

• Semantic headings, landmarks, labels, buttons, and links for screen readers and keyboard navigation.
• Visible focus states and keyboard-accessible forms, navigation, filters, consent controls, and account actions.
• Text alternatives for meaningful images and decorative images marked as decorative.
• Readable contrast, responsive layouts, scalable text, and content that does not depend on colour alone.
• Clear error, success, loading, and authentication messages announced in the relevant context.
• Reduced-motion-friendly interactions and no essential information conveyed only through animation.
• Plain-language explanations for dataset, API, credit, and security concepts.

Known limitations

Some third-party interfaces, payment screens, authentication messages, embedded browser behaviour, and provider-hosted pages are outside Deniable’s direct control. Complex catalogue data and code examples may also require additional explanation or a different presentation. We treat reports about these barriers as product issues and prioritise them according to impact.

Feedback and alternative help

If you cannot use a page, control, document, or checkout step, email "support@deniable.net". Please include the page address, what you were trying to do, the assistive technology or browser involved if relevant, and the format that would help. We can provide information or support through an alternative channel where reasonably possible.

Accessibility requests are handled as support requests. We aim to acknowledge them promptly and provide a useful response within the same support workflow.

Assessment

This statement describes the current product approach; it is not a claim that every page or third-party surface conforms to every WCAG success criterion. The page is reviewed when major navigation, account, catalogue, API documentation, checkout, or consent changes are released.

Related information

Read the Privacy Policy, Terms of Service, or Cookie settings.

Last updated: 5 September 2026