1. Define the thing being evaluated
Name the website, app or document set; its version; important user journeys; public and authenticated areas; and the platforms in scope. A sample of pages is not automatically an assessment of the whole product.
2. Agree a conformance target
Ask the provider to name the WCAG version and level and explain any additional requirements. Ask how applicable criteria and non-web content will be handled. Provider-issued certificates are not government accreditation or a legal guarantee.
3. Understand the method
Ask what is automated, what is tested manually, which browsers and assistive technologies are used, and who performs the work. Clarify keyboard testing, focus, forms, errors, navigation, media and complete user journeys. An automated scan alone is not a complete evaluation.
4. Separate an audit from user research
Technical checks and real-world user research answer different questions. If you need testing involving disabled people, ask about recruitment, access requirements, consent, compensation and representation. Do not assume a generic usability test includes these elements.
5. Specify useful findings
Request a sample report. Agree how issues will identify the affected element, reproduction steps, user impact, relevant criterion and suggested fix. Clarify whether design and engineering teams receive a walkthrough.
6. Budget for fixes and retesting
Ask whether the provider implements changes or only advises. Agree responsibility for remediation, third-party components, retest limits and handling changes after the evaluation. A dated report cannot guarantee future conformance.
Questions to put in your brief
What is included and excluded? Who does the testing? Which standards and methods apply? What do we receive? How are disabled users involved? Who fixes issues? How many retests are included? What are the price, delivery date and confidentiality terms?