Accessibility in standard systems

Requirements for the supplier

In connection with procurement of standard systems, it should be a requirement that suppliers meet WCAG 2.1 level AA. AU IT has prepared standard requirements, which can be included in a specification of requirements. 

Furthermore, it must be ensured that the supplier actually complies with the requirements. This can be done by random checks or by asking the supplier to document that they meet the required standards. External assistance may be used to carry out the checks. 

If the procurement process does not require that the supplier meet WCAG 2.1 level AA, if the supplier refuses to meet this standard for any other reason, or if it becomes disproportionately expensive for AU to ensure compliance by the supplier, then the system owner must assess whether AU can accept that the system in question does not comply with the Danish web content accessibility act.  

AU’s own configuration of the system

It is possible to configure the appearance of a number of systems, including colours and fonts. This can also affect accessibility. There can be issues associated with colours, where there is not enough contrast to make the text easily legible for the visually impaired. Therefore, all system owners should ensure that AU’s configurations do not cause accessibility problems.  

In relation to colours, you should be particularly careful if you use the following AU brand colours: Cyan, yellow, turquoise, green and orange. 

In addition, different versions of grey can cause issues. 

Usually, contrast will not be an issue for dark blue/white and black/white colour combinations. 

Accessibility statement

In addition to ensuring that the system is as compliant as possible, a statement must also be issued. A so-called accessibility statement. The accessibility statement should be published regardless of whether efforts have been made to improve accessibility. If the system owner has assessed that compliance is a disproportionately heavy burden, this must be stated in the accessibility statement.  

The accessibility statement is created by using the Danish Agency for Digitisation's tool: https://digst.dk/digital-service/webtilgaengelighed/lov-om-webtilgaengelighed/was-tool/ and will be located at the following URL after publication: https://www.was.digst.dk/. The title is filled in while preparing the statement. 

A NemID staff signature is required to access the tool. Click the link to order a NemID staff signature: https://medarbejdere.au.dk/administration/it/vejledninger/sikkerhed/medarbejdersignatur/ 

If the system administration does not have the competences to assess the accessibility of the system, it is possible to ask the supplier to document the extent to which they meet WCAG 2.1 level AA. Alternatively, external assistance may be used for the assessment. 

The accessibility statement must be published in the system's footer. And must also be available on the website's URL via www.xyz.dk/was. The URL must redirect to the URL on was.digst.dk/xy. Check www.mitstudie.au.dk for an example. 

The statement must also include an email address that can be used for questions regarding accessibility. We recommend that you use a support address or a shared mailbox, where these questions can be compiled and answered. 

Please note that if new modules are taken into use in a standard system, it may be necessary to update the accessibility statement.