2021-04-13 Meeting notes

Date

13 Apr 2021

Zoom

https://us02web.zoom.us/j/264479336?pwd=U0tBcWg5b3pJZWJrK2FCREM2alBGQT09

Meeting ID: 264 479 336
Passcode: folio-lsp

Attendees

egerman

Paul Moeller

@ Zoë McLaughlin

Khalilah Gambrell

@heidi schroeder

Agenda and Notes

Topic	Details	Notes
Jira Check-in	Accessibility Dashboard	Several dev teams were able to address issues in Iris Keyboard navigation adding to apps (e-holdings and agreements (creating and saving records). Baseline keys and have to be implemented at the app level (can't be implemented in STRIPES) Users has keyboard shortcut modal Panes not focusing, P2: STRIPES-701 - Getting issue details... STATUS
New SIG Charge	SIG Charge 2.0 - charge that all SIGs have	Any questions or feedback?
Testing	CU Boulder - Schedule \| 2021 Schedule Testing has started. Meeting with Acquisitions to discuss feedback Updates from MSU testing	Course Reserves issue doesn't have a development team UXPROD-2996 - Getting issue details... STATUS UC Boulder completed screenreader testing of Courses app. See feature that includes results: https://folio-org.atlassian.net/browse/UXPROD-2996 Michigan State has also conducted accessibility testing of several apps - report is available - https://docs.google.com/spreadsheets/d/1-ZfFvEc7NSNECZMlQBZtylCSBEWMUK_51lBwjxjIw7c/edit#gid=0 Will send recording
Accessibility Statement	Accessibility Statement draft	There was a request to add "non-accessible content' as a section of the statement. This is common/required in Europe. Is "Non-accessible content is documented on our accessibility dashboard.". Appropriate?
Wiki Update	Use Cases draft	About the SIG Meeting Notes Accessibility Commitment Accessibility Statement User Testing Reports Accessibility Dashboard Resources For Product Owners For Developers For UX Designers Documentation Report an Issue
Next Meeting Planning / Parking Lot		Review updated wiki

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)