Barrierefreiheitserklärung

Measures to support accessibility

The PDF/UA Foundation takes the following measures to ensure accessibility of within the organization:

• Include accessibility as part of our mission statement.
• Embed accessibility throughout our internal policies.
• Integrate accessibility into our procurement practices.
• Appoint an accessibility officer and/or ombudsperson.
• Provide continual accessibility training for our staff.
• Assign clear accessibility goals and responsibilities.
• Employ formal accessibility quality assurance methods.

Conformance status

The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. The PDF/UA Foundation is partially conformant with WCAG 2.1 Level AA. Partially conformant means some parts of the content may not fully comply with the accessibility standard.

Additional accessibility considerations

Images of text are only used for decorative purposes.

Formal approval of this accessibility statement

This Accessibility Statement is approved by:
PDF/UA Foundation
Mikkel Ándre Jensen-Maar
Webmaster

Assessment approach

The PDF/UA Foundation assessed the accessibility of its website by the following approaches:

• Self-evaluation

How is the site evaluated?

In July 2021, internal web accessibility specialist consultants made a full accessibility audit of the site based on the WCAG 2.1 standard. Key elements are mainly assessed manually.

Limitations and alternatives

Despite our best efforts to ensure accessibility of the PDF/UA Foundation, there may be some limitations. Below is a description of known limitations along with potential solutions. Please contact us if you observe an issue not listed below.

Known limitations for the PDF/UA Foundation:

1. Adjust the cookie and tracking settings: When a keyboard or screen reader user opens the cookie dialogue window from a link to adjust the cookie and tracking settings, the keyboard focus is not moved to the cookie module. The focus in also not restricted to the elements in the dialogue window because the current module was not built for this feature. A new cookie module is in development. When adjusting cookie and tracking settings from the “Privacy Policy” page, activate the link “Adjust the cookie and tracking settings” found under the level 3 heading by the same name. Activate the link (no feedback is given) and tab through all the interactive elements on the website and browser. After the address bar in the browser gets focus, tab again and the link “Privacy Policy” in the cookie module will get into focus. From here, it is possible to navigate in the module and adjust cookie and tracking settings.
2. The cookie module does feature correct semantic tagging: The cookie module is a non-modal dialogue (dialogue windows that don’t disable the main content when activated) because accessible dialogues were not included in the CMS. A new cookie module is in development. When visiting the page for the first time, the cookie module will be the first element presented for a screen reader and the dialogue window is closed by activating the “Save” button.
3. No global search, index, or sitemap: There is no global search, global index, or sitemap for users who receive their information through these functions because no sitemap has been implemented yet. A sitemap is in development and will be added soon. All pages can be navigated to through the menu and every page has links to any subpages.
4. No relationship between button and visible labels: There are toggle buttons in the cookie module with a semantically and visible label. The label is not correctly associated with a form control because of limitations in the CMS. A new cookie module is in development. Users of assistive technology should be aware that the toggle buttons will announce their status twice.
5. Insufficient error messages: When inserting an incorrect email in a validated field in a form, the description of the error is insufficient. An error message should help the user to correct the error, but this is currently not possible in the CMS. A review of all error messages is planned. Contact us by email at contact (at) pdfua.foundation if the forms do not work.

Technical specifications

Accessibility of the PDF/UA Foundation relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:

• HTML
• WAI-ARIA
• CSS
• JavaScript

These technologies are relied upon for conformance with the accessibility standards used.

Compatibility with browsers and assistive technology

The PDF/UA Foundation is designed to be compatible with the following assistive technologies:

• Firefox 84 with NVDA on Windows 10
• Firefox 84 with JAWS on Windows 10
• Chrome 88 with NVDA on Windows 10
• Chrome 88 with JAWS on Windows 10
• Safari 14 with VoiceOver on IOS
• Opera 73 with NVDA on Windows 10
• Opera 73 with JAWS on Windows 10
• Edge 88 with NVDA on Windows 10
• Edge 88 with JAWS on Windows 10
• Internet Explorer 11 with NVDA on Windows 10
• Internet Explorer 11 with JAWS on Windows 10
• iOS ≤ 13 14
• Android ≤ 11

Further combinations will be tested in the future.

The PDF/UA Foundation is not compatible with:

• Safari with VoiceOver reads the content in tool tips regardless of if they are expanded or not.

Feedback

We welcome your feedback on the accessibility of the PDF/UA Foundation. Please let us know if you encounter accessibility barriers on the PDF/UA Foundation website:

• Email: contact (at) pdfua.foundation
• Contact form

Visitor Address:
PDF/UA Foundation
2780 Coventry Road
Oakville, Ont., L6H 6R, Canada

We try to respond to feedback within one business day, or as soon as possible.

Formal complaints

If you find accessibility issues not outlined in this document, please use the contact form below, under det heading “Contact form”, to notify the technical manager.