Module 6, Accessibility auditing and creating an accessibility statement

Module 6

• In the accessibility audit process, the accessibility of the service is assessed as a whole and more broadly than individual components or usage paths.
• The auditing is based on legally prescribed requirements. The tools used include the WCAG (Web Content Accessibility Guidelines) criteria.
• An audit carried out in accordance with the Accessibility Model will produce an up-to-date accessibility statement required by law.

The law obligates Helsinki to produce accessible digital services

Finnish law features the Act on the Provision of Digital Services (Ministry of Finance, 1 April 2019), which is based on the EU Directive on accessibility. The Act obligates authorities, such as the City of Helsinki, to make all publicly available digital services (websites, mobile applications) accessible. The Act defines accessibility as criteria for technical and visual implementation that the service must meet; the criteria are in turn based on the international Web Content Accessibility Guidelines (WCAG).

• Act on the Provision of Digital Services (in Finnish)
• WCAG 2.1

The law is based on the WCAG 2.1 criteria, but a new version of the guidelines has been published. The new WCAG 2.2 guidelines are recommended. The Regional State Administrative Agency estimates that WCAG 2.2 will become part of the Digital Services Act in 2024.

• WCAG 2.2

Web Content Accessibility Guidelines

The WCAG standard sets a series of criteria that are used to assess the accessibility of a service. The criteria are concrete, primarily consisting of requirements related to technical and visual implementation placed at the A, AA or AAA level in the standard. The law stipulates that public-sector services must meet the AA level criteria of the WCAG, with the exception of AA criterion 1.2.4, “Captions (Live)”.

The law also contains some requirements outside the WCAG, such as the requirement that the service must be secure and efficient. However, in practice, the accessibility of services produced by the City of Helsinki is tested based on the WCAG standard, as the legally prescribed accessibility statement is also based on the fulfilment of the WCAG criteria.

Accessibility auditing and accessibility statement

Every service published by the City of Helsinki must include an accessibility statement as required by law. The statement is public and is made available to users of the service. The statement shall describe the accessibility status of the service, including any deficiencies and discrepancies, and information on any plans for remedial action. It also provides a channel for users to provide feedback on the accessibility of the service. More detailed information about the legally prescribed contents of the statement can be found on a website administrated by the responsible authority, the Regional State Administrative Agency, or AVI for short (www.webaccessibility.fi).

In Helsinki’s Accessibility Model, ‘accessibility auditing’ refers to testing with the purpose of establishing and reporting how well the service meets the requirements of the WCAG standard. The nature of the audit must be such that it can be used as the basis for creating an accessibility statement regarding the service. The contents of the auditing report are discussed in greater detail later in this document.

If the audit is ordered from an external supplier, the order must specify who will create the accessibility statement. The Accessibility Model recommends that the auditor work with the service owner to produce the statement. The service owner’s knowledge of the service’s background, limitations, and future development plans will be valuable in creating the statement.

The supplier must be familiar with the methods used. They can also carry out the audit on their own if they have persons well acquainted with the WCAG and aid devices at their disposal.

Link to the Papunet checklist (in Finnish)

Ordering an accessibility audit

The supplier of the accessibility audit will be responsible for selecting the tools and methods used in the testing, as well as their suitability for WCAG compliance testing. The client is not required to be able to define the expert roles of the testing process unless they specifically want to do so.

Therefore, the supplier will be responsible for gathering all necessary information to ensure a thorough service testing process. This includes details such as which sections of the service require logging in but are still accessible to the public, and whether documents on the website, such as PDF files, are included in the audit or covered by another testing process.

More detailed information on what document and media contents and organisational intranet systems are subject to accessibility legislation can be found on the AVI website (www.webaccessibility.fi). More detailed information was also added to the instructions of the Accessibility Model in March 2021.

Reporting the accessibility testing results

As a result of the accessibility audit, the client will be provided with a report detailing any elements of the service that do not meet the requirements of the WCAG criteria.

There is no need to specify every individual WCAG breach if the breach is a repetition of a previously reported occurrence. In other words, having the report point out the elements of the service in which the WCAG breach is repeated will suffice. For example, a shortcoming detected can concern an element that is always repeated in a certain page template, whereby there will be no need to list every individual page on which the element is featured. The information that the issue is repeated in the service wherever the element in question is used will suffice.

As regards WCAG breaches, at least the following information marked as required must be reported. Reporting any information marked as recommendations is optional.

• Requirement: Where the breach occurs in the service. Recommendation: A screenshot that illustrates the phenomenon in the service is attached to the report.
• Requirement: Which WCAG criterion or criteria the shortcoming detected is related to.
• Requirement: The WCAG breach is categorised in accordance with its effectiveness. The gauge is how significant the effect of the accessibility issue is on the users of the service. The purpose of this categorisation is to help the owner of the service prioritise potential remedying and further development work in accordance with how the actual accessibility of the service can be improved the most efficiently. The categories are ‘critical’, ‘significant’ and ‘minor’.
  • Critical accessibility shortcoming: The program may prevent some of the users of the service from carrying out the functions of the service altogether. For example, if the language menu in the banner section of the page cannot be opened when browsing with a keyboard, the shortcoming (WCAG 2.1.1) is critical.
  • Significant accessibility shortcoming: The issue reduces the usability of the service particularly for special groups, but not necessarily completely. For example, if the service issues a notification on the page stating that the user has an unread message and the notification is not conveyed to assistive technologies as a live, status or alert notification but can still be found on the page (WCAG 4.1.3), the shortcoming is significant but not critical.
  • Minor accessibility shortcoming: The issue is a breach of the WCAG criteria and thus subject to the Act on the Provision of Digital Services, but its impact on the usability of the service is minor. For example, if the headings used on the website need specification or clarification, the issue may be a breach of WCAG criterion 2.4.6 the impact of which is quite minor.

• Requirement: The report must provide a verbal account of how the shortcoming reported is a breach of the WCAG. In practice, the reader must be able to understand from the account how the issue occurs and why the occurrence does not comply with the assigned criterion. As such, merely listing or tabulating WCAG breaches (criterion met / not met) is not enough.
• Recommendation: The report should also suggest a remedy for every accessibility shortcoming detected. From the client’s perspective, such remedying suggestions and instructions can be extremely useful, especially if the client does not yet have sufficient accessibility expertise to be provided to the developers.
• Recommendation: The assignment includes reviewing the report together with the client and the supplier of the testing. At this report workshop, the client will have an opportunity to ask about and discuss the observations documented and aspects such as the most suitable remedying method for each situation.

Original version: Tero Pesonen
Created: 4 March 2021