thatbudakguy
commented
2 years ago added comments to Camille's analysis, but here's a quick breakdown of the two major issues.
- Primary buttons don't have a focus style. this is a WCAG violation and makes it difficult for sighted keyboard users to submit reservation forms. This affects all pages that have primary buttons. Fortunately, it's an easy fix — we are explicitly disabling the focus style on these buttons in our CSS currently, so we just need to set a focus style. Probably good to get a designer's take, but in the meantime we can do something simple but functional. Relevant CSS here:
- The booking widget is not keyboard accessible. no one other than sighted mouse users can interact with this widget, which shows up on the library landing page and individual space booking page. It isn't quite game-over, though, because the "accessible version" of the booking experience works fine for both SRs and keyboard users. The only issue is that sighted keyboard users probably won't know to click the "version of this page for screen readers" link and will be frustrated when they can't initially access the booking widget. This link text should be updated so it's more obvious that keyboard users need to go to this page, too. I think this is a SpringShare thing; not sure what their bandwidth to address it is.
there's a few other minor issues, but nothing that is a blocker to access, and nothing that screen reader users aren't likely used to dealing with elsewhere.
anarchivist
SUL wants to go live with LibCal for group study room booking in Green, ideally by July 29, 2022. We need to undertake accessibility testing of this feature. I believe the pages we will need to test are the following:
The best recommendation I can follow is to look at the past accessibility analysis that Camille did in August 2021, which used the following methods: