Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: link: WCAG 2.1 AA by law


The FOLIO platform must be WCAG 2.1 AA compliant and this requirement is also included in the Technical Council's Definition of Done draft.  WCAG 2.1 AA compliance is important as many libraries have accessibility requirements by law or by policy and require software providers to complete a Voluntary Product Accessibility Template (VPAT) to describe its accessibility efforts. Accessibility is a key factor whether an institution will use a product/platform.


Keyboard testing is one of the best and easiest ways to identify accessibility issues. If a user must use a mouse to navigate or complete an action then it is not accessible.  Keyboard testing should take no more than 30 minutes for the most complex of apps. Check out a great table by WebAIM on how to conduct keyboard testing

Keyboard focus is on Titles tab

When conducting keyboard testing you want to check: 

  • Navigate a page in a logical order. Are you able to use the keyboard to navigate on links/actions/content in a way that makes sense? A logical order is one where you navigate a pane/page left to right and from top to bottom.  
  • Ensure focus is clearly indicated. As you navigate FOLIO with a keyboard, it is important that the focus is clearly indicated as shown on screenshot.

How to start this effort? 

  • Add to your team's definition of done for frontend developers to conduct keyboard testing on applicable user stories. This test should not take very long! 

  • POs should schedule time (at the end of a quarter) to conduct keyboard testing of his/her apps. Add these stories to your backlog with the label 'a11y.' If you are unable to do so, then ask a SIG member to assist. 

  • Remind your team that WCAG 2.1 AA compliance is a condition of definition of done. Please have them reach out to John Coburnfor more developer details.