Requirements - Web Content
Download these requirements as an Excel spreadsheet
-
Accessibility for all users
Description
Ensure that web services can be accessed by all users, including those with disabilities.
Rationale
Section 24 of the Disability Discrimination Act makes it unlawful to discriminate, when providing goods and service against another person on the basis of the person's disability.
Priority
Mandatory
-
Comply with WCAG 2.1 Level AA
Description
Ensure that web accessible elements of the solution comply with the Web Content Accessibility Guidelines set out in WCAG 2.1 Level AA.
Rationale
The University has endorsed WCAG 2.1 Level AA as its standard in relation to web content.
Priority
Mandatory
-
Text alternatives
Description
Provide text alternatives for any non-text content such as images.
Rationale
Allows non-text content to interpreted by assistive technologies, such as Braille readers and speech synthesizers.
Priority
Mandatory
-
Labels for form fields
Description
Add labels to form fields.
Rationale
Labels need to be explicitly associated with form input fields in order for them to be read by assistive technologies, such as Braille readers and screen readers.
Priority
Mandatory
-
Video captions
Description
Provide alternatives for time-based media such as video and audio.
Rationale
Users with visual impairments and deafness require audio descriptions, captions and/or transcripts to help them access content contained in video and audio.
Priority
Mandatory
-
Headings and lists
Description
Use structural markup such as headings (e.g. <h1> - <h6>) and lists (e.g. <ul> <ol>) to organise content.
Rationale
Most screen reader users navigate content using structural mark-up such as heading tags and lists rather than in a linear fashion. Correct structural markup also allows content to be accessed by a wide variety of platforms, including mobile and handheld devices.
Priority
Mandatory
-
Contrast
Description
Provide a contrast ratio of 4.5:1 between foreground text and the background.
Rationale
All users, particularly those with vision impairments, have trouble reading text if the contrast is insufficient.
Priority
Mandatory
-
Data table headings
Description
Add column and row headings (e.g. <th>) to data tables.
Rationale
Screen reader users have difficulty navigating data tables if columns and rows are not given headings.
Priority
Mandatory
-
Increased text size
Description
Ensure that all pages are readable and functional when text size is increased by up to 200%.
Rationale
Users with vision impairments often have to increase the text size in order to be able to read content.
Priority
Mandatory
-
Keyboard
Description
Make all functionality available via the keyboard.
Rationale
40% of people with a motor impairment have difficulty using their hands. Many have trouble using mice because of limited hand-eye co-ordination, trouble finding a pointer or hand tremors.
Priority
Mandatory
-
Sufficient time
Description
Provide users with enough time to read and use content.
Rationale
Many users with disabilities take longer to find things, read things and physically respond to events.
Priority
Mandatory
-
Avoid seizures
Description
Do not design content in a way that is known to cause seizures.
Rationale
Users with photosensitive seizure disorders can have a seizure triggered by content that flashes at certain frequencies for more than a few flashes.
Priority
Mandatory
-
Consistent navigation
Description
Help users navigate, find content and determine where they are via consistent navigation, headings and links.
Rationale
Consistent navigation makes it easier for all users to keep track of their location, particularly those with memory or reading problems.
Priority
Mandatory
-
Language identification
Description
Identify the human language of the page (e.g. English).
Rationale
Both assistive technologies and conventional user agents can render text more accurately when the language of the web page is identified.
Priority
Mandatory
-
Consistent content order
Description
Present content in a consistent order from page to page and make the behaviour of interactive components predictable.
Rationale
The synthetic speech of screen readers makes it difficult for users to understand spatial relationships and users with cognitive limitations become confused if components appear in different places on different pages.
Priority
Mandatory
-
Labels, cues and instructions
Description
Provide sufficient labels, cues and instructions for users when completing forms.
Rationale
Everyone makes mistakes. However some people have more difficulty creating error-free input and detecting that they have made an error.
Priority
Mandatory
-
Meaningful link titles
Description
Avoid 'click here' links.
Rationale
Both search engines and screen readers commonly navigate pages by looking at link text.
Priority
Mandatory
-
Page titles
Description
Add meaningful page titles.
Rationale
Users of voice synthesizers and Braille readers rely on page titles to identify pages when they have multiple pages open.
Priority
Mandatory
-
Javascript
Description
Ensure that changes to the page via Javascript are reported to adaptive technologies.
Rationale
Changes to page layout caused via Javascript are often are not reported to assistive technologies
Priority
Mandatory