Dataverse accessibility and section 508 compliance

[fooba...@gmail.com]

Trying to launch a dataverse-based site for my organization, I was surprised to find that dataverse fails our accessibility scan. I went and scanned a search results page on Harvard Dataverse as a test case using https://accessibe.com/ and found that it also fails quite badly. Some examples of the problem are link tags containing no text or alt text, forms without names, and tables without th or role=presentation. Beyond being a beaurocratic obstacle, this means that dataverse sites are probably a real pain to use for visually impaired people with screen readers.

Is there any existing effort to make dataverse 508 compliant? I may be able to help with such an effort, or start one.

[Sebastian Karcher]

We've worked on this a fair bit -- you can find our repository at https://data.qdr.syr.edu/ and also see the remaining open issues here: https://github.com/QualitativeDataRepository/dataverse/issues?q=is%3Aissue+is%3Aopen+label%3Aaccessibility

I'm pretty sure all remaining issues are related to the primefaces framework and would be quite difficult to fix downstream, but we'd be happy for any additional thoughts. I think there's another post about this somewhere -- either here or on the dev list.

Sebastian

On Wed, Feb 23, 2022 at 1:24 PM fooba...@gmail.com <fooba...@gmail.com> wrote:

Trying to launch a dataverse-based site for my organization, I was surprised to find that dataverse fails our accessibility scan. I went and scanned a search results page on Harvard Dataverse as a test case using https://accessibe.com/ and found that it also fails quite badly. Some examples of the problem are link tags containing no text or alt text, forms without names, and tables without th or role=presentation. Beyond being a beaurocratic obstacle, this means that dataverse sites are probably a real pain to use for visually impaired people with screen readers.

Is there any existing effort to make dataverse 508 compliant? I may be able to help with such an effort, or start one.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/38a7092e-2657-4ae9-bc75-6c2abd8f4a8en%40googlegroups.com.

--

Sebastian Karcher, PhD
www.sebastiankarcher.com

[James Myers]

FWIW: Most of the QDR updates have been merged into the community version already and will be available in v5.10 when it is released this month. There’s another set of updates I haven’t yet made a pull request for, so they may not hit until v5.11. I do plan to do that soon. Anyone who’s interested in testing/further development could/should start from there.

 

-- Jim

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CAOSYSD5Si52nHK3c-FroW8easx1U-Aj1_f4GkM-VszRBOFRckA%40mail.gmail.com.