Azorus accessibility statement

Azorus has made assessments based on the WCAG 2:1 to make the public side of our CRM application fully accessible as provided out of the box. Client branding, content, or display changes could alter end user experience.

An area of note is that the public side of Azorus includes the requirements to support screen readers, where values are set by the clients themselves. If a client wishes to extend screen reading support software from their core website to the Azorus product, this can be implemented.

Clients are able to provide content through email, print, and have the option to setup support calls and tickets. This will be up to clients to decide what level of support they will offer.

The Azorus admin panel and wiki are not currently covered by WCAG 2:1 and currently have been assessed as disproportion.

Accessibility issues should be raised through their account managers and accessibility items will be assessed in lines with WCAG 2:1 AA standard.

Azorus is committed to providing a website that is accessible to the widest possible audience, regardless of ability. We are actively working to increase the accessibility and usability of our website and in doing so adhere to many of the available standards and guidelines.

Expected use

We want as many people as possible to be able to use this website. For example, that means you should be able to:

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

We know some parts of the application are not fully accessible where client branding has been set:

Some extensions may have difficulty changing the fonts from what the clients have chosen.
Client branding choices may not give enough contrast between colours
Client branding choices may not have large enough font
Where clients have not set historic alt text on images

What a user should do if they cannot access parts of the application Reporting issues Enforcement procedure

Enforcement procedure

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).

Contacting us by phone or visiting us in person Content that’s not within the scope of the accessibility regulations

Content that’s not within the scope of the accessibility regulations

None public facing parts of the applications are not cored within the scope of the new

regulations. They have been assessed however, and added to our Disproportionate burden documentation with notes for any future developments in that area.

Areas covered by this include:

The Azorus Wiki
Azorus YouTube Training videos
The Azorus admin interface

How we tested this website

We created an assessment based on the articles here: https://alphagov.github.io/wcag-primer/checklist.html#perceivable

We then ran tested for key public web pages such as Forms, Event Booking Process, and the Preference centre.

We ran through Perceivable, Operable, Understandable, Robust tests, including using these external tools:

Checks: accessibility, usability, errors, compability, search: https://www.powermapper.com/products/sortsite/ads/acc-wcag-testing/

Checks: Finds buttons, images, popups, links with no alt text: https://www.webaccessibility.com/test

This included navigation via keyboard, testing audio descriptions, font size differences.

A lot of it by default is fine, but of course, if a client changes their branding that could be affect items such as readability, or their content changing context.

Releases related to accessibility

Items we identified for the public side were fixed in a release on the 22nd of August:

Release 2019.v05.00

We also created a disproportionate exemption list, but only our internal wiki, YouTube training videos and admin interface have entries there.

Features added related to accessibility in the release 2019v05.00:

ACCESSIBILITY - Captcha: - Captcha audio may now be played by pressing the space bar when focus is on the audio button.

ACCESSIBILITY - Forms: When a form submission fails, the errors at the top of the form now indicate all fields with errors, replacing the "see highlighted fields below" message.

ACCESSIBILITY - Images: A new page has been provided, showing a list of images which do not have their alt text set. It is highly recommended that you go through this list and supply alt text for all images. Typically, alt text is a short, simple description of what is in the image.

ACCESSIBILITY - Forms: Several label elements have been updated to be properly associated with their intended targets, including dropdown fields, Communication Preferences checkboxes, and the captcha.

We've since removed Captcha, and upgraded to Recapture which is better for accessibility as well.

Further updates 2022-2024:

2022 - Updated forms for better error reading by screen readers

2022 - Gave options for where first focus is on a webpage

2022 - Removed link attributes on lists

2022 - replaced jqmobile popups with better ones for keyboard controls

2023 - Form DOB labels

2023 - Accessible auto complete option added

2023 - fixed 400% zoom issue

2023 - updated telephone package to work better for keyboards

2023 - missing aria attributes set for accessibility

2024 - tables containing non-tabular data having a presentation role

What we’re doing to improve accessibility

Azorus is considering detecting accessibility users when booking an event where the end-user can build a timetable. We could then present them with a help dialogue informing them of the opening times of the Events team, so that they can get phone assistance in creating their event booking.

We will continue to listen to client feedback and resolve issues as they are identified.