Accessibility Statement

Plain-language summary

We want everyone to be able to use Clap Ideas, including people with disabilities.
We aim to meet WCAG 2.2 level AA, a widely used accessibility standard. This is our target, not a promise that every page is perfect.
We build in features like keyboard navigation, a skip-to-content link, clear focus outlines, light and dark themes, and reduced-motion support.
Some complex or AI-generated parts may not yet work perfectly with every assistive technology. We are still improving.
Found a barrier or need help? Email support@clapideas.com or use our contact page.
We will formally review accessibility before public launch.

1. Our commitment

Clap Ideas exists to democratize ideas. That goal only works if the platform is open to everyone, including people who use assistive technology such as screen readers, screen magnifiers, voice control, or keyboard-only navigation. We are committed to making Clap Ideas perceivable, operable, understandable, and robust for as many people as possible.

2. The standard we aim for

We use the Web Content Accessibility Guidelines (WCAG) 2.2, level AA as our target and baseline. WCAG is an international standard for making web content more accessible. Aiming for level AA means we work toward clear, well-tested accessibility across the platform.

This is a goal we work toward, not a guarantee that the whole platform fully conforms today. Accessibility is ongoing work. We test, find gaps, and fix them over time.

3. Accessibility features we provide

The platform is built with these access features:

Keyboard navigation. You can move through and use the platform with a keyboard, without needing a mouse.
Skip-to-content link. A skip link lets keyboard and screen-reader users jump straight to the main content, past the header.
Semantic structure and labels. We use semantic landmarks (such as header, navigation, main, and footer) and ARIA labelling so assistive technology can understand the page.
Visible focus. Interactive elements show a clear focus outline so you can see where you are on the page.
Light and dark themes. You can choose a light or dark theme to suit your visual comfort.
Reduced motion. If your device is set to reduce motion, we respect that preference and limit animation.
Responsive, mobile-friendly layouts. Pages adapt to different screen sizes and to zoom, so content stays usable on phones, tablets, and desktops.
Clear forms. Form fields have visible labels, and validation messages explain what needs fixing.

4. Known limitations

We want to be honest about where we still fall short. Accessibility is never finished, and some areas need more work:

Some complex, interactive areas may not yet be fully optimised for every assistive technology or every browser.
AI-generated visualisations, charts, or summaries may not yet have complete text alternatives in every case.
Some third-party content or embedded tools may have their own accessibility limits that are outside our direct control.

We treat these as work in progress and keep improving. If you hit a barrier we have not listed, please tell us — it helps us prioritise fixes.

5. How to get help or report a barrier

If something on Clap Ideas is hard to use, or you cannot access content you need, contact us and we will help:

Email support@clapideas.com.
Use our contact page.

We respond by email only; we do not offer telephone support. Please tell us the page or feature, what went wrong, and the device, browser, or assistive technology you were using. That helps us reproduce and fix the problem. We aim to acknowledge accessibility reports promptly and to work with you on a solution or an alternative way to get what you need. For a friendlier overview of our approach, see our accessibility overview.

6. Review and formal assessment

Conformance with WCAG 2.2 AA will be formally reviewed before public launch. We expect to assess the platform, record the results, and update this statement with what we find and what we are working to improve. As the platform changes, we will keep testing and revisiting this statement.

For accessibility help, email support@clapideas.com or use our contact page. You can also read our friendlier accessibility overview.

Change history is tracked by document version; see the Legal Centre.