Translate procurement requirements into user journeys
Begin by mapping the service outcomes named in a contract: apply, register, report, pay, request information, manage a case, or publish a decision. Then identify the public pages, authentication, forms, documents, dashboards, notification emails, and third-party services involved. Clearpath checks missing form labels, unclear link purpose, heading structure, missing landmarks, missing page language, invalid ARIA roles, broken ARIA references, and duplicate IDs. Those signals are most useful when attached to a route, component, release, and user journey rather than treated as an isolated score. Include content editors, delivery partners, and the contracting authority's representative in the review, because a technically sound template can still expose unclear instructions or an inaccessible document supplied by another team.
Forms, documents, and public information
Public services often rely on long forms, data tables, notices, maps, PDFs, and status messages. Use visible labels and appropriate autocomplete tokens for personal information, connect help and errors to the correct control, and make the sequence understandable at large text sizes. Tables need real header relationships; maps need equivalent text; headings and landmarks need to support direct navigation. Clearpath checks missing autocomplete, missing form labels, unhelpful error messages, missing table headers, blocked zoom, low colour contrast, missing alt text, and heading structure. A scan cannot inspect every document's reading order or decide whether policy language is understandable. Include representative PDFs and downloadable files in the procurement evidence, and test submission, saved drafts, timeouts, error recovery, and any translated or multilingual route.
Subcontractors, embeds, and conformance evidence
Suppliers often integrate identity, payment, video, mapping, chat, analytics, or case tools that are owned elsewhere. A meaningful iframe needs a useful title, and a component with a custom role needs a complete accessible name, state, and keyboard behaviour. Clearpath can surface missing iframe titles, invalid ARIA roles, keyboard traps, suppressed focus indicators, missing captions, and broken references, but responsibility should be assigned explicitly in the service boundary. Keep a record of the URL and build version tested, browser and assistive technology used, findings, exceptions, remediation dates, and retest evidence. Avoid copying a generic accessibility statement across contracts when the actual scope differs. Procurement reviewers need an honest account of what was measured, what remains uncertain, and what users can do if they encounter a barrier.
Price the work as delivery risk reduction
Run a free Clearpath scan early enough that findings can influence architecture and bid assumptions, then use pricing to cover the number of services, environments, templates, releases, and partner integrations rather than simply counting URLs. The cost of failure can include rework during acceptance, delayed launch, contract remedies, additional assisted service, exclusion of residents, and reputational damage. Recurring monitoring is useful when a supplier maintains many public services or ships frequent changes, while a focused manual audit is essential before a major acceptance milestone. Pair automation with keyboard, screen-reader, zoom, content, document, mobile, and task testing. Frame EAA or WCAG references carefully: contractual obligations and national public-sector rules differ, and a technical finding is evidence for action rather than a universal legal verdict.
Frequently asked
Questions about this issue
- Can a scan satisfy a public-sector accessibility contract?
- Usually not by itself. It can provide repeatable technical evidence and help prioritise work, but the contract may require manual testing, documents, user research, conformance reporting, or specific delivery evidence.
- Who owns accessibility when a supplier embeds another service?
- Define the boundary in delivery and procurement documents, but test the complete user journey. Record the provider, observed barrier, workaround, remediation owner, and any accepted risk.
- Should supplier audits include PDFs and documents?
- Yes, when residents or officials must use them. Check reading order, headings, language, tables, alternatives, form fields, and the document's relationship to the HTML service.
- Why monitor after acceptance?
- Templates, content, dependencies, and releases change. Recurring checks help catch regressions before they become a new acceptance issue or block a public task.
Check your own site for this issue
Run a free quick scan and Clearpath will surface this and other accessibility findings with the exact element and a practical fix.