Our commitment
Bid Champions wants people to be able to read, navigate and use this website regardless of device, input method or disability. The build target is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. That target is used as an engineering and editorial baseline; it is not presented as a completed certification.
How the site should work
The implemented design is intended to let users:
- navigate the header, links, controls and disclosure panels using a keyboard;
- skip directly to main content and see a strong visible focus indicator;
- zoom and reflow content on narrow screens without a separate mobile-only page;
- use landmarks, headings, labels, lists and tables exposed as semantic HTML;
- understand controls without relying on colour or an icon alone;
- reduce non-essential motion through the operating-system preference;
- read text alternatives for meaningful non-text content; and
- receive specific form errors and status messages without a false success state.
Testing completed so far
The release suite checks generated HTML, duplicate IDs, links and anchors, missing assets, metadata, route coverage, security headers and responsive budgets. Automated accessibility testing covers representative routes plus 320-pixel reflow, zoom-equivalent layouts, reduced motion, text spacing, forced-colour visibility, keyboard focus and control targets. The current run reports no serious or critical automated findings.
Automated checks cannot replace testing with disabled users and representative assistive technologies. Manual review therefore remains part of ongoing maintenance, particularly after changes to navigation, interactive tools, forms or document downloads.
Known limitations and open work
- Manual coverage: not every canonical page has been exercised with every browser and assistive-technology combination.
- Forms: the contact form has explicit labels, native validation, an accessible error summary, a live status message and keyboard-operable controls. Direct public file upload is not offered.
- Research pages: long service and sector pages may require additional navigation effort. Shared headings, breadcrumbs, section structure and related links are used to support orientation.
- Third-party maps: live Google Maps frames are embedded on the Contact and office pages. Each map has a descriptive frame title, and the full postal address and a directions link remain available as accessible alternatives.
- Documents: no future PDF or office document should be published without an accessibility check and an HTML alternative where needed.
When a specific failure is confirmed, this statement will identify the affected feature, user impact, available workaround and planned correction where those details are known.
Request help or an alternative format
If a page is difficult to use, or you need information in another format, email info@bidchampions.com. Include the page address, what you were trying to do, the problem encountered, and your preferred format or contact method. Do not include confidential tender material in an accessibility report.
No telephone accessibility route is currently published. Email is the available contact method and lets the sender describe the required format or communication adjustment.
If the response does not resolve the problem
Reply to the same email thread and ask for the issue to be escalated to the website owner. You may also seek independent advice about any rights that apply to your circumstances.
Technical approach
The site uses server-generated HTML, local styles and restrained JavaScript. Core content and navigation do not depend on cookies, analytics, drag gestures, hover alone or a screenshot used as a page. Focus styles, a skip link, semantic headings, labelled controls, reduced-motion handling and responsive reflow are built into the shared layer so fixes apply consistently.
Preparation and review
This statement was updated on 18 August 2026 and informed by GOV.UK guidance on testing against WCAG 2.2 AA and publishing an accessibility statement. That guidance is a testing reference; it does not certify this implementation.
The statement is rechecked after material changes to forms, navigation, visual components, third-party embeds or after a recorded accessibility defect.