Requirements - Authoring Tools

  1. Comply with ATAG 2.0

    Description

    Ensure that author content generated by the solution comply with the Authoring Tool Accessibility Guidelines (ATAG).

    Rationale

    The ATAG set out guidelines for ensuring that any web content generated by users is accessible.

    Priority

    Desirable

  2. Accessible automatic content

    Description

    Ensure that automatically specified content is accessible.

    Rationale

    If the system allows users to enter information that will automatically generate web content, then the system should ensure that the content is accessible.

    Priority

    Desirable

  3. Preservation of accessibility information

    Description

    Ensure that accessibility information is preserved.

    Rationale

    If the system allows users to edit content, then the accessibility of the content should be preserved.

    Priority

    Desirable

  4. Accessible content production

    Description

    Ensure accessible content production is possible.

    Rationale

    The system shouldn't restrict the ability of users to create accessible content.

    Priority

    Desirable

  5. Guide authors

    Description

    Guide authors to produce accessible content.

    Rationale

    If the system allows users to style content (e.g. text) then options should prompt them to produce accessible content.

    Priority

    Desirable

  6. Alternate content

    Description

    Assist authors with managing alternative content for non-text content.

    Rationale

    If the system allows users to upload images, it should prompt them to provide alt text.

    Priority

    Desirable

  7. Accessible templates

    Description

    Assist authors with accessible templates.

    Rationale

    If the system allows users to create content using templates, then those templates themselves should be accessible.

    Priority

    Desirable

  8. Accessible pre-authored content

    Description

    Assist authors with accessible pre-authored content.

    Rationale

    If the system allows authors to generate content using code snippets (e.g. a table or list), then those code snippets should be accessible.

    Priority

    Desirable

  9. Automatic accessibility checks

    Description

    Assist authors in checking for accessibility problems.

    Rationale

    If the system should provide a mechanism for authors to allow them to check if their content is accessible.

    Priority

    Desirable

  10. Automatic accessibility corrections

    Description

    Assist authors in repairing accessibility problems.

    Rationale

    The system should provide help content authors to correct accessibility problems.

    Priority

    Desirable

  11. Support accessible content production

    Description

    Ensure the availability of features that support the production of accessible content.

    Rationale

    Accessible content features should be active by default.

    Priority

    Desirable

  12. Documentation

    Description

    Ensure that documentation promotes the production of accessible content.

    Rationale

    The system documentation should help content authors to correct accessibility problems.

    Priority

    Desirable

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