Accessibility statement generator - AccessibilityTeam.eu

Step 1: Document context

Statement scope ● required
Affects the document content

Scope

Website

Mobile application

Website + application

Site / store URL wymagane

Document identifier dobrowolne

If empty — the generator will assign one automatically.

Step 2: Entity and dates

Entity (name) wymagane

Publication date (YYYY-MM-DD) wymagane

Publication date of the website / mobile app release.

Date of last significant update (YYYY-MM-DD) wymagane

Statement preparation date (YYYY-MM-DD) wymagane

Date of last statement review (YYYY-MM-DD) optional

Becomes required after the first review.

Step 3: Status and inaccessible content

Accessibility status

Fully conforming

Partially conforming

Non-conforming

Non-conformance with the annex

List digital accessibility issues that need fixing. Describe problems in plain, non-technical language.

Issue title required

Short description required

Content not covered by the rules

Required if applicable (e.g. archived documents).

Title optional

Short description optional

Disproportionate burden

Required if applicable — e.g. a feature inaccessible due to disproportionate financial burden.

Cost description optional

Short description optional

Link to digital accessibility cost analysis optional

Required when disproportionate burden is filled in.

Facilities, limitations and other information

Optional — e.g. information about workarounds to ensure accessibility of inaccessible content

Title optional

Short description optional

Keyboard shortcuts

Required if applicable — information about non-standard keyboard shortcuts used on the site.

Shortcut / description optional

Short description optional

Basis for preparation wymagane

Indicate how accessibility was checked.

Step 4: Contact

Contact wymagane

Full name of the person or name of the organisational unit responsible for digital accessibility contact.

Contact email wymagane

Phone (E.164 format, e.g. +48123456789) required

Phone (display format, e.g. 12 345 67 89) required

Feedback section content optional

Default text comes from Ministry of Digital Affairs guidelines. If left empty, the matching template is inserted automatically for the selected scope (website or mobile app).

Step 5: Complaints

Complaints section intro text optional

Default text comes from Ministry of Digital Affairs guidelines. If left empty, the matching template is inserted automatically.

Complaint addressee wymagane

Address wymagane

Email wymagane

Step 6: Mobile apps

Required if the service includes mobile applications.

Application name optional

App link (store URL) optional

Link to the app accessibility statement optional

Link title (alternative text, e.g. go to Google Play) optional

Step 8: Generate statement

Are you sure you want to generate the statement?

Check all data before generating. After generation you can copy or download the HTML file.

Basis for preparation:

Will appear after the form is completed

💡 We recommend a professional accessibility assessment

This generator helps create a basic accessibility statement. For a full WCAG 2.2 conformance assessment we recommend a professional accessibility audit by certified experts.

A professional assessment includes assistive-technology testing, WCAG 2.2 AA conformance evaluation and detailed reports with recommendations.

Preview updates when you move between steps; the “Generate” button runs full validation.

Step 9: Preview and download