[UXPROD-3043] Draft - Add WCAG 2.1 AA checklist as UX guideline Created: 16/Apr/21  Updated: 01/Jul/22  Resolved: 01/Jul/22

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: TBD
Reporter: Julian Ladisch Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: a11y, accessibility, delegate_candidate
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UXPROD-216 Accessibility: WCAG 2.1 AA Compliance. In Progress
relates to DEBT-5 No WCAG Support Closed
Development Team: Stripes Force
PO Rank: 0

 Description   

Task

Add all WCAG 2.1 AA success criteria to FOLIO's UX accessibility guidelinesĀ - either as an additional checklist (an external link to WCAG 2.1 AA is sufficient), or by adding them to the existing checklists.

Reasoning

The accessibility section of FOLIO's UX guidelines
https://ux.folio.org/docs/topics/accessibility/
contain 3 checklists:

  • Front-end accessibility checklist
  • UX accessibility checklist
  • Visual design accessibility checklist

They cover less than 50 % of WCAG 2.1 AA. For details see list below.

FOLIO development uses only these 3 checklists. Violations of other WCAG criteria are not considered a bug.

WCAG is the international accessibility standard.
European Union law requires all public sector bodies to comply with WCAG 2.1 AA.

Therefore FOLIO'x UX guidelines must list all WCAG 2.1 AA success criteria as checklist items.

WCAG 2.1 AA converage

This is the list of all WCAG 2.1 AA success criteria (taken from https://www.w3.org/WAI/WCAG21/quickref/?levels=aaa ), and how they are covered by FOLIO's 3 UX accessibility checklists:

1.1.1 Non-text Content partly
1.2.1 Audio-only and Video-only (Prerecorded) missing
1.2.2 Captions (Prerecorded) missing
1.2.3 Audio Description or Media Alternative (Prerecorded) missing
1.2.4 Captions (Live) missing
1.2.5 Audio Description (Prerecorded) missing
1.3.1 Info and Relationships partly, and partially wrong (H65)
1.3.2 Meaningful Sequence partly
1.3.3 Sensory Characteristics partly
1.3.4 Orientation missing
1.3.5 Identify Input Purpose partly
1.4.1 Use of Color covered
1.4.2 Audio Control missing
1.4.3 Contrast (Minimum) covered
1.4.4 Resize text covered
1.4.5 Images of Text covered
1.4.10 Reflow missing
1.4.11 Non-text Contrast partly
1.4.12 Text Spacing missing
1.4.13 Content on Hover or Focus missing
2.1.1 Keyboard partly
2.1.2 No Keyboard Trap missing (despite referencing 2.1.2.)
2.1.4 Character Key Shortcuts missing
2.2.1 Timing Adjustable missing
2.2.2 Pause, Stop, Hide missing
2.3.1 Three Flashes or Below Threshold missing
2.4.1 Bypass Blocks missing
2.4.2 Page Titled covered
2.4.3 Focus Order covered
2.4.4 Link Purpose (In Context) covered
2.4.5 Multiple Ways missing
2.4.6 Headings and Labels covered
2.4.7 Focus Visible covered
2.5.1 Pointer Gestures missing
2.5.2 Pointer Cancellation missing
2.5.3 Label in Name missing
2.5.4 Motion Actuation missing
3.1.1 Language of Page partly
3.1.2 Language of Parts missing
3.2.1 On Focus missing (despite referencing 3.2.1.)
3.2.2 On Input missing
3.2.3 Consistent Navigation partly
3.2.4 Consistent Identification partly
3.3.1 Error Identification partly
3.3.2 Labels or Instructions partly
3.3.3 Error Suggestion missing
3.3.4 Error Prevention (Legal, Financial, Data) missing
4.1.1 Parsing missing
4.1.2 Name, Role, Value missing (despite referencing 4.1.2.)
4.1.3 Status Messages missing



 Comments   
Comment by Khalilah Gambrell [ 28/Sep/21 ]

Julian Ladisch,

  • WCAG 2.1 AA is a part of all development teams' definition of done
  • We are also including automated Deque aXe testing with RTL/Jest
  • We also conduct accessibility testing with Michigan State and UC - Boulder
  • The documentation (https://ux.folio.org/docs/topics/accessibility/) was written to support WCAG 2.1 AA requirements. The documentation was written and approved by frontend developers including John Coburn. So I think the documentation does cover applicable WCAG 2.1 AA requirements to FOLIO.
  • What we can do is make it clearer how to use this documentation in relation to other documentation.
Generated at Fri Feb 09 00:28:53 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.