Skip to main content

Accessibility overview

General accessibility responsibility statement

At Guidewire, we are committed to ensuring that our software products, design system, and documentation resources are accessible and usable by everyone. We firmly believe that software experiences must be inclusive and accessible to all users. Accessible design not only supports people with disabilities, but also results in better, more usable experiences for everyone.

Our standards

We strive to conform to the Web Content Accessibility Guidelines (WCAG) as our baseline accessibility standard. These internationally recognized guidelines define how to make digital content more accessible to people with a wide range of disabilities, including visual, auditory, motor, and cognitive impairments. Where applicable, our products and resources are evaluated against WCAG 2.2 Level AA.

Our process

Accessibility considerations are integrated into our design, development, and testing practices. We conduct regular accessibility reviews and continuously identify and address accessibility improvements. Known accessibility issues are tracked and prioritized based on their impact on users.

Accessibility testing typically includes a combination of:

  • Manual assessment by our UX Accessibility Specialists
  • Automated testing using industry-standard tools
  • Testing with common assistive technologies and browsers, as documented in our Voluntary Product Accessibility Templates (VPATs)

Jutro digital experiences: Build and extend

This statement applies to Jutro resources intended to enable customers to build their own digital experiences, including:

  • The Jutro Design System
  • Jutro application templates and starter projects

Jutro Design System

The Jutro Design System is designed to support the creation of accessible digital experiences. Our goal is to ensure that design system components are accessible, usable, and reliable as a foundation for customer development.

Component accessibility

Jutro components are designed, developed, and tested to meet WCAG 2.2 Level AA accessibility standards in their default, base configuration implementation. When used as provided, components include appropriate semantics, keyboard behavior, focus management, and visual contrast.

Accessibility validation includes:

  • Manual assessments by the UX Accessibility team and Jutro engineers
  • Automated testing using Axe Core

Each component is validated against applicable WCAG success criteria, and known accessibility limitations are documented in our VPAT.

Configuration and customer responsibility

Accessibility depends on how components are used and combined within an application. Once components are styled, configured, extended, or combined into application flows, it becomes the responsibility of the customer development team to ensure the resulting application remains accessible.

Customizations such as removing labels, altering keyboard behavior, or changing color contrast can introduce accessibility issues.

Therefore:

  • Guidewire is responsible for the accessibility of core Jutro components in their base configuration
  • Customers are responsible for the accessibility of applications built using those components
  • Any customized or extended components must be reviewed and tested for accessibility as part of the customer's development and QA process

Documentation includes guidance and best practices for accessible usage of components.

Jutro templates

Jutro templates are provided as starting points that demonstrate good development and accessibility practices. These templates are designed and audited to align with WCAG 2.2 Level AA.

Once customers modify or extend templates, responsibility for ongoing accessibility compliance rests with the customer.

Jutro reference applications

Guidewire provides Jutro reference applications that demonstrate recommended design patterns, coding practices, and accessibility considerations using the Jutro Design System.

These reference applications:

  • Are intended as examples
  • Are audited against WCAG 2.2 Level AA for representative screens
  • Include accessible patterns and implementations where possible

Accessibility validation includes:

  • Manual testing by the UX Accessibility team
  • Automated testing with Axe Core
  • Review of selected, representative user journeys

As with templates, reference applications are not intended to be production-ready solutions. Once customers adapt, extend, or reuse reference application code, they are responsible for ensuring accessibility compliance in their final implementation.

Feedback and resources

Feedback is always welcome. If you experience any accessibility barriers or have suggestions for improvement, please contact us. For additional Guidewire-specific information, please view our product documentation.

Customers are strongly encouraged to conduct their own accessibility testing, including keyboard, screen reader, and color contrast checks, and follow established guidance: