Myths about creating accessible resources
Myth # 1
There is one document type that can be used by everyone, regardless of disability
Although on the surface this statement appears in line with many long held beliefs regarding accessibility of electronic material, it is in fact impossible to create a single document that is accessible to everyone. A Braille document is perfectly accessible to a person who can read Braille and completely inaccessible to a person who cannot.
The notion of creating accessible resources is not that all resources created by academic staff conform to a single standard, but rather that any resources that are developed be accessible to the largest number of users. With a little planning you can ensure your material is perceivable, operable, understandable and robust to the widest possible cohort of students.
The Web Content Accessibility Guidelines (WCAG) version 2.0 defines these four principles of accessibility as:
Perceivable
Information and user interface components must be presentable to users in ways they can perceive. This means that users must be able to perceive the information being presented (it can't be invisible to all of their senses).
Operable
User interface components and navigation must be operable. This means that users must be able to operate the interface (the interface cannot require interaction that a user cannot perform).
Understandable
Information and the operation of user interface must be understandable. This means that users must be able to understand the information as well as the operation of the user interface (the content or operation cannot be beyond their understanding).
Robust
Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies. This means that users must be able to access the content as technologies advance (as technologies and user agents evolve, the content should remain accessible).
Source: Introduction to Understanding WCAG 2.0.
Myth # 2
Creating resources in compliance with a set of guidelines means you are accessible
Guidelines are just that, guidelines. They give guidance on how to do a particular task or set of tasks. Although useful in steering processes in the right direction by encouraging users to meet certain standards, they often focus more on what not to do rather than what you can, and should, do. Guidelines are often ignored once people think they have an understanding of the process, not how what they do has an impact.
The aim of creating inclusive resources is to ensure, as far as practical, that you do not willingly exclude people from accessing content.
Visit Web Accessibility in Mind for more information.
Myth # 3
It takes a lot of time to make materials accessible
It generally takes longer to create inaccessible resources than it does to create accessible ones as the time spent creating visually appealing content often results in additional barriers to accessibility. Add to this the time taken to convert material back into an inclusive format after the fact and your resource has now taken far longer than just the initial creation. Consider also the additional work that will be required to add to this content at a future date.
Creating accessible content is really about unlearning the bad habits we have largely adopted, thinking about your content and how best to communicate it, and taking time to consider the end user and how you think they will be accessing the material. We are all creatures of habit and learning to do new things, and change our habits is no small task, but it can be achieved if you are committed to it. Finding a reason to commit to changing your practice is simple: you will be a better communicator and the skills you gain will make you a more inclusive content developer.
Thinking and planning are the key. Developing more inclusive resources assists everyone, including you.
