Accessibility Statement - CometWeb Insight

Last reviewed: July 17, 2026 | Target: WCAG 2.1 AA

CometWeb is a website-quality platform — accessibility is one of the things we measure for our users, so we hold our own product to the same standard. We work to make the app.cometweb.io application usable by as many people as possible, including people who rely on a keyboard, a screen reader, or other assistive technology. This statement describes where we stand and is written to be honest rather than reassuring.

1. Conformance status

We target WCAG 2.1 level AA. Today the application is partially conformant: most of the interface meets AA, but some parts do not yet fully conform (see "Known limitations"). We do not hold, and do not claim, any formal accessibility certification or third-party audit seal — this is a self-assessment backed by automated testing and an internal expert review.

2. How we test

Automated checks with axe-core (WCAG 2.2 AA rulesets) in our end-to-end test suite, covering both signed-out and signed-in views. We run them periodically and when the interface changes; they are not part of an automated gate that blocks every release.
Keyboard-navigation checks in the same suite: skip link to main content, focus management in dialogs and drawers, Escape handling, and ARIA roles on menus and comboboxes.
An external accessibility code review of the application was completed in July 2026; identified blockers and quick-win fixes have been shipped, and remaining items are tracked internally.

3. Known limitations

We want to be straightforward about the gaps:

Automated scope. Automated tools only catch a portion of possible issues; they cannot judge whether alt text is meaningful, whether reading order makes sense, or whether an interaction is intuitive. Some barriers can still exist even when our checks pass.
Legacy views. A few older, data-dense screens have not yet been through the same manual review as the rest of the app, and may have contrast, focus-order, or labelling issues we are still working through.
Complex visualisations. Charts and interactive report widgets expose the underlying data, but some do not yet have a fully equivalent non-visual presentation.
Third-party components. Embedded flows we do not fully control (for example the payment checkout) follow the provider's own accessibility level.

4. Feedback and contact

If you find something you cannot use, or an accessibility barrier we have not listed, please tell us — your report genuinely helps us prioritise. Email hello@cometweb.io with the page address and a short description of the problem (and, if you can, the browser and assistive technology you were using). We aim to acknowledge accessibility reports within 48 business hours. If we cannot resolve an issue quickly, we will let you know and, where possible, suggest an alternative way to access the content or complete the task.

Escalation. We respond to accessibility reports no later than 30 days from receipt. If that is not possible we will tell you why and give a new deadline, no more than 2 months out. If you consider our response inadequate, or we do not respond in time, you may complain to the market surveillance authority for the accessibility of products and services — in Poland the President of the State Fund for Rehabilitation of Disabled Persons (PFRON), under the Act of 26 April 2024 implementing Directive 2019/882 (European Accessibility Act). You may complain regardless of whether you used the contact route above.

5. Preparation and review

This statement was prepared on July 17, 2026 based on our own assessment (automated axe-core testing and an internal expert review of the interface). We review it periodically — at least once a year and whenever we ship a significant change to the interface — and update it as our conformance and known limitations change.