Skip to content

About this Site

The guidelines for each type of web content cover three areas, including

  • How to make web content (there is a lot of accessibility you can add to any content before you put it in a webpage)
  • Making the purpose of the web content clear
  • Operating the web content in a webpage

How WCAG 2.0 has been used in this site

WCAG 2.0 is organised according to its Success Criteria and conformance levels. The techniques for complying with WCAG 2.0 are grouped under different technologies, or as general techniques, rather than different content types or the conformance levels. This makes WCAG 2.0 very large, complex and difficult to interpret and apply.

This website seeks to make WCAG 2.0 easier to apply by web authors, with sections for each type of web author at the university and for different types of web content. This website seeks to create a set of practices and techniques that help people with their work.

Not all available techniques have been used, so if you need to do something special in a site, please contact Web Services or refer to WCAG 2.0 directly. Examples of the simplest and clearest techniques have been chosen to help web editors apply this information to their sites.

If a WCAG 2.0 technique applies to more that one Success Criterion, such as one at single A and another at triple A, that technique has been included at the lowest (most important) conformance level.


There is also a strong focus on usability in this site. Some techniques that do not represent good usability and do not conform to the UTAS Web Publishing Guidelines, have not been used. The Guidelines were updated from WCAG 1.0, and some techniques represent a weakening of accessibility standards under WCAG 2.0. These techniques are listed below.

Techniques that are not recommended

G53: Identifying the purpose of a link using link text combined with the text of the enclosing sentence

The example given in this technique suggests that the link text 'click here' is acceptable if preceded by relevant text. This is not recommended practice at UTAS. Although the page suggests that this is fine for people using screen readers if they are reading sentence by sentence, it does not help people using screen readers to browse the page as a list of links. If there is more than one 'click here' link in a page, people will not be able to tell the difference between them from the link text (this does not mean you can have one such link).

Link text should make sense when read out of context. The use of 'click here', or 'read more' is considered poor accessibility and bad usability and is therefore not supported practice in the UTAS Web Publishing Guidelines. It was certainly not recommended in WCAG 1.0. It is interesting that the other example on the page is accompanied by a note that suggests it is not good practice.

H45: Using longdesc

Used to be a good way of including more information about images by adding a link with the longdesc attribute, but longdesc is not well supported by major browsers.

It is better to add a visible link to a longer description. That way, everyone can use it.