The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
The software authoring company has committed to addressing these issues by 30 April 2022:
Only a sample of pages were tested. The issues found may be present on other screens which may contain other issues.
The University of Birmingham Logo doesn’t have any Alt Text.
This fails WCAG success criterion 1.1.1 (non-text content) which recommends that images and form image buttons to always have appropriate, equivalent alternative text. This is also found on the Group Dashboard page.
On the login page, ‘Forgot Password’ is a local link with no destination. Site pages do not always use headers, regions or landmarks appropriately. Search buttons are not labelled. This fails WCAG success criterion 1.3.1 (Information and Relationships) which recommends that semantic mark-ups, regions/landmarks, lists and emphasised or special text are used appropriately. This issue was also found on the Group Management page.
A large number of items are not in the tab index. This fails the WCAG success criterion 1.3.2 (Meaningful Sequence) which recommends that the reading and navigation order is logical and intuitive.
On the login page the following items have insufficient contrast: Username, Password, Forgot Password link, Login, Login with single sign-on. On the dashboard the contrast of the tiles and the search input field contrast is too low. This fails WCAG success criterion 1.4.3 (Contrast Minimum) which recommends that text and images of text have a contrast ratio of at least 4.5:1. This issue was also found on the Group pages tested.
At a width of 320 pixels on the dashboard the Home icon and text overlap each other and for all pages feedback option is off the screen. This fails WCAG success criterion 1.4.5 (Images of Text) and 1.4.10 (Reflow) which recommends that there is no loss of content or functionality and ne need to scroll horizontally when content is presented at a width of 320 pixels. On the Group Dashboard page the Reflow issue is found as content is not visible without having to scroll in two dimensions.
Zooming and scaling is disabled, affecting use on mobile devices.
This fails WCAG success criterion 1.4.4 (Resize text) which recommends that the page is readable and functional when zoomed to 200%.
On the dashboard the icons in coloured boxes have insufficient contrast. This fails WCAG success criterion 1.4.11 (Non-text Contrast) which recommends a contrast ration of at least 3:1 for differentiating graphical objects. This issue was also found on the Group pages tested.
In the application the following are not accessible by the keyboard: Data Manager Menu, the Settings Menu, and anything on the main screen other than the ‘add message’ icon and the Dashboard breadcrumb. This fails WCAG success criterion 2.1.1 (Keyboard) which recommends that all page functionality is available via the keyboard. This issue was also found on the Group pages tested.
There is a header and menu on screen at all times, and to reach a new screen you have to tab through the menu. This fails WCAG success criterion 2.4.1 (Bypass Blocks) which recommends a link to skip navigation and other page elements that are repeated across web pages. This issue was also found on the Group pages tested.
The page title for the login page is not descriptive enough, it should be ‘Log in to Cards Online – University of Birmingham’, or similar. This fails WCAG success criterion 2.4.2 (Page Titled) which recommends that a web page has a descriptive and informative page title.
Menu items Data Manager and Setting Menu and anything apart from Add Message and the Dashboard breadcrumb are not accessible via the keyboard. The ‘Add Message’ screen does not transfer focus to the popup it opens, or receive it back when the popup is closed. This fails WCAG success criterion 2.4.3 (Focus Order) which recommends that the navigation order of links, form elements, etc., is logical and intuitive. This issue was also found on the Group pages tested.
The left hand menu links don’t convey their purpose clearly when using a keyboard and screen reader. The tab runs down the icons and not the text and the icons aren’t described clearly. This fails WCAG success criterion 2.4.4 (Link Purpose (In Context)) which recommends that the purpose of each link (or form image button or image map hotspot) can be determined from the link text alone, or from the link text and its context (e.g., surrounding text, list item, previous heading, or table headers). This issue was also found on the Group pages tested.
The focus indicator is indistinct. This fails WCAG success criterion 2.4.7 (Focus Visible) which recommends that it is visually apparent which page element has the current keyboard focus (i.e. as you tab through the page, you can see where you are).
The visible name icon ‘My account’ has the accessible name ‘account circle’. This fails WCAG success criterion 2.5.3 (Label In Name) which recommends that if an interface component (link, button, etc.) presents text (or images of text), the accessible name (label, alternative text, aria-label, etc.) for that component must include the visible text.
The language of site pages is not set. This fails success criterion 3.1.1 (Language Of Page) which recommends that the language of page content that is in a different language is identified using the lang attribute (e.g., <blockquote lang="es">). This issue was also found on the Group Management page. This issue was also found on the Group Dashboard page.
On the login page there are no suggestions for fixing inputting errors for username and password. This fails WCAG success criterion 3.3.3 (Error Suggestion) which recommends that suggestions are provided for fixing input errors in timely and accessible manner.
On the dashboard the large coloured panels are not identified with roles or have accessible names. This fails the WCAG success criterion 4.1.2 (Name, Role, Value) which recommends that mark-up is used in a way that facilitates accessibility. This includes following the HTML/XHTML specifications and using forms, form labels, frame titles, etc. appropriately. This issue was also found on the Group pages tested.
On the login page the error message for inputting invalid username or password is not announced. This fails WCAG success criterion 4.1.3 (Status Messages) which recommends that important status messages are announced to screen reader users.