2025/05/07 Samvera Accessibility WG Meeting Notes

Samvera Community Wiki


2025/05/07 Samvera Accessibility WG Meeting Notes

Attendees:

  • @Robin Lindley Ruggaber

  • @Nicholas Mark Homenda

  • @Kate Lynch

  • @Rebekah Kati

  • @Margaret Mellinger

  • @Former user (Deleted)

Regrets:

  • @Jon Cameron

Agenda and notes:

  • Participation on the Samvera Roadmaps Alignment Group - outcome of Samvera Virtual Connect today

    • Nick Mark Homenda and Jon Cameron currently already attend.

    • Kate will check in with Julie Hardesty about this.

  • Testing with Fable?

    • Could get on the testing schedule to utilize this as a resource

    • Between now and end of September, but we would need to get scheduled

    • What do we want to test in each of the three softwares?

      • A good first step could be focusing on the basics – acting as a user and performing a simple deposit

      • Look at aligning these tasks with Hyku as well.

      • What about Avalon? That could be different/more complex.

    • Next steps

      • Kate will check in with Princeton colleagues about what a user interview would look like, and about getting on the schedule for August/September.

      • Let’s think about what specifically we would want to test.

  • Next steps for advancing VPATs

    • Hyrax

      • Nick has begun a bare bones draft.

      • Could use some help, looking at portions of the document not done yet. Some of this would involve looking at nurax and figure out how to test, to be able to answer those questions.

    • Hyku

    • Avalon

    • Questions

      • What constitutes a bare-bones VPAT?

      • What is our methodology for doing accessibility-related improvements?

      • How do we make sure that, once we have a VPAT, it’s being updated along with the software upgrades?

        • There’s an expectation that VPATs get updated with each major release, not minor releases.

      • We could like a pointer to outstanding accessibility-related issues in GitHub for each

        • Using a standardized GitHub labeling scheme