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] <[email protected]> on 
behalf of Hayles, Steven <[email protected]>
Sent: Tuesday, May 12, 2020 11:25 AM
To: [email protected] <[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

He referenced the code contribution guidelines, item 5

‘User interface patches must be XHTML-compliant and have a W3C 
WCAG<http://www.w3.org/TR/WAI-WEBCONTENT/> 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



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<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



--
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/DB7PR06MB4695FB971BDFED125B817CA88ABE0%40DB7PR06MB4695.eurprd06.prod.outlook.com<https://groups.google.com/d/msgid/dspace-community/DB7PR06MB4695FB971BDFED125B817CA88ABE0%40DB7PR06MB4695.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/DM5PR2201MB114890056EBA38911FBDB7AFEDBE0%40DM5PR2201MB1148.namprd22.prod.outlook.com.

Reply via email to