Accessibility: WCAG 2.1 AA Compliance.
Description
Priority
Labels
Fix versions
Development Team
Assignee

Parent
Parent Field Value
Parent Status
is defined by
Checklist
hideTestRail: Results
Activity

Khalilah Gambrell May 21, 2020 at 11:21 AMEdited
, my hope is FOLIO can state it full supports most of WCAG 2.1 AA by October/November. But we need:
1.) Teams to run their apps through an accessibility checker and address bugs.
2.) Have a group or third party vendor review FOLIO against all WCAG A and AA guidelines
3) Teams follow the Accessibility dev documentation https://github.com/folio-org/stripes-components/blob/master/docs/AccessibilityDevPrimer.md#development-checklist
Common issues we have are tied to web development best practices such as all form elements must have labels. Other issues require some stripes work like reflow and focus issues.
cc: , , and

Mike Gorrell May 20, 2020 at 1:15 PM
- do you have any sense for when FOLIO might attain WCAG 2.1 AA Compliance?

Cate Boerema February 19, 2018 at 3:31 PM
I entered this epic because it appears on the Sys Ops and Management tab of the v1 roadmap. That said, I am going to close it as a duplicate because I think it is superseded by the epics on the Accessibility tab.
Details
Reporter
Cate BoeremaCate Boerema(Deactivated)Score
32.88TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Reporter

Per Accessibility SIG: Folio should comply with WCAG 2.1 Priority AA. Therefore, Stripes components, UI Design, Frontend development must adhere to this guideline.
See https://folio-org.atlassian.net/wiki/pages/viewpage.action?pageId=5374397 "Product Owner Accessibility Testing & Requirements"
and https://ux.folio.org/docs/guidelines/accessibility/ "UX Accessibility Guidelines"