Okay, thanks for the thorough response! Since it's something we're very likely to adopt, I'll definitely spend some time filing issues. I can't really commit any time to doing anything beyond that, though I will poke at higher-ups and see if there's any interest in getting more involved. (DSpace is like 5% of my total workload since it's one of our most turnkey projects)
On Monday, June 17, 2019 at 12:35:17 AM UTC-7, Jeremy Echols wrote: > > Hi, I'm working with DSpace 6 and finding that remediation of > accessibility failures is a huge chore just for our theme alone (requiring > changes to core Java code and XSL files just to do things like add labels > to form fields). As we saw posts about accessibility in the past, we had > been hoping the situation would have improved for DSpace 7, but looking > over the demo site hosted by Atmire, it actually appears to have gotten > significantly worse. > > Is there a group dedicated to accessibility for DSpace 7? Should I be > filing tickets as I run into problems, or is the demo a very early > prototype? Are the core developers aware of the issues and simply haven't > yet dealt with them? Some issues are so trivial that it seems unlikely > that there's widespread awareness, but I know nothing of Angular or how the > core team operates, so maybe I'm jumping the gun here. > > Detailed problems are listed below. I found these in about fifteen > minutes, so this is far from an in-depth audit. Note that many of these > are WCAG level A -- which means, essentially, that they are critical > priority and block a large number of users from accessing the site. It > also means that under most jurisdictions, a university could be in legal > trouble if they stood up the site as it exists today. > > - The pages have no defined language, e.g., <html lang="en"> > - Over a dozen fields have no labels, particularly within the search > filter area > - There are images used as links which have no alt attribute (or other > alternative text) > - The search page's filters are tab-accessible, despite being visually > hidden, so keyboard focus just gets lost for several links > - There's no way I can figure out to open up the search filters with just > a keyboard without actually clicking one of the hidden links > - There's at least one misuse of aria, where an <a> tag is given a role of > "button", but its behavior isn't actually button behavior (spacebar doesn't > activate it, for instance) > - Some links have a title but no text. Depending on browser and screen > reader combination, a user may have no idea what's being presented. > - I can't figure out how to use the date slider with just a keyboard. > - There are dozens of instances of low-contrast text > -- 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 Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/02dfb5b2-5e8c-4c7d-9550-6327f413323e%40googlegroups.com.
