Accessibility statement
This statement covers the TenderSeal web app at web.tenderseal.com, provided by TENDERSEAL LTD. We want everyone who bids for work to be able to use it, including people who use a keyboard instead of a mouse, a screen reader, magnification, or their own colours and text sizes.
1. How accessible TenderSeal is
TenderSeal partially conforms with the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. "Partially" means most of the app meets the standard, and the parts that do not yet are listed in section 2.
What you can expect:
- Every page can be used with a keyboard alone, with the exceptions in section 2. "Skip to main content" is the first thing the Tab key reaches, and the control with keyboard focus always shows a blue outline.
- Text and controls have enough colour contrast to read at WCAG AA, including the colours that show status (green, amber and red).
- Buttons, fields and dialogs have names a screen reader announces, and the app's dialogs keep focus inside them until you close them, with Escape or their Close button.
- Pages that need a large screen tell you so on a small one, and let you carry on.
- The app follows the language you choose in Profile, and tells your browser which language each page is in.
2. What is not accessible yet
- The document editor. Writing and formatting work with a keyboard, but some blocks (tables, columns, equations and embedded media) are hard to follow with a screen reader, and moving a block is done by dragging it or with its block menu. To move a block by keyboard, cut and paste it.
- The Knowledge Hub's graph is a picture of your past bids. Each bid in it can be reached with the Tab key and opened with Enter, which shows its details as text, but the links between bids are only drawn.
- PDFs in the document viewer are shown as their original pages. A PDF that is a scan without text cannot be read aloud; TenderSeal's analysis of it appears as text in the tender's tabs.
- Videos and audio added to a document have captions only if whoever added them provides them.
- Charts are not described to screen readers yet.
We are working on these, and update this statement as each is fixed.
3. How we tested it
- Every page a customer reaches is checked automatically on each change with axe (Deque's accessibility engine), against WCAG 2.2 A and AA, and a serious or critical failure stops the change from shipping.
- The app's code is checked for accessibility mistakes (eslint-plugin-jsx-a11y) on each change.
- Some keyboard journeys are tested automatically in a browser: reaching "Skip to main content" and moving to the page, opening a document from its card, and closing a dialog with Escape.
- We have not yet had the app tested by an outside auditor or by screen reader users. Until we have, we do not claim full conformance.
4. Tell us about a problem
If something in TenderSeal does not work for you, or you need information in a different format, please tell us:
- email support@in.tenderseal.com, or
- use Help & feedback in the app.
Say which page you were on and what happened. We reply within two working days, and we will tell you how and when we will fix it, or help you do what you came to do in another way.
5. If you are not happy with our response
TenderSeal is a private company in the United Kingdom, so the Equality Act 2010 applies to us. If you are not happy with how we respond to a complaint about accessibility, you can contact the Equality Advisory and Support Service (EASS).
6. About this statement
This statement was prepared on 25 October 2026, from our own testing. We will review it by October 2027, and sooner whenever something in section 2 changes.