What Changed and Why It Matters

You may have noticed some UI changes recently — such as improved scrolling on list pages, refined color contrast in dark mode, and tighter keyboard navigation. But why did we dedicate so much development time to achieving this specific certification?

Here is a look at why we made these changes, what it means for your teams, and why accessibility is a core pillar of Spira’s future.

1. Championing Inclusivity and Equal Access

The most important reason we pursued WCAG 2.1 AA compliance is simple: it is the right thing to do.

Software development, testing, and project management are highly collaborative fields. By ensuring our platform is accessible to users with visual, auditory, motor, or cognitive disabilities, we are breaking down barriers to entry.

With improved screen reader support and highly structured page layouts, users who rely on assistive technologies can now navigate Spira’s complex grids, testing dashboards, and requirement hierarchies seamlessly. We want to ensure that every team member can contribute to their project's success without the software getting in the way.

2. Enhancing Usability for Everyone

A well-known principle in UX design is that "accessible design is good design." The changes we made to comply with WCAG standards don't just help users with disabilities; they improve the daily experience for all users.

  • Keyboard Navigation: Power users who want to navigate through test runs or update tasks rapidly can now do so entirely via their keyboards, saving time and reducing mouse fatigue.

  • Color Contrast & Dark Mode: By fixing color contrast issues in grid properties (especially in dark mode), the application is now much easier on the eyes, reducing strain during long working sessions.

  • Better UI Scaling: Fixes to grid cell label widths and responsive scrolling on left-hand sidebars mean the application behaves more predictably, whether you are on a massive desktop monitor or a zoomed-in laptop screen.

3. Meeting Global Compliance and Regulatory Standards

Many of our customers operate in highly regulated industries—such as government, healthcare, finance, and defense. For these organizations, software accessibility isn't just a nice-to-have; it is a strict legal requirement.

By aligning Spira with WCAG 2.1 AA, we are helping our clients meet mandatory global accessibility laws, including:

  • Section 508 of the Rehabilitation Act (United States)

  • The Americans with Disabilities Act (ADA) (United States)

  • The European Accessibility Act (EAA) (European Union)

  • AODA (Ontario, Canada)

Achieving this standard ensures that our enterprise and public-sector clients can confidently deploy Spira across their organizations without compliance concerns.

4. Supporting the Modern, Diverse Workforce

Teams are more distributed and diverse than ever before. When you choose a platform to manage your application lifecycle, you need a tool that scales with your workforce. If a tool is inaccessible, it limits who you can hire and how your team can collaborate. By adhering to WCAG 2.1 AA guidelines, Spira empowers organizations to build diverse, inclusive teams where every developer, tester, and project manager has the tools they need to thrive.

What’s Next?

Accessibility is not a one-time project; it is an ongoing commitment. This dedication is formally outlined in Inflectra's Accessibility Commitment Statement.

While closing [RQ:5592] represents a massive leap forward for the Spira platform, we are continually auditing new features, listening to user feedback, and refining our interface to ensure we maintain these standards in every future release.

If you have feedback on the new accessibility improvements or suggestions for how we can make Spira even better, we’d love to hear from you!