Care should be taken to test and validate your new web site or application before launching.
The benefits of web accessibility are:
- ability of people with a disability to benefit from your information or service
- compliance with laws and government guidelines
- improved search engine rankings
- a better experience for everyone
Preparing accessible content
A helpful habit to adopt is to apply existing styles e.g. headings to your document rather than changing text size, fonts and colours individually. Most programs such as word processors and web editors work with styles.
Obtaining a template that already has the right styles and has been prepared or enhanced by a colleague who is trained in accessibility, can save a lot of time and produce quality results.
Photos, videos, charts, audio and flash are inaccessible when they are first created. Plan time to address this (instead of avoiding this type of media). Video and audio require transcripts for example.
Here is guidance about making digital media accessible.
Here are some tips to help you get started:
- If content is important, it should be in HTML. Avoid PDFs whenever possible. However if PDFs are unavoidable on your site, then make sure they're tagged - and even then, it's good to have a text alternative as well.
- If an image serves a purpose on your site, you need alt text to describe its purpose. For example, if an infographic shows that 2 out of 10 bank loans are rejected, then the alt text needs to say this.
- If an image is purely decorative then you need to make sure it doesn't have title text PLUS you need to have alt="" within the image tag. This will ensure assistive technology ignores it.
- You can't give physical directions to where content is on a screen - ie avoid saying "click on the icon in the left-hand corner" - since this means little to those using a screen reader
- Don't refer to objects by their shape (ie "click on the rectangular icon")
- Don't rely on colour for navigation or to give meaning
- Use left, center and right alignment for layout, instead of tables. However, if you have to use tables, make sure the content makes sense if read sequentially from left to right toward the bottom - because that's how assistive technology (AT) will read it.
- If you use a table to present data then you need to use TH tags to identify column and row headings. If the table is purely to help with the layout, don't use TH tags - if you do, a screen reader (or other form of AT) will assume it's a data table
- Use CSS to control the layout, style and size of text to keep it visible to screen readers and achieve smooth resizing including on large displays and mobile devices, and for great readability for everyone. Avoid presenting text in the form of images.
When validating pages for WCAG 2.0 AA, the HTML_CodeSniffer is the easiest of the tools available. This tool can quickly identify most issues your website may have. The tool is unable to work on secure pages. Developers should be aware that it can't check pages where the DOM has not been used to display content.
SiteBeam which reviews entire sites, may be available for use within the team. Ask Billy about how to access it.
An important area for accessibility is maintaining colour contrast for users with poor eyesight or colour blindness. Designers can use the Colour Contrast Analyser from Vision Australia.
WebAIM has some other useful tips for designers http://webaim.org/resources/designers/
Web resources for meeting the WCAG 2.0 Accessibility standard
- Understanding WCAG 2.0
- Accessibility checklist
- How to meet WCAG 2.0
- Techniques for WCAG 2.0
- PDF Techniques for WCAG 2.0
- Vision Australia
- Australian Government Web Guide (Accessibility section)
- Practical tips for accessible content
- HTMLCodeSniffer Compliance checker
- AChecker accessibility checker
- Colour Contrast Analyser for webpages
- Macquarie University Accessibility information
This is an interim document while web accessibility tools, training and processes are agreed for a long-term strategy.