[UXPROD-216] Accessibility: WCAG 2.1 AA Compliance. Created: 19/Feb/18 Updated: 06/Feb/24 |
|
| Status: | In Progress |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Epic | Priority: | P3 |
| Reporter: | Cate Boerema (Inactive) | Assignee: | Khalilah Gambrell |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | accessibility, sysops_mgt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||
| Epic Name: | Accessibility: WCAG 2.1 AA Compliance | ||||||||||||||||||||
| Development Team: | Stripes Force | ||||||||||||||||||||
| Score: | 32.88 | ||||||||||||||||||||
| Start date (migrated): | |||||||||||||||||||||
| End date: | |||||||||||||||||||||
| Epic Color: | ghx-label-6 | ||||||||||||||||||||
| Description |
|
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" |
| Comments |
| Comment by Cate Boerema (Inactive) [ 19/Feb/18 ] |
|
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. |
| Comment by Mike Gorrell [ 20/May/20 ] |
|
Khalilah Gambrell - do you have any sense for when FOLIO might attain WCAG 2.1 AA Compliance? |
| Comment by Khalilah Gambrell [ 21/May/20 ] |
|
Mike Gorrell, my hope is FOLIO can state it full supports most of WCAG 2.1 AA by October/November. But we need: 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: Hkaplanian, John Coburn, and Cate Boerema |