Accessibility
Accessibility Statement
TenderReader aims to meet WCAG 2.2 AA for public and core product journeys, while honestly tracking the gaps that still need audit evidence.
Last updated: 12 June 2026
Current status
The app uses server-rendered HTML, visible focus styles, skip links, semantic headings, labels, Playwright smoke checks, and a CI Lighthouse accessibility gate for selected core pages.
The Day 88 production audit found and fixed a mobile overflow issue on the data-accuracy page. A full independent accessibility audit has not been completed yet.
Known limitations
- Generated PDFs and uploaded tender documents may inherit accessibility issues from source files.
- Very dense extracted source text can still require careful manual review on small screens.
- French legal pages currently show English governing copy until a reviewed translation is ready.
Feedback
If you find an accessibility barrier, use the operator contact channel already used for your TenderReader account or onboarding conversation. Include the page, browser, assistive technology, and what you were trying to do.