This accessibility statement applies to Asset Bank created by Bright. Asset Bank can be viewed by a custom web address that is unique for each of our clients. For example one of our demo instances of Asset Bank has the address https://cast.assetbank-server.com/, your address will vary.
We want as many people as possible to be able to use Asset Bank. For example, that means you should be able to:
- change colours, contrast levels and fonts
- zoom in up to 300% without the text spilling off the screen
- navigate most of the website using just a keyboard
- navigate most of the website using speech recognition software
- listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
We’ve also made the website text as simple as possible to understand. AbilityNet has advice on making your device easier to use if you have a disability.
Bright is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards.
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’). If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).
Measures to support accessibility
Bright takes the following measures to ensure the accessibility of Asset Bank:
- Include accessibility throughout our internal policies.
- Assign clear accessibility targets and responsibilities.
We welcome your feedback on the accessibility of Asset Bank. Please let us know if you encounter accessibility barriers on Asset Bank:
- Phone: +44 (0) 1273 923152
- E-mail: email@example.com
- Visitor address: 9th Floor, Tower Point, 44 North Road, Brighton, East Sussex, BN1 1YR
We try to respond to feedback within two business days.
Technical information about this website’s accessibility
Bright is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Accessibility of Asset Bank relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:
These technologies are relied upon for conformance with the accessibility standards used.
Which areas are tested for compliance?
We aim to be compliant with WCAG 2.1 Level AA in all areas and features within Asset Bank, but due the vast configuration options and levels of customisation sometimes this is not possible. We have identified a set list of key pages we aim to be compliant on, based on user metrics. This current list is what we are testing compliance against and is as follows:
Additional pages will be tested based on the relevance to the WCAG 2.1 guideline in question.
Asset Bank is not compliant with the Web Content Accessibility Guidelines version 2.1 AA standard. The non-compliances and exemptions are listed below.
Non-compliance with the accessibility regulations
- List of issues
WCAG 2.1 AA Failures
- 1.1.1 Non-text Content - Not all system images contain alternate text descriptions and there is no current implementation of customising alternative text on images.
- 1.2.2 Captions (Prerecorded) - No current way of adding captions to video elements. However, admins can create transcripts as an attribute for an asset description.
- 1.2.3 Audio Description or Media Alternative (Prerecorded) - Not possible to add audio descriptions to uploaded assets
- 1.2.4 Captions (Live) - Captions cannot be created nor synchronized with live video
- 1.2.5 Audio Description (Prerecorded) - Not possible to add audio descriptions to uploaded assets
- 1.3.1 Info and Relationships - Some pages can contain custom widgets that do not have appropriate ARIA role values. Incorrect semantic markup on various elements / pages
- 1.3.2 Meaningful Sequence - Some elements have inappropriately ordered HTML markup
- 1.3.3 Sensory Characteristics - Some elements only use colour to indicate information, such as selecting assets are only highlighted green
- 1.3.5 Identify Input Purpose - Not all inputs have associated labels
- 1.4.1 Use of Color - Some elements only use colour to indicate information, such as selecting assets are only highlighted green
- 1.4.3 Contrast (Minimum) - Not all text and images have a passing contrast ratio
- 1.4.4 Resize text - Resizing text can cause loss of information
- 1.4.5 Images of Text - There are some images of text within the system
- 1.4.10 Reflow - Some pages cause horizontal scrollbars to appear when zoomed in above 100%, or the browser width is scaled down
- 1.4.11 Non-text Contrast - Not all text has acceptable contrast ratios
- 1.4.12 Text Spacing - Adjusting the line height and font size can cause the information to be visually lost
- 1.4.13 Content on Hover or Focus - Some content can only be visible on mouse hover and not focus
- 2.1.1 Keyboard - Not all actions or controls can be used with a keyboard alone
- 2.1.2 No Keyboard Trap - Some pages can only be accessed via the mouse
- 2.1.4 Character Key Shortcuts - Not currently possible to turn off or change keyboard shortcuts
- 2.2.1 Timing Adjustable - Some pages contain fixed time limits which cause page refreshes
- 2.2.2 Pause, Stop, Hide - Some pages contain fixed time limits which cause page refreshes which are below 5 seconds in length
- 2.4.1 Bypass Blocks - There is no way to bypass the main header or navigation with when navigating with keyboard only
- 2.4.2 Page Titled - Not all pages contain a title
- 2.4.3 Focus Order - Not all elements are in correct focus order
- 2.4.4 Link Purpose (In Context) - Some links do not have a correct text alternative
- 2.4.5 Multiple Ways - There is no sitemap and sometimes only single paths to certain pages
- 2.4.6 Headings and Labels - Some headings and labels usage is not semantically correct
- 2.5.3 Label in Name - Not all inputs/controls have associated names assigned to them
- 3.1.1 Language of Page - When changing languages using the multi-language feature, the HTML tag does not update to the appropriate language
- 3.1.2 Language of Parts - No programmatic way of determining language changes in page
- 3.2.1 On Focus - Focus can cause some elements or controls to change context or value
- 3.2.2 On Input - Some inputs can cause context changes without prior warning
- 3.2.4 Consistent Identification - Not all components that have the same functionality within some pages are identified consistently
- 3.3.1 Error Identification - When an error occurs, incorrect form inputs are not always highlighted
- 3.3.2 Labels or Instructions - Some inputs or controls have no description
- 4.1.1 Parsing - There can be some elements without proper semantic children. Additionally, there might be instances where multiple id's of the same type exist on a single page
- 4.1.2 Name, Role, Value - Not all custom components have an appropriate role or semantic markup
- 4.1.3 Status Messages - Not all status messages have appropriate markup
Despite our best efforts to ensure accessibility of Asset Bank, there may be some limitations. Below is a description of known limitations, and potential solutions. Please contact us if you observe an issue not listed below. Known limitations for Asset Bank:
- User Generated Content: e.g. Videos may not be captioned or have transcribed content because We are unable to ensure the accessibility of content uploaded by our customers. This responsibility has to be passed on to the administrators of individual Asset Banks.
Plans for addressing accessibility issues
Our development team has prioritised and scheduled work to address the majority of accessibility issues within Asset Bank. At this time we are unable to give an accurate date on when all of these changes will be made. This document will be updated when new Asset Bank versions are released containing changes that address accessibility issues.
Preparation of this accessibility statement
This statement was prepared on 10 August 2020. It was last reviewed on 21 September 2020. Asset Bank was last tested on 21 September 2020.
The test was carried out by our development team. Testing was completed via a manual process using relevant tools such including a screen reader, WAVE (web accessibility evaluation tool) and additional browser extensions.
Further information on our approach to accessibility can be found in our help centre article on Asset Bank and Web Accessibility (WCAG)