Accessibility Statement
Last reviewed: May 17, 2026
Partial Compliance — In Progress
Aiscern is working toward WCAG 2.1 Level AA compliance. Some areas are not yet fully compliant. We are actively addressing known issues and welcome feedback.
1. Our Commitment
Aiscern is committed to ensuring digital accessibility for people with disabilities. We continually improve the user experience for everyone, and apply the relevant accessibility standards.
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. These guidelines explain how to make web content more accessible to people with a wide range of disabilities.
2. Conformance Status
The current conformance status of Aiscern is partially conformant with WCAG 2.1 Level AA.
Partially conformant means that some parts of the content do not fully conform to the accessibility standards.
Keyboard Navigation
All interactive elements are accessible via keyboard. Tab order is logical throughout.
Colour Contrast
Text contrast ratios meet or exceed 4.5:1 for normal text and 3:1 for large text across the dark theme.
Touch Targets
All touch targets are a minimum of 44×44px (Apple HIG / WCAG 2.5.5).
Font Sizing
Base font size is 16px on mobile, preventing iOS auto-zoom. Users can resize text up to 200% without loss of content.
Reduced Motion
All animations respect prefers-reduced-motion. Framer Motion animations are disabled for users who opt out.
Skip Navigation
A 'Skip to main content' link is available at the top of every page.
Semantic HTML
Pages use landmark roles (main, nav, header, footer), heading hierarchy, and ARIA labels where appropriate.
Screen Reader Testing
Automated testing via axe-core has been performed. Manual screen reader testing with NVDA/JAWS is in progress.
Complex Widgets
The scan result confidence visualisations and animated charts may not convey all information to screen reader users. Text alternatives are being added.
File Upload
The drag-and-drop file upload interface has keyboard fallback but may present challenges for some assistive technologies.
WCAG 2.1 Full Audit
A formal third-party WCAG audit has not yet been completed. We plan to commission one in Q3 2026.
3. Technical Specifications
Aiscern relies on the following technologies for conformance:
- HTML5 semantic markup
- CSS (Tailwind CSS with focus-visible support)
- JavaScript (Next.js React — server and client components)
- WAI-ARIA 1.2 where native HTML semantics are insufficient
The following assistive technologies have been tested:
- Chrome + ChromeVox (automated)
- axe-core browser extension (automated)
- iOS VoiceOver (basic manual testing)
4. Known Limitations
Despite our best efforts to ensure accessibility of Aiscern, there may be some limitations. Below is a description of known limitations and potential workarounds:
- Detection result confidence rings: SVG-based visualisations may not be announced correctly by all screen readers. A numeric percentage is always displayed as a text alternative.
- Real-time scan progress: Live detection updates use aria-live regions but may announce too frequently. We are reviewing announcement frequency.
- PDF export: Generated PDFs are not yet tagged for accessibility. Tagged PDF output is planned for a future release.
- Video player (demo): The homepage hero video does not currently have captions. We are adding caption support.
5. Feedback and Contact
We welcome your feedback on the accessibility of Aiscern. Please let us know if you encounter accessibility barriers:
- Email: accessibility@aiscern.com
- Response time: We aim to respond within 2 business days
We try to respond to feedback within 2 business days. If you are not satisfied with our response, you can contact the relevant supervisory authority in your jurisdiction.
6. Formal Complaints
If you are located in the EU and are not satisfied with our response to your accessibility feedback, you have the right to contact your national accessibility enforcement authority. In the UK, you may contact the Equality and Human Rights Commission.
7. Assessment and Roadmap
Aiscern assesses the accessibility of our platform through:
- Self-evaluation using axe-core automated testing on every deployment (CI/CD)
- Manual keyboard navigation testing on all new features
- Review of user feedback and accessibility bug reports
Planned improvements:
- Q2 2026: Complete manual screen reader testing (NVDA + JAWS)
- Q3 2026: Commission formal third-party WCAG 2.1 AA audit
- Q3 2026: Tagged PDF export
- Q4 2026: Full WCAG 2.1 AA conformance target
