It is a great idea to have a working group to work on accessibilities. I have been dedicated to the task for a few weeks to solve most our DSpace accessibility issues (we ignored the contrast errors though). I have most of them cleared but some I can't seem to figure out. I'd love to be part of the team.
Ying Rice University https://scholarship.rice.edu On Wed, May 13, 2020 at 11:24 AM Jeffrey Sheldon <[email protected]> wrote: > Without a formal contact in place yet, I'll respond here. > > Representing K-State Libraries, I'm highly interested in being a part of a > DSpace Accessibility Working Group (DAWG). > > > -Jeff > > > ________________________________________ > From: [email protected] <[email protected]> > on behalf of Tim Donohue <[email protected]> > Sent: Wednesday, May 13, 2020 9:59 AM > To: Mark H. Wood; [email protected] > Subject: Re: [dspace-community] Re: Accessibility - version of WCAG > > Hi Mark, > > I think that sounds like a nice idea. I'd love to see DSpace provide more > detailed advice around accessibility. That's not something I can claim > expertise in though, so I think it'd likely require efforts of some > volunteers with this expertise or interest in building up this expertise. > It also could be the start of a DSpace Accessibility Working Group (if we > found enough interested folks). > > So, yes, I love the idea & I think it'd be a huge help to future > development (as it'd better clarify for developers what to watch out for as > well). I think it would require volunteer(s) interested in helping this > along to make a reality. > > If anyone is interested in this, let us know. Starting up a working group > is also easy to do, but it does take someone(s) willing to chair (or > co-chair) the working group efforts. > > Tim > > ________________________________ > From: Mark H. Wood,UL 0115A,+1 317 274 0749, on behalf of Mark H. Wood > Sent: Wednesday, May 13, 2020 7:09 AM > To: [email protected] > Subject: Re: [dspace-community] Re: Accessibility - version of WCAG > > 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<http://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 > . > > -- > 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/DM5PR2201MB11486E4CCE724EDA8A6409F0EDBF0%40DM5PR2201MB1148.namprd22.prod.outlook.com > < > https://groups.google.com/d/msgid/dspace-community/DM5PR2201MB11486E4CCE724EDA8A6409F0EDBF0%40DM5PR2201MB1148.namprd22.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/DM6PR05MB52914AE6D07D6BC59C426E4BD0BF0%40DM6PR05MB5291.namprd05.prod.outlook.com > . > -- 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/CAM5ifZ9YpKKZkjNHM0eTooRyaPjWxmdfpmJo_ob6Uqr9YdNS3Q%40mail.gmail.com.
