You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 30 Next »

Date & Time

  • October 9th 15:00 UTC/GMT - 11:00 EDT

Zoom meeting:

We will be using the DSpace Zoom Meeting Room for our meeting.

Meeting location: https://duraspace.zoom.us/my/dspace  

Enter Meeting ID: 502 527 3040 , followed by #

Zoom information: DSpace Meeting Room


Meeting will be facilitated by Terry Brady

Agenda:

Accessibility in DSpace

Other Updates

  • Update on the new DSpace Documentation and Training Working Group

Preparing for the call

If you can join the call, or are willing to comment on the topics submitted via the meeting page, please add your name, institution, and repository URL to the Call Attendees section below.  

Meeting notes

Steve Fernie at Georgetown has worked on accessibility for their websites.  He shared some challenges:  

  • No alt-text on thumbnails. 
  • Lack of titles on iframes for embedded video.
  • Site-improve tool:  Automated testing for accessibility.  Repository is so large that the tool is having problems checking it all.  Working on ways to do this in smaller batches.
  • WCAG

Georgetown at least initially will use the item's title as Alt-text for the thumbnail.  Working on better ways to include context information instead of just title.  Customized theme uses dc.description.alt information instead of title when it's present in the record.  Information in this field can be added when the item is submitted.

VTech:  Hope that DSpace 7 will include this functionality (Marianne agreed).  DSpace 7 working group is hoping for guidance on accessibility needs of repositories. 

University of Arizona discussing how to reduce "noise" in the user experience.  Considering whether some accessibility choices make it harder for users to access the items.  Will be consulting with their accessibility resource center on campus.   Thinks that DCAT should look at tools that make this easier.  Also, many users come directly to the repository from Google Scholar, so how does that factor in to this?

Georgetown:  Some of this depends on the screen reader that people are using and what their goals are in accessing the content.   Thumbnails can encourage someone to open an item, but may not be needed for a person with a disability.   Often a difference between what WCAG reports and what each individual user wants out of the site. 

For video, we close-caption the videos on YouTube and provide links in the record.   We could download cc/transcript files and include them in DSpace records, but that can be a lot of extra work and it's not clear how useful that would be because DSpace doesn't provide a framework that pulls cc files and videos into a seamless user experience. 

VTech:  What if DSpace could be constructed with accessibility features such as skip-navigation so that users using screen readers could get more directly to the content.  

Question:  What is the timeframe for providing accessibility guidance?
Answer:  Getting good clear guidelines to the developers as soon as possible would be very much appreciated.  

Getting feedback from users would be an important.  Testing with real users

What standards are institutions adopting as a standard?   Those requirements would be helpful. Kate Dohe's institution is requiring WCAG 2 AA by 2020.  Our concern is accessibility to the content, but to what extent are DCAT participants involved with the submitters to the repository to increase accessibility from the user end? 

Arizona:  Broad interest to the repository community as a whole- Perhaps an opportunity to connect to other groups such as DLF or other repository platforms to see if there are existing best practices or if we could develop them together. 

Three parts to accessibility issues.  Of concern beyond the repository management community.  Others have to deal with the same issues. 

  • DSpace platform itself
  • Incoming content
  • Legacy content

Most helpful would be if DSpace as a system is WCAG compliant.   Develop a community of practice, too.  

Texas Digital Library is reviewing best practices now.   Interested in developments on the system side, since we can only control the incoming content. 

Very little control over the accessibility of ingested theses and dissertations.  Virginia Tech requires submission of ETDs in PDF/A.  Not enforced through ingest mechanism, but is required by Graduate School. 

Chat transcript:

From Terry Brady to Everyone:  10:00 AM
https://wiki.duraspace.org/display/cmtygp/DCAT+Meeting+October+2018

From Samuel to Everyone:  10:02 AM
I'm Samuel Willis from Wichita State University Libraries. I'm Technology Development Librarian and help the IR Librarian with DSpace.

From Kimberly A Chapman to Everyone:  10:03 AM
Sorry forgot I was still muted!

From keithg to Everyone:  10:18 AM
I’m wondering if there’s an appropriate way that we could get blind users (as an example) to give feedback on DSpace 7, given what Kimberly is saying.

From Samuel to Everyone:  10:19 AM
That is a good idea.

From Kimberly A Chapman to Everyone:  10:25 AM
I agree with the needs for testing with real users and getting their feedback

From Kate Dohe to Everyone:  10:27 AM
We are - all public sites by 2020

From Kimberly A Chapman to Everyone:  10:40 AM
Yes, there is an accessibility requirement - I don’t know the details but I will find out

From Samuel to Everyone:  10:40 AM
We are building on WCAG 2.0.

From Anne Lawrence to Everyone:  10:41 AM
We are aiming for WAG2 AA
I mean WCAG 2 AA

From nslindsey to Everyone:  10:41 AM
Same here, we have an accessibility requirement. I'm not sure what the institution is aiming for, but I'm thinking it's probably the same as what others have mentioned here.

From Kimberly A Chapman to Everyone:  10:54 AM
I agree, I think determining what the requirements are and ensuirng the software is compliant is the first goal

From Kate Dohe to Everyone:  10:57 AM
this is our GA’s work from a couple years ago: http://hdl.handle.net/1903/18917
I know there is more data but we may have stored it internally; I’ll ask our IR manager.

From Felicity Dykas to Everyone:  11:00 AM
Great meeting!
From Samuel to Everyone:  11:00 AM
Okay, thank you all. Can someone add me to the attendance?

From Lisa Spiro (Rice) to Everyone:  11:00 AM
Thanks!

From nslindsey to Everyone:  11:00 AM
Thanks! Take care.


Call Attendees

  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.