...
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.
...
Very little control over the accessibility of ingested theses and dissertations.
One university 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 and 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
- Terrence W Brady (Georgetown University Library)
- Keith Gilbertson (University Libraries, Virginia Tech)
- Kimberly Chapman (University of Arizona Libraries)
- Marianne Reed (University of Kansas Libraries)
- Claudio Cortese (4Science)
- Suzanne Chase (Georgetown University Library)
- Anne Lawrence (University Libraries, Virginia Tech)
- Pauline Ward University of Edinburgh