On Tue, May 12, 2020 at 10:03:51PM +0000, Tim Donohue wrote: > Yes, you are welcome to report WCAG compliance issues (v1 or v2) as bugs. > Obviously, keep in mind though that DSpace is unable to guarantee WCAG > compliance for *content added into DSpace* (as that is based entirely on your > local usage of DSpace). As a simple example, I know WCAG v2.1 A compliance > requires captions for prerecorded videos. As DSpace has no video captioning > capabilities (and likely never will), it is up to the institution using > DSpace to pre-caption any videos they plan to store in their DSpace if they > want full WCAG compliance for their DSpace. > > So, in general, for DSpace, the goal is to try to align with WCAG latest > guidelines. But, obviously some guidelines require your own local policies > or workflows to ensure content added into DSpace is also WCAG compliant, that > your local theme is WCAG compliant (as even tiny changes like color scheme > can affect compliance), etc.
Would it require more than reasonable effort for DSpace to provide a "compliance profile" outlining portions of the standard which DSpace is expected to implement? Sites would benefit from a clear understanding of where to look for noncompliance issues: DSpace, local modifications, or user content. -- Mark H. Wood Lead Technology Analyst University Library Indiana University - Purdue University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 www.ulib.iupui.edu -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-community/20200513120901.GB25032%40IUPUI.Edu.
signature.asc
Description: PGP signature
