Current staff

Accessibility author checklist

  1. Home
  2. Information and services
  3. Information technology
  4. Web and intranet sites
  5. Web writing guide
  6. Edit website content
  7. Web accessibility

This guide provides a practical checklist for developing accessible website content. 

Content

  • Aim for Grade 9 level readability (or lower).
  • Use plain language your audience will understand.
  • Don’t use jargon or puns, metaphors or other non-literal text.
Top of page

Formatting

  • Use sentence case.
  • Use sans serif fonts. The block-like appearance is more readable.
  • Don’t use centred or justified text. Left aligned only.
  • Avoid italics.
  • Don’t underline text (unless default link text styling).
Top of page

Headings

  • Headings should be short and simple but also meaningful.
  • Use one H1 per page.
  • Use H2 for the main subheadings on a page.
  • Use subsequent subheadings (H3, H4, etc.) in descending order (e.g. H3 is used to organise content under H2).
  • Don't skip a heading level (e.g.  jump from H2 to H4).
  • Don’t use headings for style reasons (e.g. to make text bigger).
  • Don’t use bold text or full capitals instead of a heading.
Top of page

Images

  • Use alt text to explain what the image contains.
  • Where possible, avoid infographics or process flows. If you must include an infographic, include text alternatives, such as a numbered list to show process order. Include alt text on the infographic describing where the text alternative is (e.g. Text description below, and either the description or a link to a text description immediately below the infographic).
  • Don’t use images as the only way to convey information.
  • Don’t use images of text.
Top of page

Links and buttons

  • Use meaningful link text that describes what is being linked to (no ‘click here’ or ‘read more’).
  • Buttons should only be used for the key actions on a page. These shouldn’t be overused. Make sure the user knows what will happen when they click the button (e.g. ‘log in’, ‘apply’).
  • Don’t use a button if a regular link will do.
  • Links should open in the same window.
  • If linking to a document, include the document type and file size in brackets (e.g. Study at UQ: Program page content sources (PDF, 5.3 MB)).
    • New Drupal will do this automatically when you link to a document. When working in Drupal 7 you will need to tick the ‘Display file type and size in link’ box.
  • Link text should be blue.
Top of page

Tables

  • Tables should be simple.
  • Use the caption element to give the table an informative title.
  • Use headers that apply to the whole column or row.
  • Don’t put tables within tables.
  • Don’t use tables for layout reasons (e.g. to make text columns).
  • Don’t merge cells.
Top of page

Documents

  • Use headings and follow hierarchy rules.
  • Set the reading order (column A, then column B, then break-out box, etc).
  • Include a table of contents for longer documents. This should include jump links.
  • Use metadata to provide information on the contents of the document. To add metadata to a PDF:
    • open ‘document properties’
    • add an appropriate title (use the H1), author (The University of Queensland) and subject (brief description of the document) 
    • click ‘ok’ and save the document. 
Top of page