Happy Monday to you all! This post is an update on some fixes and enhancements we've made but it also serves as an explanation of how we approach accessibility (and bugs in general) at Kuali.

Noteworthy Fixes

Here are just a few of the recent noteworthy fixes and enhancements that we've recently rolled out in Build:

• Keyboard focus added/fixed on multiple navigational elements
• Error messages are now screen-reader compatible
• Some screen reader messaging (including some button labels) was unclear

We have new stuff we're fixing all the time and a couple of larger enhancements coming soon. 

Our Approach to Accessibility

If you weren't already aware, one of our software development policies is called Zero Bug. This means we try to keep our bug list to zero (or near zero) every week. We aren't always perfect at this but we do a pretty good job.

In terms of accessibility, we actually treat accessibility issues as bugs. Naturally, we try to address them before they become bugs—as part of our typical development process—but occasionally some sneak past us. When they do, we add them to our bug list and apply our Zero Bug policy liberally and with glee.

Report Them Bugs 🐜

So that's a little "inside baseball" for you today. Hopefully that gives you a clearer idea of how we Do Our Thing™ here at Kuali. 

As usual, we encourage you to report any accessibility (or other) bugs. We appreciate the feedback we get from our customers and thank you for helping us make our software better. Cheers! ✌️