2021-02-09 Meeting notes




Meeting ID: 264 479 336
Passcode: folio-lsp 


Paul Moeller

Khalilah Gambrell


Agenda and Notes 

Jira Check-in 

Accessibility Dashboard 

  • Keyboard navigation (hopefully) has found a team to work on
  • Short cut keys will be applied in Agreements, License (maybe), Users, and ER but won't be able to display within the App 
  1. CU Boulder - Schedule  | 2021 Schedule 
    1. Testing has started. 
    2. Meeting with Acquisitions to discuss feedback
  2. Updates from MSU testing? 
Accessibility Statement 

Accessibility Statement draft 


Wiki UpdateUse Cases draft
  • Added some more 
  • Khalilah will send to devs and POs for feedback
Next Meeting Planning / Parking Lot
  • Continue with Wiki and 'telling our story' 

Parking lot

  • Assistive Technology User Group 
  • FOLIO on tablets / touch technology / voice
  • New governance model (slidedeck)
  • Update on the accessibility demo 
  • Does one meeting a month keep us moving in a way that is sufficient?
  • What is the role of the SIG in the community? Relationship between development and testing. Especially with new modules. What is the expectations of the community of the SIG?  
  • What are implementers having issues with and what are others doing? Documentation of accessibility?
  • How is accessibility information about the resources built in into the system? 
  • Line between usability and accessibility 
  • User engagement 
  • Overarching Goal: Make sure that other libraries are able to adopt FOLIO 
    • What does an updated demo look like? (follow what Jane did and should show resolved issues) 
  • There is a request from the PC to develop process for telling the story of how we are improving the accessibility within FOLIO. There was also interest in having another demo of accessibility within FOLIO. 

    • Something to consider: report dashboard page for documenting evidence of improvement/testing 
    • egerman and Khalilah will review the Assessment Approach section to expand upon our practices. 
    • Documenting progress (explain what we did as a narrative and Abby can capture) 
    • Data element (tickets created / tickets resolved)