Request an accessibility specification

The form below collects the context needed to prepare an accessibility specification for a website or a section. A useful specification connects user needs to critical processes, components, acceptance evidence and responsibilities.

Discussion of user needs and a task journey leads to structured interface requirements.

Pilot operation

The request service works in pilot mode. The time of the answer and the queue of requests are not guaranteed: the questionnaire is read and processed by a person, not by an automatic tool. Personal data are not requested: contact with the applicant is established only through Telegram, using the link that appears after the questionnaire is sent, the same way as in the website check service.

Request questionnaire

Website

The full address with http:// or https://, for example https://example.org. Leave the field empty if the site does not exist yet.

Category of the site owner

The owner category is one input to the requirements profile. Applicable law and contractual requirements depend on the jurisdiction, resource and procurement context. See the international overview and record the requirements that apply to this project; the listed national examples are not cumulative obligations.

Type of the product
Critical processes

Name the processes that must be completed by a user, for example signing in or submitting an application.

Target groups

By the needs profile of the development methodology. Several groups may be selected.

Target profile

By default WCAG 2.2 AA.

Technologies and third-party components
Documents and media
Stage
What is needed as a result

State the relevant countries or regions, and any known legal, procurement or contractual requirements. Add other context needed to prepare the specification.

Describe the product

Name the public service, its audience and the environments that matter. Identify critical processes such as registration, search, purchase, payment, document upload or support. Explain whether authentication, personal data or third-party components affect testing.

Describe access needs

Cover keyboard use, screen readers, magnification, colour and contrast, captions and transcripts, clear language, predictable interaction and enough time. The needs brief can help structure this discussion.

Define acceptance

State which versions, pages, states, platforms and documents will be checked. Combine automated evidence with manual checks and, where appropriate, research with disabled users. Name the evidence expected at handover and the process for repairing and retesting defects.

Review the result

A generated specification is a starting point for human review. Product owners, developers, assessors and procurement or legal specialists should confirm scope, national requirements and contractual wording before use.