Scope & Objectives
Samvera has matured to have several applications an institution could select to satisfy their requirements. Increasingly Institutions are adopting requirements for all applications to meet Web Content Accessibility Guidelines (WCAG). Therefore market scans increasingly require all applications to have a Voluntary Product Accessibility Template (VPAT) and if rudimentary, language stating the goals and progress related to meeting compliance with WCAG to at least the minimum acceptable level.
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. 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
Use cases that demonstrate these needs and requirements
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 to determine changes needed
- 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..
- 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..
- 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