WCAG 2.0 AA Responsibility Breakdown

• Content developer

  • Images

    • Add alt text to images and labels to forms - 1.1.1 Non-text Content
    • Don't use images of text - 1.4.5 Images of Text

  • Audio

    • Add transcripts to audio - 1.2.1 Audio-only and Video Only (Pre-recorded)

  • Video

    • Add captions to videos - 1.2.2 Captions (Pre-recorded)
    • Add a transcript to describe silent content in videos - 1.2.3 Audio Description
    • Add live captions to real-time videos - 1.2.4 Captions (live)
    • Add an audio description of silent content in videos - 1.2.5 Audio Description

  • Text

    • Don't make instructions reliant on size, shape, visual location or sound - 1.3.3 Sensory Characteristics
    • Add a meaningful page title - 2.4.2 Page Titled
    • Avoid 'click here' link text - 2.4.4 Link Purpose (In Context)
    • Add informative headings and form labels - 2.4.6 Headings and labels

• Developer

  • Semantic structure

    • Use heading tags, table headings and lists - 1.3.1 Info and Relationships
    • Make code match the reading and navigation order - 1.3.2 Meaningful Sequence

  • Forms

    • Identify required input formats and clearly identify errors - 3.3.1 Error identification
    • Use labels, fieldsets and legends for forms - 3.3.2 Labels or Instructions
    • Identify input errors - 3.3.3 Error Suggestion
    • Allow users to confirm and reverse changes to data - 3.3.4 Error Prevention (Legal, Financial Data)

  • Code

    • Use the lang attribute to identify the language of the page - 3.1.1 Language of page
    • Identify the language of page content if different to the rest of the page - 3.1.2 Language of Parts
    • Avoid validation errors - 4.1.1 Parsing
    • Use valid markup - 4.1.2 Name, Role, Value

• UX / Interaction designer

  • Audio

    • Allow users to stop, pause or mute audio - 1.4.2 Audio Control

  • Timing

    • Let users turn off or extend time limits - 2.2.1 Timing Adjustable
    • Allow pausing of animations - 2.2.2 Pause, Stop, Hide
    • Avoid flashing page content - 2.3.1 Three flashes or below threshold

  • Navigation

    • Add skip to content links or content groupings - 2.4.1 Bypass Blocks
    • Add a list of related pages, index, sitemap or search - 2.4.5 Multiple Ways

  • Interaction

    • Avoid pop-up windows when elements receive focus - 3.2.1 On Focus
    • Avoid surprise changes when inputing information - 3.2.2 On Input

  • Text

    • Allow Text Resizing - 1.4.4 Resize Text

  • Keyboard

    • Make the navigation order of links and forms logical - 2.4.3 Focus Order
    • Make each page navigable by keyboard alone - 2.1.1 Keyboard
    • Don't trap the keyboard - 2.1.2 No keyboard trap

• Design System / Style Guide / Designer

  • CSS

    • Don't use color alone to distinguish between links and surrounding text - 1.4.1 Use of Color
    • Provide sufficient contrast between text and background colors - 1.4.3 Contrast (Minimum)
    • Give an indication of keyboard focus - 2.4.7 Focus Visible

  • Templates

    • Keep navigation consistent - 3.2.3 Consistent Navigation
    • Identify elements consistently - 3.2.4 Consistent Identification

• Project Manager

  • Planning

    • Assign responsibilities, e.g. agile project: add accessibility tasks to product backlog

  • Monitoring

    • Monitor progress, e.g. agile project: ensure that some accessibility tasks are completed each sprint

• Product Owner / Project Steering Committee

  • Oversight

    • Ensure that accessibility forms part of the non-functional requirements of the project / solution

Contact Us

For assistance or to report accessibility problems please contact:

Andrew Normand
Web Accessibility Lead
Email: anormand@unimelb.edu.au
Phone: +61 3 9035 4867