In an era where digital inclusion is paramount, accessibility is no longer just a consideration but a crucial aspect for businesses aiming to meet Diversity, Equity, and Inclusion (DEI) obligations.
At Juriba, we understand the significance of providing accessible solutions, and our commitment to inclusivity is evident in every facet of our products.
Our ongoing commitment to accessibility means you can rest assured that when you engage your end-users using Juriba they will be able to use them regardless of any accessibility needs.
Understanding digital accessibility
Digital accessibility ensures that websites, mobile apps, and software are usable by individuals with diverse disabilities. Compliance with the 50 guidelines outlined in WCAG 2.1 AA is crucial for providing a seamless experience. Examples include screen reader support, keyboard-only navigation, high contrast mode, and session extension.
Demonstrating our commitment
-
VPAT: We engage IAAP accredited agencies to produce VPATs for each product every 12-18 months. These are published in our documentation at Juriba Platform Accessibility VPAT and Juriba AppM Accessibility VPAT.
-
Definition of Ready & Done: Our SDLC process ensures that accessibility requirements are considered during the design phase (Definition of Ready) before development even begins and before a feature is signed off after development is complete (Definition of Done).
-
Documentation: Our product documentation adheres to the same accessibility standards as the products themselves.
-
Internal Testing: Regular testing ensures that every product change complies with accessibility guidelines.
-
External Audit: Engaging objective, external digital accessibility specialists for audits holds us to high bar, and ensures full compliance with WCAG 2.1 AA.
-
Coding Standards: Our developers follow coding standards that include guidelines for accessibility.
-
Static Code Analysis: Automated tests at the code level verify technical elements for accessibility features.
Image: Screenshot of Juriba product in high contrast mode.
Image: Screenshot showing how Juriba highlights the focus area for a keyboard only user.
Image: Screenshot showing how users can "skip to main content" link (top left) that lets a keyboard user skip the menu and navigate directly to the main part of the page
What’s next?
W3C WAI released updated WCAG 2.2 guidelines in October 2023. Our next VPAT refresh will incorporate these new guidelines.
FAQ
-
Why WCAG 2.1 AA and not A? Level A is the minimum level of conformance and fairly straight-forward to meet. It incorporates only basic accessibility features. Level AA compliance takes digital accessibility much further and enables a more inclusive, user-friendly digital experience.
-
Why WCAG 2.1 AA and not AAA? Practicality; WCAG AAA is quite restrictive and generally impractical for complex enterprise applications. WCAG AA meets the needs of the majority of users.
-
Why not WCAG 2.2? Testing for WCAG 2.2 guidelines is included in our process, and the next VPAT will cover these updates.
-
Why is our VPAT better? Our VPAT is produced as the result of an external audit by an accredited agency who rigorously test and hold us to high standards. Many VPATs are produced by the vendor themselves, without specialist knowledge.
-
Other Standards: We also comply with Section 508 (US) and EN 301 549 (EU).
Conclusion
Juriba’s commitment to digital accessibility goes beyond just ticking the box. Digital accessibility is at the heart of our SDLC. This reflects our commitment to building inclusive digital products and supporting our customers to meet their diversity and inclusion objectives and obligations.
