For IBSS we strive to continually improve our support for accessible software. We are on a journey to target WCAG 2.2 Level AA with ongoing development and improved testing.

For our Mobile application, we are rebuilding from the ground up to target WCAG 2.2 Level AA compliance with the initial release (summer 2024).

Our approach to compliance is a gradual improvement on key functionality where needed, to ensure we cover not only the need to add desired features, but to also make sure these features are usable by as many people as possible. Where possible we are using UI frameworks like Material Design, to aid our designs for accessibility.

We have carried out several rounds of internal testing and testing with existing clients. We are also looking to expand our testing operations to include specialised 3rd party testing aimed specifically at WCAG compliance. 

We are committed to ensuring the IBSS platform is accessible and compliant with WCAG 2.2 Level AA.

WCAG 2.2 is based on 4 design principles:

• Perceivable: To ensure that users can access and understand the information and interface elements of a website, it is important to present content in a way that can be perceived through at least one of the user’s senses.
• Operable: It is essential that user interface elements and navigation are fully operable by users. This means that users must be able to easily interact with the interface, and should not be required to perform actions they are unable to do.
• Understandable: Users must be able to understand the information presented, and should know how to effectively use and navigate the website.
• Robust: A wide range of user agents, including assistive technologies, should be able to access website information and use the interface. This means that users should be able to continue accessing content even as technologies change.

We achieve this through the following activities:

• External Testing: A specialist service validates our compliance with WCAG 2.2 Level AA standards.
• Continuous Improvement: With every release, we enhance our platform’s accessibility features.
• Accessible UI Components/Frameworks: We use UI components with built-in high-level WCAG compliance wherever possible.
• Ongoing Testing: We regularly test and improve our platform to maintain and strengthen accessibility support.

Our goal is to provide an inclusive experience for all users and to go a step further to accommodate a broader range of disabilities.