Check out Part One: Accessibility of PDFs and other downloadable documents Why PDFs are not always a suitable solution There are many reasons, especially with the advent of social media, why PDFs are not a suitable solution for releasing content. It is important, as an organisation, to support your end users by providing them content
Blog Archive
Part One: Accessibility of PDFs and other downloadable documents
The history of the accessibility of PDF (in Australia) In the late 2000s, the Australian Government conducted an enquiry into the accessibility of PDFs by: Requesting public comment Testing PDFs with blind and low vision users Testing PDFs against WCAG2 Talking to assistive technology manufactures Talking to Adobe At that point, PDFs were defined as
All WCAG2.1 Additions Blog Posts
Recently we ran a presentation on WCAG2.1 and WCAG2.2 additions to WCAG2. Since then we have been publishing these additions – one success criterion a day. Here is a list of the WCAG2.1 success criteria blog posts. Level A Success Criterion 2.1.4: Character Key Shortcuts Success Criterion 2.5.1: Pointer Gestures Success Criterion 2.5.2: Pointer Cancellation Success
WCAG2.1 Addition – Success Criterion 4.1.3: Status Messages (Level AA)
Status messages should be programmatically determinable through appropriate roles or properties, allowing assistive technologies to present the information to users without altering their current focus.
WCAG2.1 Addition – Success Criterion 1.4.13: Content on Hover and Focus (Level AA)
When additional content becomes visible upon receiving pointer hover or keyboard focus (and subsequently becomes hidden when these triggers are removed) it should be dismissible in a manner that allows users to close the content without needing to move the pointer or re-focus. This applies unless the additional content communicates an input error (that has then been addressed) or does not obscure or replace other content.
WCAG2.1 Addition – Success Criterion 1.4.12: Text Spacing (Level AA)
The primary goal of this success criterion is to allow users to adjust text spacing to improve readability. This approach aims to improve accessibility for users with cognitive disabilities. It does not require all content to meet these exact spacing specifications; rather, it requires that the website remains responsive when users customize their preferred text settings.
WCAG2.1 Addition – Success Criterion 1.4.11: Non-Text Contrast (Level AA)
This requirement applies to user interface components and their states, except for inactive components or when the appearance is determined by the user agent and not modified by the content creator. These user interface components are required to meet colour contrast requirements, except when a specific graphic presentation is essential to convey the information.
WCAG2.1 Addition – Success Criterion 1.4.10: Reflow (Level AA)
The purpose of this standard is to ensure that content remains readable and accessible on mobile devices. In simpler terms, it is about making sure your website is responsive.
WCAG2.1 Addition – Success Criterion 1.3.5: Identify Input Purpose (Level AA)
The purpose of each input field is to clearly define its intended function. Collecting user information can be automated when the input field’s label correctly identifies it, allowing the computer to input previously agreed content. For example, if a field is coded as a First name, then a system should be able to automatically fill in the user’s first name.
WCAG2.1 Addition – Success Criterion 1.3.4: Orientation (Level AA)
Mobile content should be usable in any orientation. In some cases, the mobile device can be affixed, set to a specific orientation and cannot be rotated by the user.