IT Services

1.1.1 Non-text Content

Some non-text content presented to the user does not have a text alternative serving the equivalent purpose. Users with visual disabilities who rely on a screen reader may be unable to access or understand non-text content. This fails WCAG success criterion 1.1.1 (non-text content).

1.3.2 Meaningful Sequence

The logical reading order of content, causing confusion for screen reader users and those navigating via keyboard. This can lead to missed instructions, inaccessible workflows, or an inability to complete tasks, especially for users with visual or cognitive impairments. Ensuring a meaningful sequence improves usability and prevents frustration. This fails WCAG success criterion 1.3.2 (meaningful sequence).

1.3.5 Identify Input Purpose

Input fields in forms are not clearly defined and their purposes may not be understood by assistive technologies. For users with disabilities, particularly those using screen readers or with cognitive challenges, the lack of clarity may lead to confusion and user errors. This fails WCAG success criterion 1.3.5 (Identify Input Purpose)

1.4.3 Contrast (Minimum)

The visual presentation of text and images of text does not have a contrast ratio of at least 4.5:1. Users may have trouble perceiving, understanding and interacting with content due to the poor contrast of content and navigation. This fails WCAG success criterion 1.4.3 (Contrast (Minimum)

Not all functionality within the content is operable through a keyboard interface. Users will face accessibility barriers as keyboard-only navigation is unavailable, limiting access for individuals with motor disabilities who rely on keyboard input. This fails WCAG success criterion 2.1.1 (Keyboard).

2.4.1 Bypass Blocks

There is no mechanism available to bypass blocks of content that repeat on multiple web pages. Users will face difficulty in navigating and accessing essential content as they are unable to bypass repetitive blocks of content, hindering efficiency, and usability, particularly for screen reader users. This fails WCAG success criterion 2.4.1 (Bypass Blocks).

2.4.4 Link Purpose (In Context)

The purpose of every link on the webpage isn't clear by reading the link text or by considering the text alongside its surrounding context. This means users don't know exactly where the link will take them or what it will do when clicked, creating confusion and frustration when unintended actions occur. This fails WCAG success criterion 2.4.4 Link purpose.

2.4.6 Headings and Labels

Headings and labels may be unclear or non-descriptive, making it harder for users to navigate and understand content, especially those using screen readers. Poorly structured or vague headings can slow down users, particularly those with cognitive impairments, by making information harder to find. This fails WCAG success criterion 2.4.6 Headings and Labels.

2.4.7 Focus Visible

Without a visible keyboard focus indicator, users who rely on keyboard navigation may struggle to know where they are on the page, leading to confusion and making the website difficult to use, especially for those with disabilities. This fails WCAG success criterion 2.4.7 (Focus Visible).

2.5.8 Target Size (Minimum)

When interactive elements like buttons or links are too small, users with motor impairments, such as those with tremors, arthritis, or limited dexterity, may find it difficult to accurately tap or click on them. This lack of precision can lead to mistakes, such as unintended clicks, which can frustrate users and hinder their ability to navigate the site efficiently. On touch devices, especially with smaller screens, the problem is magnified, making it harder for users to access important features or content, potentially excluding them from fully using the siteThis fails WCAG success criterion 2.5.8 (Target Size (Minimum).

3.2.3 Consistent Navigation

Navigation elements appear in inconsistent locations across pages, making it difficult for users to predict and efficiently find what they need. This particularly impacts users with cognitive impairments, screen reader users, and those relying on keyboard navigation, increasing confusion and cognitive load. This fails WCAG success criterion 3.2.3 Consistent Navigation.

3.2.4 Consistent Identification

Interactive elements with the same function (e.g., search bars, buttons, links) are labeled or styled inconsistently, causing confusion for users. This particularly affects those with cognitive impairments and screen reader users, who rely on predictable naming and structure to navigate efficiently. This fails WCAG success criterion 3.2.4 Consistent Identification

3.3.2 Labels to Instructions

Clear labels or instructions are not provided when user input is required, users may struggle to understand what information is needed, leading to errors and frustration. This lack of guidance can make tasks confusing and time-consuming, negatively impacting the user experience, especially for those who are less familiar with the website or have cognitive disabilities. This fails WCAG success criterion 3.3.2 (Labels or Instructions).

3.3.8 Accessible Authentication (Minimum)

As part of the sign-in process, users are required to pass a cognitive function test, a verification code generated or received on a device. This maybe difficult for end users, particularly those with cognitive disabilities. This fails WCAG success criterion 3.3.8 Accessible Authentication (Minimum).

4.1.2 Name, Role, Value

For all user interface components, the name and role cannot be programmatically determined; states, properties, and values that cannot be set by the user or programmatically set; and notification of changes to these items is not available to user agents, including assistive technologies. Users will have trouble understanding and interacting with elements as they lack proper labelling, role assignment, or value identification, leading to confusion and reduced accessibility, especially for users relying on assistive technologies. This fails WCAG success criterion 4.1.2 (Name, Role, Value).