This document provides guidance for customers on Web Content Accessibility Guidelines (WCAG) compliance for the Asset Bank cloud hosted application.

We do not guarantee full WCAG 1.0 ‘AA’ compliance as standard due to the rate at which we develop and release new features and code.

WCAG Standards break down into the following four areas:

1 - Perceivable

Information and user interface components must be presentable to users in ways they can perceive. This means that users must be able to perceive the information being presented by at least one of their senses.

How is this met within Asset Bank?.....

When developing new features we aim for all content to be consumed in a manner that is easy for the user. We try to take into consideration things such as colour contrast, editable alternate text and correct semantic markup.

Asset Bank has comprehensive metadata capabilities and as such, each asset should be identifiable to screen readers. Given the nature of core DAM features ( upload, search, browse, storage of imagery and video) it is not our responsibility to provide text based equivalents for the hosted multimedia content as required for screen readers. We cannot guarantee compliance for content uploaded Asset Bank users.

Due to the highly configurable nature of Asset Bank we are unable to guarantee compliance against any standards once certain changes to the UI have been made e.g. branding that causes colour contrast issues.

2 - Operable

User interface components and navigation must be operable. This means that users must be able to operate the interface (the interface cannot require interaction that a user cannot perform).

How is this met within Asset Bank?

The Asset Bank user interface is under constant optimisation and we make every effort to ensure accessibility is included in our software. When applicable we look for alternative ways for users to perform actions such as using keyboard commands to carry out simple tasks. We cannot guarantee alternative operational methods for all actions within Asset Bank’s interface, due to the complex nature of some of the actions within the system.

3 - Understandable

Information and the operation of user interface must be understandable. This means that users must be able to understand the information as well as the operation of the user interface (the content or operation cannot be beyond their understanding).

How is this met within Asset Bank?

When writing on screen instructions or information within Asset Bank we aim to use clear and simple language for users to understand easily.  The majority of text elements within Asset Bank can be edited by admin users and can also be translated into different languages. Due to the editable nature of most text content we cannot ensure that all text is easily understood by users viewing it.

When developing new features we aim to keep elements as consistent as possible to existing features within the interface. This helps keep key signifiers for actions uniform across the various pages and states within the system.

4 - Robust

Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies. This means that users must be able to access the content as technologies advance (as technologies and user agents evolve, the content should remain accessible).

How is this met within Asset Bank?

As part of our version release process Asset Bank is checked against industry standard testing tools to ensure consistent functionality at each release. As part of the release process we also test new features against a set list of browsers and devices to ensure they are functional with each.

If accessibility issues are reported by Asset Bank customers we aim to rectify them as soon as we can if possible. If an issue has been identified it will enter our established Agile prioritisation and development process.

Future Plans

WCAG 1.0 has been superseded by WCAG 2.1, which Asset Bank has not been assessed against. The first steps of any future accessibility work in Asset Bank would be:

• Assess Asset Bank compliance against WCAG 2.1 (http://www.w3.org/TR/WCAG/)
• Compile a list of the changes necessary for AA compliance.
  

If you have any questions or concerns about accessibility, please get in touch with us.