Run Accessibility Checker and Color Contrast Analyzer tools
Description
Environment
Potential Workaround
defines
relates to
Checklist
hideTestRail: Results
Activity
Khalilah Gambrell June 24, 2020 at 11:04 AM
All stories have been assigned to applicable teams. Thank you @Matt Connolly
Cate Boerema June 17, 2020 at 8:57 AM
Thanks @Matt Connolly! I added the "accessibility" label to the bugs you created so they end up in the right table on the FOLIO Bug Stats dashboard.
@Khalilah Gambrell I will leave it to you to review and close this issue. Could you please also assign the bugs to Core Functional that you think we should be responsible for fixing? It sounds like some issues are being worked by other teams, so I don't want to assume these should all be ours.
Thanks!
Matt Connolly June 16, 2020 at 8:25 PM
@Khalilah Gambrell Yes, I tested all those pages. I've created issues by type of error, so most of them list multiple points in the system that generate a given error (e.g., missing labels found in tags, fees/fines pages, open loan details, etc.). I've linked the new accessibility issues to this one.
Khalilah Gambrell June 16, 2020 at 4:38 PMEdited
@Matt Connolly, I just want to make sure that the following pages are tested with the accessibility tools defined in the user story
User Results list
Users Settings with the exception of custom fields
New/Edit User record
View User record
Tags panel
Patron block messaging
New/Edit Patron blocks
View patron blocks
View Open Loans with loans
View Closed loans with loans
Add permissions modal
Add service point modal
Create/Edit fee fine
View fee fine
Spitfire, Firebird, and stripes-force are addressing some of the issues you may find. I will link their stories to this one.
cc: @Oleksiy_Lemeshko and @Cate Boerema
Khalilah Gambrell March 20, 2020 at 12:07 PM
If your team plans to run an accessibility compliance checker on your app/plug-ins, please review the list of reported issues beforehand AND for any issues you create please add the label deque_<<quarter compliance checker ran>>_<<year compliance checker ran>>. AND if the reported issues are stripes related please add the label 'stripesissue'
Here is a link to all reported issues: https://folio-org.atlassian.net/issues/?filter=12107
WCAG 2.1 AA compliance is a key requirement of the FOLIO platform. To support this requirement, please do the following
Run the app through the Deque aXe compliance checker. Find plug-in here - https://ux.folio.org/docs/assets/axe/
Since FOLIO uses rgb(a) so ignore the color contrast errors that Deque aXe may report, instead use the WCAG color contrast tool - https://chrome.google.com/webstore/detail/wcag-contrast-checker/plnahcmalebffmaghcpcmpaciebdhgdf to identify any errors.
Run both tools against all actions and screens one can take and view in the app
No need to report datepicker and timepicker accessibility issues
Definition of done
Create user stories to address errors in backlog