Accessibility Conformance Report Template (WCAG 2.2, EN 301 549, Section 508)

ACR for one product version: scope, standards and legal context, methods, conformance terms, WCAG 2.2 A/AA, EN 301 549 V4.1.1 and Section 508 tables, issue plan

Tests & QualitéCompletWCAG 2.2 (ISO/IEC 40500:2025); EN 301 549 V4.1.1; Revised Section 508accessibility conformance reportMis à jour 29 oct. 2026

Ouvrir dans l'éditeurTélécharger .md

Mode d'emploi: Use it when a buyer or tender asks how your product meets WCAG 2.2, EN 301 549 or Section 508. Fill scope and methods first and link the evaluation evidence, then the WCAG table that the other two reports point to. The main pitfall is a report that covers all versions or uses vague terms such as mostly supports.

Aperçu

Accessibility Conformance Report: [Product name and version]

Accessibility conformance report (ACR) for one version of an ICT product: a web application, its downloadable documents, any native software and the support documentation that comes with it. It reports conformance against three references in one document: WCAG 2.2 levels A and AA (W3C Recommendation, also published as ISO/IEC 40500:2025), the harmonised European standard EN 301 549 V4.1.1 (2026-09) and the Revised Section 508 Standards of the US Access Board. Buyers in public and regulated procurement ask for this kind of report before they purchase. Replace every [bracketed] value and every row marked Example. This is a documentation format, not legal advice: legal facts are dated October 2026, so check the current official text and a qualified professional before relying on them.

Document control

Field	Value
Document ID	[ACR-PRODUCT-2026-001]
Product name and version	[Quillfern Desk 5.2] (Example)
Product type and platforms	[Web application, desktop and mobile browsers; PDF exports] (Example)
Vendor	[Organisation name and address]
Report date	YYYY-MM-DD
Evaluation dates	YYYY-MM-DD to YYYY-MM-DD
Version	[1.0]
Status	[Draft / Published / Superseded]
Owner	[@accessibility-lead]
Classification	[Public / Customer confidential]
Last updated	YYYY-MM-DD
Standards reported	[WCAG 2.2 A and AA; EN 301 549 V4.1.1; Revised Section 508]
Evaluation evidence	[Link to evaluation report and test records]
Contact for accessibility questions	[accessibility@example.com, or a web form]

Approvals

Role	Name	Decision	Date
Accessibility lead	[@name]	[Approved]	YYYY-MM-DD
Product owner	[@name]	[Approved]	YYYY-MM-DD
Legal or compliance reviewer	[@name]	[Reviewed]	YYYY-MM-DD

Revision history

Version	Date	Author	Change summary
0.1	YYYY-MM-DD	[@name]	Draft from evaluation results
1.0	YYYY-MM-DD	[@name]	Example: Published for release 5.2
1.1	YYYY-MM-DD	[@name]	Example: Remarks updated after fix of ACR-ISS-003 in 5.2.1

Report summary
Product and scope of the report
Standards and legal context
Evaluation methods
Conformance terms used in this report
WCAG 2.2 report
EN 301 549 V4.1.1 report
Revised Section 508 report
Known issues and remediation plan
Publication, maintenance and disclaimer
Glossary and references

1. Report summary

[Product name and version] was evaluated between YYYY-MM-DD and YYYY-MM-DD against WCAG 2.2 levels A and AA, EN 301 549 V4.1.1 and the Revised Section 508 Standards. The evaluation combined expert manual review, assistive technology testing and automated checks (section 4).

Example: Quillfern Desk 5.2 supports 40 of the 55 WCAG 2.2 level A and AA success criteria. Seven criteria are partially supported, one is not supported and seven are not applicable because the product contains no audio, video or motion-operated features. The main limitations are the drag-only ticket board (2.5.7), keyboard access to that board (2.1.1) and the custom assignee picker (4.1.2). Fixes are scheduled for 5.3 (section 9).

1.1 WCAG 2.2 summary by level

Level	Criteria	Supports	Partially supports	Does not support	Not applicable
A	31	Example: 22	4	0	5
AA	24	Example: 18	3	1	2
Total A and AA	55	40	7	1	7

WCAG 2.2 has 86 success criteria in total (31 at level A, 24 at level AA and 31 at level AAA); criterion 4.1.1 Parsing is marked obsolete and removed in WCAG 2.2, so it is not counted. Level AAA is not part of this claim and is not evaluated unless section 6.3 says otherwise.

1.2 Headline limitations for buyers

ID	Limitation	Users most affected	Workaround	Planned fix
ACR-ISS-001 (Example)	Ticket board can be reordered only by dragging	Keyboard, switch and voice control users	Change status in the ticket detail form	5.3, YYYY-MM-DD
ACR-ISS-002 (Example)	Assignee picker does not expose its expanded state or selected option	Screen reader users	Type the assignee e-mail in the plain text field under "Advanced"	5.3, YYYY-MM-DD
[ACR-ISS-nnn]	[Limitation]	[Users]	[Workaround]	[Release, date]

2. Product and scope of the report

2.1 Product description

[Two or three sentences: what the product does, who uses it, how it is delivered.]

Example: Quillfern Desk is a software-as-a-service help desk used by support agents to manage customer tickets and by end customers to submit and track requests through a self-service portal. Agents can export ticket histories as PDF files and write knowledge base articles in a built-in editor.

2.2 Components in scope

Component	Version or build	Platforms and assistive technology context	In scope
Agent web application (Example)	5.2.0	Current Chrome, Edge, Firefox and Safari on Windows 11 and macOS	Yes
Customer self-service portal (Example)	5.2.0	As above, plus Safari on iOS and Chrome on Android	Yes
PDF ticket export (Example)	5.2.0 export engine	Acrobat Reader with NVDA on Windows	Yes
Knowledge base editor (Example)	5.2.0	As agent web application	Yes, as an authoring tool
Help centre and support documentation (Example)	Content as of YYYY-MM-DD	Web	Yes
[Component]	[Version]	[Platforms]	[Yes / No]

2.3 Exclusions

Excluded item	Reason	Where to find information
Content written by customers in tickets and articles (Example)	Customer content, outside vendor control	Authoring support is covered in 7.2 and 8.3
Third-party chat widget (Example)	Separate product, optional integration	Supplier's own ACR [link]
Administration API (Example)	No user interface	Not applicable
[Item]	[Reason]	[Link]

3. Standards and legal context

3.1 Standards applied

Standard	Version and date	Levels or clauses reported	Report section	Official text
Web Content Accessibility Guidelines	WCAG 2.2, W3C Recommendation (identical text published as ISO/IEC 40500:2025)	Levels A and AA	6	https://www.w3.org/TR/WCAG22/
EN 301 549, Accessibility requirements for ICT products and services	V4.1.1 (2026-09), ETSI, CEN and CENELEC	Clauses 4 to 13 as applicable	7	Free download from ETSI, see 11.2
Revised Section 508 Standards	Final rule of 18 January 2017 (36 CFR part 1194, Appendices A and C)	Chapters 3, 5 and 6, and E205 and E207 via WCAG	8	https://www.access-board.gov/ict/

The Revised Section 508 Standards incorporate WCAG 2.0 levels A and AA by reference (section 702.10.1). WCAG 2.2 keeps every WCAG 2.0 success criterion except 4.1.1 Parsing, so the WCAG 2.2 results in section 6 answer the Section 508 question for every other WCAG 2.0 criterion; the rows for criteria added in WCAG 2.1 and 2.2 go beyond what Section 508 requires. Section 508 still incorporates WCAG 2.0, which includes 4.1.1, so report it separately in section 8.1 (W3C's current WCAG 2.1 text notes that 4.1.1 should be considered always satisfied for content using HTML or XML).

3.2 Legal context (dated examples, October 2026)

Region	Law or rule	Role of this report	Status note
EU	European Accessibility Act, Directive (EU) 2019/882; national measures apply from 28 June 2025	Evidence for the conformity information a provider must keep and publish; EN 301 549 V4.1.1 Annex ZB maps its clauses to the Act's requirements, and clause A.2 lists the clauses to meet	V4.1.1 gives a presumption of conformity only once cited in the Official Journal; until then the cited version is V3.2.1 (citation of V4.1.1 expected 16 December 2026, check the current list)
EU	Web Accessibility Directive (EU) 2016/2102, public sector websites and apps	Public bodies buying the product ask for evidence that their site or app can meet EN 301 549; Annex ZA maps the clauses	As above
UK	Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018	Public sector buyers ask suppliers for WCAG 2.2 AA evidence	Check current GOV.UK guidance
US	Section 508 of the Rehabilitation Act, Revised Section 508 Standards	Federal contracting officers use ACRs in market research and evaluation	WCAG 2.0 A and AA by reference
Any	Contract or tender clause	[Clause reference and required standard version]	[Contract date]

Questions for the legal or compliance owner (not legal advice):

Which version of EN 301 549 does each EU buyer's contract or national law cite on the date of delivery?
Does the product fall within the scope of Directive (EU) 2019/882 as a product, as part of a service, or neither?
Is any exemption claimed (for example disproportionate burden), and is the assessment documented?
Does the report need to be published, or only supplied on request?

4. Evaluation methods

4.1 Method

Item	Value
Method	[WCAG-EM 2.0 sampled evaluation / full manual review / third-party audit]
Evaluator	[Internal accessibility team / independent organisation name]
Independence	[Not involved in building the product / part of the product team]
Sample	[Number of screens, states and complete processes; link to sample list]
Complete processes tested	[Sign in, create ticket, reply, assign, close, export PDF, write article] (Example)
Testing with disabled users	[Yes, n participants, dates / No]

4.2 Assistive technologies and browsers

Assistive technology	Version	Browser or platform	Used for
NVDA (Example)	[Version]	Firefox and Chrome on Windows 11	Screen reader testing of all processes
JAWS (Example)	[Version]	Chrome on Windows 11	Agent application spot checks
VoiceOver (Example)	[Version]	Safari on macOS and iOS	Portal processes
TalkBack (Example)	[Version]	Chrome on Android	Portal processes
Voice control (Example)	[Product, version]	Windows or macOS	Voice operation of forms
Browser zoom and text spacing tools (Example)	Built in	All browsers	Reflow, resize and spacing
[Tool]	[Version]	[Platform]	[Use]

4.3 Automated tools

Tool	Version	Scope	Note
[Automated rule engine]	[Version]	[All sampled pages]	Automated checks find only part of the failures; every result was reviewed manually
[PDF accessibility checker]	[Version]	[Sample of exported PDFs]

4.4 Evidence

[Link to the evaluation report, test records and issue tracker query. Keep the evidence for at least the life of this report version.]

5. Conformance terms used in this report

Term	Meaning in this report
Supports	Every part of the product in scope meets the criterion, with no known failures
Partially supports	Some functions or content in scope fail the criterion; the remarks name them
Does not support	Most of the functions or content that the criterion applies to fail it
Not applicable	The product has no content or function to which the criterion applies; the remarks say why
Not evaluated	Used only for level AAA criteria that were not tested; never used for level A or AA

These terms follow common procurement practice for accessibility conformance reports. The definitions above are written for this template; if a buyer prescribes its own definitions, use the buyer's. EN 301 549 Annex C tests have their own result values (pass, fail, not applicable, and test assumptions not met); record them in the evaluation evidence and translate them into the terms above here.

6. WCAG 2.2 report

Each row applies to the web application and portal. Remarks say when PDF exports (EN 301 549 clause 10) or the knowledge base editor behave differently.

6.1 Level A

Criterion	Conformance	Remarks and explanations
1.1.1 Non-text Content	Example: Partially supports	Charts on the reports dashboard have no text alternative or data table (ACR-ISS-004)
1.2.1 Audio-only and Video-only (Prerecorded)	Example: Not applicable	No audio or video content
1.2.2 Captions (Prerecorded)	Example: Not applicable	No video content
1.2.3 Audio Description or Media Alternative (Prerecorded)	Example: Not applicable	No video content
1.3.1 Info and Relationships	Example: Partially supports	Report tables lack header associations; PDF exports are tagged but table headers are missing (ACR-ISS-005)
1.3.2 Meaningful Sequence	Example: Supports
1.3.3 Sensory Characteristics	Example: Supports
1.4.1 Use of Color	Example: Supports	Ticket priority shows text and colour
1.4.2 Audio Control	Example: Not applicable	No audio plays automatically
2.1.1 Keyboard	Example: Partially supports	Ticket board cards cannot be moved by keyboard (ACR-ISS-001); all other functions work by keyboard
2.1.2 No Keyboard Trap	Example: Supports
2.1.4 Character Key Shortcuts	Example: Supports	Single-key shortcuts can be turned off in user settings
2.2.1 Timing Adjustable	Example: Supports	Session timeout warns two minutes ahead and can be extended
2.2.2 Pause, Stop, Hide	Example: Supports
2.3.1 Three Flashes or Below Threshold	Example: Supports
2.4.1 Bypass Blocks	Example: Supports
2.4.2 Page Titled	Example: Supports
2.4.3 Focus Order	Example: Supports
2.4.4 Link Purpose (In Context)	Example: Supports
2.5.1 Pointer Gestures	Example: Supports
2.5.2 Pointer Cancellation	Example: Supports
2.5.3 Label in Name	Example: Supports
2.5.4 Motion Actuation	Example: Not applicable	No motion-operated functions
3.1.1 Language of Page	Example: Supports
3.2.1 On Focus	Example: Supports
3.2.2 On Input	Example: Supports
3.2.6 Consistent Help	Example: Supports	Help link in the same place on every page
3.3.1 Error Identification	Example: Supports
3.3.2 Labels or Instructions	Example: Supports
3.3.7 Redundant Entry	Example: Supports
4.1.2 Name, Role, Value	Example: Partially supports	Assignee picker does not expose expanded state or selected option (ACR-ISS-002)

6.2 Level AA

Criterion	Conformance	Remarks and explanations
1.2.4 Captions (Live)	Example: Not applicable	No live media
1.2.5 Audio Description (Prerecorded)	Example: Not applicable	No video content
1.3.4 Orientation	Example: Supports
1.3.5 Identify Input Purpose	Example: Supports
1.4.3 Contrast (Minimum)	Example: Partially supports	Placeholder text in search fields has a contrast ratio of 3.2:1 (ACR-ISS-006)
1.4.4 Resize Text	Example: Supports
1.4.5 Images of Text	Example: Supports
1.4.10 Reflow	Example: Supports	Ticket board scrolls in two dimensions, which the criterion allows for content that needs a two-dimensional layout
1.4.11 Non-text Contrast	Example: Supports
1.4.12 Text Spacing	Example: Supports
1.4.13 Content on Hover or Focus	Example: Supports
2.4.5 Multiple Ways	Example: Supports
2.4.6 Headings and Labels	Example: Supports
2.4.7 Focus Visible	Example: Partially supports	Knowledge base editor toolbar buttons show no focus indicator (ACR-ISS-007)
2.4.11 Focus Not Obscured (Minimum)	Example: Supports
2.5.7 Dragging Movements	Example: Does not support	Ticket board reordering requires dragging; no single-pointer alternative on the board (ACR-ISS-001)
2.5.8 Target Size (Minimum)	Example: Partially supports	Pagination links in ticket lists are 16 by 16 CSS pixels without enough spacing (ACR-ISS-008)
3.1.2 Language of Parts	Example: Supports
3.2.3 Consistent Navigation	Example: Supports
3.2.4 Consistent Identification	Example: Supports
3.3.3 Error Suggestion	Example: Supports
3.3.4 Error Prevention (Legal, Financial, Data)	Example: Supports	Deleting tickets or articles asks for confirmation and can be undone for 30 days
3.3.8 Accessible Authentication (Minimum)	Example: Supports	Password managers and paste allowed; passkeys supported
4.1.3 Status Messages	Example: Supports

6.3 Level AAA (optional)

[Not evaluated / list any AAA criteria evaluated, with results. Do not claim AAA conformance for the whole product; W3C advises against requiring it as a general policy because some content cannot meet it.]

7. EN 301 549 V4.1.1 report

7.1 Functional performance (clause 4.2)

Clause	Topic	Conformance	Remarks
4.2.1	Usage without vision	Example: Partially supports	ACR-ISS-002 and ACR-ISS-004
4.2.2	Usage with limited vision	Example: Partially supports	ACR-ISS-006
4.2.3	Usage without perception of colour	Example: Supports
4.2.4	Usage without hearing	Example: Supports	No audio-only information
4.2.5	Usage with limited hearing	Example: Supports
4.2.6	Usage with no or limited vocal capability	Example: Supports	No voice input required
4.2.7	Usage with limited manipulation or strength	Example: Partially supports	ACR-ISS-001 and ACR-ISS-008
4.2.8	Usage with limited reach	Example: Not applicable	No hardware
4.2.9	Minimize photosensitive seizure triggers	Example: Supports
4.2.10	Usage with limited cognition, language or learning	Example: Supports	Plain-language error messages, consistent help
4.2.11	Privacy	Example: Supports	Accessibility features do not expose ticket content to others

7.2 Generic requirements, communication and video (clauses 5 to 7)

Clause	Topic	Conformance	Remarks
5.1	Closed functionality	Example: Not applicable	Product does not prevent use of assistive technology
5.2	Activation of accessibility features	Example: Supports	Shortcut and motion settings available without assistance
5.3	Biometrics	Example: Supports	Passkey sign-in always has a password or code alternative
5.4	Preservation of accessibility information during conversion	Example: Partially supports	PDF export drops table header markup (ACR-ISS-005)
5.5 to 5.9	Operable parts, locking controls, key repeat, double-strike, simultaneous actions	Example: Not applicable	No hardware keys or physical controls
5.10	Authoring tools	Example: Partially supports	Editor prompts for image alternative text; table headers cannot be marked (ACR-ISS-009)
6	ICT supporting real-time bidirectional communication	Example: Not applicable	No voice, video or real-time text communication
7	ICT with video capabilities	Example: Not applicable	No video playback

7.3 Hardware, web, documents and software (clauses 8 to 11)

Clause	Topic	Conformance	Remarks
8	Hardware	Example: Not applicable	Software product only
9.1 to 9.4	Web content: WCAG 2.2 A and AA success criteria	See section 6	Same results as 6.1 and 6.2
9.6	WCAG conformance requirements	Example: Partially supports	Follows from the partial results in section 6
9.7	User preferences for web pages	Example: Supports	Respects reduced motion and system colour settings
10.1 to 10.4	Non-web documents (PDF exports)	Example: Partially supports	Tagged PDF with document language and reading order; table headers missing (ACR-ISS-005)
10.7	User preferences for non-web documents	Example: Supports
11	Non-web software	Example: Not applicable	No native application in scope; if a native app is added, report clauses 11.1 to 11.7

7.4 Documentation, support and relay services (clauses 12 and 13)

Clause	Topic	Conformance	Remarks
12.1	Accessible information about products	Example: Supports	Help centre meets WCAG 2.2 AA; accessibility features documented
12.2	Accessible information about services	Example: Supports	Support by e-mail, web form and text chat
12.3	Accessibility and compatibility features	Example: Supports	Documented at [help centre URL]
12.4, 12.5	Electronic program guides	Example: Not applicable	Not a broadcast product
13	Relay or emergency service access	Example: Not applicable	Product provides no relay or emergency service

8. Revised Section 508 report

8.1 Electronic content and software through WCAG (E205.4, E207.2)

[Supports with the exceptions listed in section 6.] Example: The WCAG 2.0 level A and AA subset of section 6 applies. Criteria first added in WCAG 2.1 and 2.2 (for example 2.5.7 and 2.5.8) are reported in section 6 but are not Section 508 requirements. For Section 508 purposes the partially supported criteria are 1.1.1, 1.3.1, 1.4.3, 2.1.1, 2.4.7 and 4.1.2.

Criterion	Conformance	Remarks
4.1.1 Parsing (WCAG 2.0, required by Section 508 only)	Example: Supports	Web content uses HTML; W3C's WCAG 2.1 text notes the criterion is always satisfied for HTML or XML content

8.2 Functional performance criteria (chapter 3)

Criterion	Topic	Conformance	Remarks
302.1	Without vision	Example: Partially supports	ACR-ISS-002, ACR-ISS-004
302.2	With limited vision	Example: Partially supports	ACR-ISS-006
302.3	Without perception of color	Example: Supports
302.4	Without hearing	Example: Supports
302.5	With limited hearing	Example: Supports
302.6	Without speech	Example: Supports
302.7	With limited manipulation	Example: Partially supports	ACR-ISS-001
302.8	With limited reach and strength	Example: Supports
302.9	With limited language, cognitive, and learning abilities	Example: Supports

8.3 Software and authoring tools (chapter 5)

Section	Topic	Conformance	Remarks
501	General (software scoping)	[Conformance]	[State whether the web application is treated as software for chapter 5 and why]
502	Interoperability with assistive technology	[Conformance]	[Remarks, or Not applicable with reason]
503	Applications (user preferences, alternative user interfaces, user controls for captions and audio description)	[Conformance]	[Remarks]
504	Authoring tools	Example: Partially supports	Same gap as EN 301 549 clause 5.10 (ACR-ISS-009)

8.4 Support documentation and services (chapter 6)

Section	Topic	Conformance	Remarks
602.2	Accessibility and compatibility features in documentation	Example: Supports
602.3	Electronic support documentation	Example: Supports	Help centre evaluated against WCAG 2.2 AA
602.4	Alternate formats for non-electronic support documentation	Example: Not applicable	No printed documentation
603.2	Information on accessibility and compatibility features	Example: Supports
603.3	Accommodation of communication needs	Example: Supports	Support by text chat, e-mail and relay calls

9. Known issues and remediation plan

ID	Issue	Criteria and clauses	Severity	Workaround	Target release and date	Status
ACR-ISS-001 (Example)	Ticket board cards can be moved only by dragging	WCAG 2.1.1, 2.5.7; EN 4.2.7; 508 302.7	High	Change status in ticket detail form	5.3, YYYY-MM-DD	Planned
ACR-ISS-002 (Example)	Assignee picker lacks expanded state and selected option	WCAG 4.1.2; EN 4.2.1; 508 302.1	High	Plain e-mail field under "Advanced"	5.3, YYYY-MM-DD	In progress
ACR-ISS-003 (Example)	Ticket list sort control announced as "button" without its state	WCAG 4.1.2	Medium	None needed	5.2.1	Fixed in 5.2.1
ACR-ISS-004 (Example)	Report charts have no text alternative or data table	WCAG 1.1.1; EN 4.2.1; 508 302.1	Medium	CSV download of the same data	5.3, YYYY-MM-DD	Planned
ACR-ISS-005 (Example)	Tables lose header markup in web reports and PDF export	WCAG 1.3.1; EN 5.4, 10.1	Medium	CSV download	5.4, YYYY-MM-DD	Planned
ACR-ISS-006 (Example)	Placeholder text contrast 3.2:1	WCAG 1.4.3; EN 4.2.2; 508 302.2	Low	Field labels are visible and meet contrast	5.2.2	In progress
ACR-ISS-007 (Example)	No visible focus on editor toolbar buttons	WCAG 2.4.7	Medium	Keyboard shortcuts listed in help	5.2.2	In progress
ACR-ISS-008 (Example)	Small pagination targets	WCAG 2.5.8; EN 4.2.7	Low	"Show 100 per page" setting	5.3, YYYY-MM-DD	Planned
ACR-ISS-009 (Example)	Editor cannot mark table header cells	EN 5.10; 508 504	Medium	Use lists instead of tables	5.4, YYYY-MM-DD	Planned
[ACR-ISS-nnn]	[Issue]	[References]	[Severity]	[Workaround]	[Release, date]	[Status]

ACR-ISS-003 is fixed in 5.2.1 and no longer affects the results; it is kept here so readers of version 1.0 of this report can trace the change.

10. Publication, maintenance and disclaimer

10.1 Publication and updates

Published at: [URL of the accessibility page, linked from the product page].
Machine-readable copy: [Optional: OpenACR file produced with the GSA ACR Editor, link].
Update trigger: every release that changes the user interface, every change of reported standard version, and at least every [12] months.
Related public statement: if the product is a public sector website or an EU service, the accessibility statement (legal-lite/accessibility-statement, where available in this library) should use the same results.

10.2 Feedback and barriers

Users can report accessibility barriers at [contact]. We acknowledge reports within [5] working days and record them in [tracker] with a reference that is shared with the reporter.

10.3 Disclaimer

This report describes [product and version] as evaluated on the dates in the document control table, using the methods in section 4. It is not a certification by any authority. Customer-created content, configurations and third-party integrations outside the scope in section 2 may change the results. Legal duties depend on the buyer, the use and the jurisdiction; this report does not give legal advice.

11. Glossary and references

11.1 Glossary

Term	Meaning in this document
ACR	Accessibility conformance report: a supplier's statement of how a product meets named accessibility standards
Assistive technology	Software or hardware people use to access ICT, for example screen readers, magnifiers, switches and voice control
Success criterion	A testable WCAG requirement, identified by number and short name
Self-scoping clause	An EN 301 549 requirement that applies only when its stated condition is true
Functional performance	EN 301 549 clause 4 and Section 508 chapter 3: whether people with different abilities can use the product, beyond individual technical checks
Presumption of conformity	Legal effect, under EU product law, of meeting a harmonised standard cited in the Official Journal
VPAT	Voluntary Product Accessibility Template, a report form published by ITI; a registered service mark of ITI

11.2 References

W3C, Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation: https://www.w3.org/TR/WCAG22/
W3C, WCAG Evaluation Methodology (WCAG-EM) 2.0, W3C Group Note: https://www.w3.org/TR/wcag-em-2/
ISO/IEC 40500:2025 (WCAG 2.2 as an International Standard): https://www.iso.org/standard/91029.html
ETSI, CEN and CENELEC, EN 301 549 V4.1.1 (2026-09), free download: https://www.etsi.org/deliver/etsi_en/301500_301599/301549/04.01.01_60/en_301549v040101p.pdf
ETSI, CEN and CENELEC, EN 301 549 V3.2.1 (2021-03), free download: https://www.etsi.org/deliver/etsi_en/301500_301599/301549/03.02.01_60/en_301549v030201p.pdf
National Disability Authority (Ireland), publication and Official Journal citation status of V4.1.1: https://nda.ie/news/en301549-published
US Access Board, Revised Section 508 Standards and Section 255 Guidelines: https://www.access-board.gov/ict/
Section508.gov (GSA), guidance on accessibility conformance reports: https://www.section508.gov/sell/acr/
ITI, VPAT (current edition and terms of use): https://www.itic.org/policy/accessibility/vpat
Directive (EU) 2019/882: https://eur-lex.europa.eu/eli/dir/2019/882/oj/eng
Directive (EU) 2016/2102: https://eur-lex.europa.eu/eli/dir/2016/2102/oj/eng
GOV.UK, accessibility requirements for public sector bodies: https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-websites-and-apps

Related templates: Accessibility Evaluation Report (quality/accessibility-audit) for the evidence behind this report, Accessibility Checklist (design/accessibility-checklist) for design reviews, Bug Report (dev/bug-report) for the issues in section 9, and Release Notes (dev/release-notes) to announce fixes.

Standard and licence note

Based on WCAG 2.2 (W3C Recommendation, also ISO/IEC 40500:2025) for success criterion numbers, short names and levels, on EN 301 549 V4.1.1 (2026-09) for clause numbers and short clause headings, and on the Revised Section 508 Standards (36 CFR part 1194, final rule of 18 January 2017) for section numbers and headings. W3C documents are cited under the W3C Document License; no normative text from WCAG, EN 301 549 or the Section 508 Standards is reproduced, so read the official texts for the requirements. Official text: W3C and ETSI (free downloads) and the US Access Board, at the links in section 11.2. The layout and conformance term definitions are original and do not reproduce the ITI VPAT form; VPAT is a registered service mark of ITI and is named for identification only. Legal facts are dated October 2026; check the current official text and a qualified professional before relying on them. This report format is not legal advice. Template licence: MIT.

Modèles associés

Tests & Qualité