Accessibility

At Guidewire, we are passionate about ensuring that technology empowers people, and that those with challenges or disabilities are still able to excel at their jobs and achieve their goals.

Jutro strives to be an inclusive platform, and supporting accessibility is critical to that mission. Our long-term goal is to achieve full accessibility support for all components and features of the framework, from planning to design and then from development to release.

Jutro components include accessibility support that conforms with the Web Content Accessibility Guidelines version 2.0 at the AA level (WCAG 2.0 AA), developed by the World Wide Web Consortium's Web Accessibility Initiative (W3C WAI).

This means that Jutro components can be:

• used without a mouse (keyboard only).
  • To achieve this, Jutro follows the Web Accessibility Initiative's Accessible Rich Internet Applications specification (WAI-ARIA) for Developing a Keyboard Interface.
• used with assistive technologies, including screen readers, screen magnification software and braille displays.
  • Jutro supports browser zooming up to 200% and responsive layout.
  • Jutro supports screen readers such as JAWS, NVDA, and VoiceOver with code that complies with WAI-ARIA standards.
  • Jutro component roles and names: components are built using standard markup. Where necessary, appropriate WAI-ARIA roles, such as button, link, and so on will be included, and each component will support an associated name (label), if applicable.
• used without a reliance on sound, color, animation, or timing.
  • The Jutro color scheme is designed to provide a luminosity contrast ratio of at least 4.5:1.

Jutro components aim for both functional accessibility and usable accessibility, with reference to four guiding principles:

1. Perceivable - Information and user interface components must be presented to users in ways they can perceive. This means that users must be able to perceive the information with their available senses.
2. Operable - User interface components and navigation must be operable. This means that users must be able to operate the interface (the interface cannot require interaction that a user cannot perform).
3. Understandable - Information and the operation of the user interface must be understandable. Content and operation of the UI must be accessible with available senses.
4. Robust - Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies. This means that users must be able to access the content as technologies and user agents evolve.

Validation is carried out via automation using Axe Core and manual assessment by UX Accessibility. Each component has been validated to meet the WCAG 2.0 AA success criteria. However, changes made by the content owner can affect the accessibility status of a component, and hence its conformance.

The design and implementation of applications needs to be done with accessibility in mind, which goes beyond the use of Jutro components. Be sure to review and follow the guidance located in the following locations:

How to Meet WCAG Quick Reference: https://www.w3.org/WAI/WCAG21/quickref/

WAI Authoring Practices 1.1: https://www.w3.org/TR/wai-aria-practices-1.1/