Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

TimeItemWhoNotes

"Won't Do" on Dashboard

The Accessibility Dashboard lists all known accessibility issues in its UAT Backlog section, however, valid accessibility issues that have been closed as "Won't Do" are not listed.

Institutions in the European Union are required by European Union law to report ALL known issues including the "Won't Do" issues.

Can the "Won't Do" issues been added to the issue list of the Accessibility Dashboard? Otherwise a line with a link to those issues should be added at the top of the page.

Example: FOLIO-3229 reports more than 100 WCAG violations where <div> is used but <h1> ... <h6> should be used instead. FOLIO will never fix it because it was decided that the issue must be closed as "Won't Do".


Complete Accessibility Review

UXPROD-3133 "Complete Accessibility Review"

Institutions in the European Union are required by European Union law to conduct a complete accessibility review of the parts of FOLIO that they use

(UXPROD-3133 Complete Accessibility Review)

. To avoid duplicate work all accessibility reviews should be published on the A11Y SIG wiki.


UX guidelines

UXPROD-3043 "Add WCAG 2.1 AA checklist as UX guideline"

FOLIO's UX guidelines https://ux.folio.org/docs/topics/accessibility/ cover less than 50 % of WCAG 2.1 AA and has two guidelines that contradict WCAG 2.1 AA.

Developers don't care about WCAG, they only care about FOLIO's UX guidelines.

Therefore the latter should be extended to completely cover and comply with WCAG 2.1 AA.

...