Scope & Objectives
...
The Samvera Community values accessibility and works to make all applications meet accessibility best practices, however, applications are not currently tested against WCAG standards and do not have a VPAT. The Samvera Community partnership discussed the needs at the Spring 2024 partners meeting and decided Samvera applications should meet WCAG standards and each applications should have a VPAT and/or accessibility roadmap. This satisfies the community goals of developing repository applications meeting the needs of all, and the institution requirements for compliance. Samvera Community members with knowledge of the code base have called for the accessibility requirements be baked into the processes of development, testing, and deployment.
Use Case:
Narrative text that should result in a common understanding of:
...
The overall domain into which the discussion falls
...
The shared needs and requirements within that domain
...
An institution has an accessibility policy for all commercial software purchased or Open Source software adopted, stating that software must meet certain accessibility standards and have accessibility documentation such as a VPAT and/or accessibility roadmap made available to the customer before that software can be purchased or adopted for staff and/or public use. Samvera software solutions must have a VPAT, even a rudimentary one, and an accessibility roadmap that demonstrates a timely commitment to ensuring the accessibility of the software. Samvera software solutions must also use tools for accessible software development, testing, and release.
Deliverables & Timeframe
- Establish barebones VPAT for Hyku
- Establish barebones VPAT for Avalon?
- Establish barebones VPAT for Hyrax
- Evaluate Website to determine changes needed to make VPATS available
- Evaluate process for code development, testing and deployment software release to determine changes neededNarrative or bulleted text describing the tangible outcomes of the working group.
- Recommendations for best practices for developing/maintaining VPATs and accessibility roadmaps for Samvera software solutions
- Establish an accessibility roadmap for one of the above Samvera software solutions (voted on by the members of the group once formed and meeting); charge the other software solutions to develop accessibility roadmaps using the process developed by this group as a guide
Timeframe
The timeframe for activities and producing deliverables should also be included in this section. Included should be a sunset date for the group (the date WG will end and announce the WG deliverables/accomplishments).
To be reviewed with Samvera Board
Meeting Times & Communication Channels
Note that following current best practices within Samvera, interest and working groups should use an existing communication channel unless and until it becomes clear that a dedicated channel is needed. This section should specify which existing channel(s) will be used: e.g., samvera-tech, samvera-partners, samvera-community@googlegroups.com. When using a shared channel, individual working groups should start the subject line with their name in []s, such as [archives] for the Archives Working Group. If and when a dedicated channel is needed, the new channel should be well publicized and open to any interested subscribers/participants in the community.
- Meeting dates/times/frequency TBD
- Communication channel:
- #accessibility-wg on Samvera Slack
- Emails to Samvera mailing list should begin with "Samvera Accessibility WG: Subject here"
Members
Note that Working Groups must have participants from three different Partners. All members of a working group producing software must be licensed Samvera contributors covered by the appropriate CLAs. Other types of contributions such as requirements, design, best practices, documentation, etc. - do not require CLAs but participants should accept that the materials to which they contribute may be released under a Creative Commons Attribution 4.0 International License..
- facilitator's name here, facilitator (facilitator's institution here)
- your name here (your institution here)
Resources
- helpful links
Meeting Notes
- list of links
- or table of meeting notes
Scope & Objectives
Narrative text that should result in a common understanding of:
The overall domain into which the discussion falls
The shared needs and requirements within that domain
Use cases that demonstrate these needs and requirements
Deliverables & Timeframe
Narrative or bulleted text describing the tangible outcomes of the working group.
The timeframe for activities and producing deliverables should also be included in this section. Included should be a sunset date for the group (the date WG will end and announce the WG deliverables/accomplishments).
Meeting Times & Communication Channels
Note that following current best practices within Samvera, interest and working groups should use an existing communication channel unless and until it becomes clear that a dedicated channel is needed. This section should specify which existing channel(s) will be used: e.g., samvera-tech, samvera-partners, samvera-community@googlegroups.com. When using a shared channel, individual working groups should start the subject line with their name in []s, such as [archives] for the Archives Working Group. If and when a dedicated channel is needed, the new channel should be well publicized and open to any interested subscribers/participants in the community.
Members
Note that Working Groups must have participants from three different Partners. All members of a working group producing software must be licensed Samvera contributors covered by the appropriate CLAs. Other types of contributions such as requirements, design, best practices, documentation, etc. - do not require CLAs but participants should accept that the materials to which they contribute may be released under a Creative Commons Attribution 4.0 International License..
...
Princeton and UVA are developing this charter and will enroll members from Hyku, Avalon, and Hyrax to participate, along with any other interested parties in the Samvera community.
- Robin Ruggaber, UVA (co-facilitator)
- Kate Lynch, Princeton (co-facilitator)
- your name here (your institution here)
Resources
- helpful links Accessibility documentation
- WCAG 2.0
- LevelAccess: Navigating the VPAT
- European Accessibility Act (EAA)
Meeting Notes
- list of links
- or table of meeting notes