OneVu 2.8

In order to comply with the rules around WCAG 2.1 AA needed for September 23rd 2019 for new websites*, we have made changes in this build of OneVu to enhance what we do in terms of accessibility.

It's worth noting that OneVu already had many compliant elements, these changes are to augment the solution further.

The changes made in this release are as follows:

Change 1 - Chronological Tabbing

Previously when one solely used a keyboard to navigate OneVu the first tab would take one to the far right of the nav menu. Then jump to the left of the nav menu and jump from left to right.

In this release these issues have been resolved so that theres a naturally order when tabbing.

Change 2 - Elements not tabbed to

None of these items were even identified as element to be tabbed to:

• the departments shown to a customer on the 'Get Answers Fast' page
• the in progress forms a customer had
• the forms found on form search
• the entire list of forms on browse forms
• the processes a person was tracking / or those completed
• items that were hyperlinks in the header above the navbar i.e. clickable logos

These elements, which were 'divs' (elements of HTML that make up web pages), have been updated to be buttons and are now recognised by the browser when tabbing.

Change 3 - Using appropriate aria-labels and img alt labels

Where appropriate aria-labels  have been added.

To provide an example, Lambeth Council has a hyperlink on its logo within OneVu to take them back to the Lambeth Council home page.

Previously this showed like this:

 <a href="https://www.lambeth.gov.uk/" target="_blank">

<img src="/Content/images/lambethlogo.png"></a>

This now shows like this:

<a href="https://www.lambeth.gov.uk/" rel="noreferrer" aria-label="Go back to Lambeth Council home page" target="_blank"><img alt="Lambeth Council Logo" src="/Content/images/lambethlogo.png"></a>

By having these labels added, it means a user with a screen reader that tabs to the logo is able to be told what this hyperlink will do and what the image relates to. 

Change 4

Similar to the above, it was not possible to use the multiple accounts function because, the table containing details of the accounts linked to your OneVu account, was not able to be interacted with using solely a keyboard. 

To solve this, a button has been added to access any other accounts/cases associated with a given department:

Important

i) It is important to note that within OneVu it is possible to add HTML in FAQs for departments. Consequently, it is valid to state that you should review whether any of this presents an issue from an accessibility stand point. It is also important that any future HTML being added is done in a way that is also accessible.

ii) It is important to note that one of the elements of an accessibility audit is based upon contrast of text against the background. I.e. you need to ensure your own corporate colours/CSS meet these standards. If they are changed and OneVu's CSS needs to change too please let us know ASAP.

iii) Having completed the changes above we tested OneVu against Google's Lighthouse Audit and the following score of 100/100 was achieved for accessibility:

*New means any website/web application published after 23rd September 2018.