Hi Steven & all, No specific reason at all. I just wasn't able to immediately find the 2.1 guide when I did a quick search on WCAG 2.
I've now found it after digging a bit deeper & can correct the link: https://www.w3.org/TR/WCAG21/ Again, I think the solution here is to establish a working group who can provide us (developers & myself) with better advice on aligning with WCAG. This advice has been lacking as we are entirely volunteer driven (quite literally I have no staff who work for me, I'm just a coordinator of volunteers who help me to maintain DSpace). As for establishing a working group, I've heard several folks interested in being a member of such a group. Therefore, I think all we'd need is a willing "chair" (or a set of co-chairs) to run the group. Such a working group can schedule meetings as you see fit, and you are more than welcome to use our DSpace Zoom (https://wiki.lyrasis.org/display/DSPACE/DSpace+Meeting+Room) for meetings (I'd need to give the chair access though if you wanted to record meetings or share screens). If anyone is interested in chairing such a group, please do get in touch. I'd be glad to talk with you on how to get started, and how we can work together to provide accessibility advice/requirements back to the development team (especially the team working on DSpace 7 right now). Thanks all! Tim ________________________________ From: [email protected] <[email protected]> on behalf of Hayles, Steven <[email protected]> Sent: Thursday, May 14, 2020 2:53 AM To: [email protected] <[email protected]> Subject: [dspace-community] RE: Accessibility - version of WCAG Hi Tim Thanks, that’s helpful. I see that you’ve updated the code contribution check list<https://wiki.lyrasis.org/display/DSPACE/Code+Contribution+Guidelines>, replacing the link to WCAG 1.0 with on for WCAG 2.0. What was the reason for choosing 2.0 rather than 2.1? Steven Hayles Systems Analyst Advance notice of leave: May 25-29, July 10-21 IT Services, University of Leicester, Prospect House, 94 Regent Rd, Leicester, LE1 7DA, UK Working from home e: [email protected]<mailto:[email protected]> w: le.ac.uk<http://www.le.ac.uk/> [cid:[email protected]] Follow us on Twitter<https://twitter.com/uniofleicester> or visit our Facebook<http://www.facebook.com/uniofleicester> page From: Tim Donohue <[email protected]> Sent: 12 May 2020 23:04 To: Hayles, Steven <[email protected]>; [email protected] Subject: Re: Accessibility - version of WCAG Hi Steven, 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. As noted in previous messages on this topic, we'd welcome the community to report issues as bugs. Keep in mind, as DSpace is community built/maintained software, we are reliant on willing volunteers (or service providers) to help us resolve such issues before the next release. So, if you find & issue and know how to fix it, please also report the fix, as that can help ensure it is resolved more rapidly. Thanks! Tim ________________________________ From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of Hayles, Steven <[email protected]<mailto:[email protected]>> Sent: Tuesday, May 12, 2020 11:25 AM To: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> Subject: [dspace-community] Accessibility - version of WCAG At the University of Leicester, we are auditing our many web services for WCAG 2.1 AA compliance. We currently have 3 DSpace instances. Two are running version 6.3 and the other one will be shortly. (Currently running 1.8.3 but not exposed to the internet.) I’ve seen that Tim discussed the approach to compliance on this group in March 2018: https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!searchin/dspace-community/WCAG|sort:date/dspace-community/gfnqfrww5Do/W3Ty9dyQAAAJ<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fforum%2F%3Futm_medium%3Demail%26utm_source%3Dfooter%23!searchin%2Fdspace-community%2FWCAG%257Csort%3Adate%2Fdspace-community%2Fgfnqfrww5Do%2FW3Ty9dyQAAAJ&data=02%7C01%7Csh23%40leicester.ac.uk%7C8efef93a828c481c356308d7f6c05e66%7Caebecd6a31d44b0195ce8274afe853d9%7C0%7C0%7C637249178393578814&sdata=%2FN%2FdMQ6waKc2705yFdvIy0sRHNTHP%2B4UDy0NVPuuqbo%3D&reserved=0> He referenced the code contribution guidelines, item 5 ‘User interface patches must be XHTML-compliant and have a W3C WCAG<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2FTR%2FWAI-WEBCONTENT%2F&data=02%7C01%7Csh23%40leicester.ac.uk%7C8efef93a828c481c356308d7f6c05e66%7Caebecd6a31d44b0195ce8274afe853d9%7C0%7C0%7C637249178393578814&sdata=09%2B2np5L8s9OQzrbhpzjn1e5iXb0MJe4JGGFQyxxZoA%3D&reserved=0> Conformance Level of "Double-A"’. The link here is to WCAG version 1.0. WCAG 2.0 compliance was raised in October 2018: https://wiki.lyrasis.org/display/cmtygp/DCAT+Meeting+October+2018<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.lyrasis.org%2Fdisplay%2Fcmtygp%2FDCAT%2BMeeting%2BOctober%2B2018&data=02%7C01%7Csh23%40leicester.ac.uk%7C8efef93a828c481c356308d7f6c05e66%7Caebecd6a31d44b0195ce8274afe853d9%7C0%7C0%7C637249178393588810&sdata=FmEwz7U84bSP7MvTF1NSwjSppOorsSMQ7L76MYunyD4%3D&reserved=0> Would/should WCAG 2.1 AA failures in DSpace 6 or 7 now be considered bugs? Thanks Steven Hayles Systems Analyst IT Services, University of Leicester, Prospect House, 94 Regent Rd, Leicester, LE1 7DA, UK e: [email protected]<mailto:[email protected]> w: le.ac.uk<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.le.ac.uk%2F&data=02%7C01%7Csh23%40leicester.ac.uk%7C8efef93a828c481c356308d7f6c05e66%7Caebecd6a31d44b0195ce8274afe853d9%7C0%7C0%7C637249178393588810&sdata=GApSlMTvXma%2F4nhOVG5fLFGvU95qHaocYl0%2Fl3F9mTw%3D&reserved=0> [cid:[email protected]] Follow us on Twitter<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2Funiofleicester&data=02%7C01%7Csh23%40leicester.ac.uk%7C8efef93a828c481c356308d7f6c05e66%7Caebecd6a31d44b0195ce8274afe853d9%7C0%7C0%7C637249178393598805&sdata=Gv7OLqH4IyTOv7aeGgvGqsNdIsXGwl1wqPfaehPuF3U%3D&reserved=0> or visit our Facebook<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.facebook.com%2Funiofleicester&data=02%7C01%7Csh23%40leicester.ac.uk%7C8efef93a828c481c356308d7f6c05e66%7Caebecd6a31d44b0195ce8274afe853d9%7C0%7C0%7C637249178393598805&sdata=950lFQXwwlo1dhvdBG1Zv%2BXD7Lhm3FodeqMO4zADzLY%3D&reserved=0> page -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fduraspace.org%2Fabout%2Fpolicies%2Fcode-of-conduct%2F&data=02%7C01%7Csh23%40leicester.ac.uk%7C8efef93a828c481c356308d7f6c05e66%7Caebecd6a31d44b0195ce8274afe853d9%7C0%7C0%7C637249178393598805&sdata=V8S6D7zrS%2FM6ZLGk%2Bz0qqqTIeD0VyjpVlWhXYZEK65Y%3D&reserved=0> --- 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]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-community/DB7PR06MB4695FB971BDFED125B817CA88ABE0%40DB7PR06MB4695.eurprd06.prod.outlook.com<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Fmsgid%2Fdspace-community%2FDB7PR06MB4695FB971BDFED125B817CA88ABE0%2540DB7PR06MB4695.eurprd06.prod.outlook.com%3Futm_medium%3Demail%26utm_source%3Dfooter&data=02%7C01%7Csh23%40leicester.ac.uk%7C8efef93a828c481c356308d7f6c05e66%7Caebecd6a31d44b0195ce8274afe853d9%7C0%7C0%7C637249178393608797&sdata=ua6LuQrqJ6pZZVf7qaRkkjn1j19qz7hWAS83SxMxZNQ%3D&reserved=0>. -- 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]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-community/AM6PR06MB46927D8F19BD787A3142CDF18ABC0%40AM6PR06MB4692.eurprd06.prod.outlook.com<https://groups.google.com/d/msgid/dspace-community/AM6PR06MB46927D8F19BD787A3142CDF18ABC0%40AM6PR06MB4692.eurprd06.prod.outlook.com?utm_medium=email&utm_source=footer>. -- 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/DM5PR2201MB1148753D0C9922B7DB9B9340EDBC0%40DM5PR2201MB1148.namprd22.prod.outlook.com.
