Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Screen reader challenges on bioconductor.org site #304

Open
seandavi opened this issue Feb 12, 2025 · 10 comments
Open

Screen reader challenges on bioconductor.org site #304

seandavi opened this issue Feb 12, 2025 · 10 comments

Comments

@seandavi
Copy link

From the support site:

Hi! Thanks for all the work on an organized and useful website. I've found biocViews like this one https://bioconductor.org/packages/release/BiocViews.html#___ExperimentData produce tables that are inaccessible with a screen reader. I've tested on Mac with Safari and Chrome. The screen reader sees that there is a table and it produces a description of the number of rows and columns but it cannot read the contents.

@HenrikBengtsson
Copy link

Is there a way to "reproduce" these finding programmatically? Are the tools and validators that pick up this particular problem?

@seandavi
Copy link
Author

Good question. There are some tools for general 508-compliance, but my sense is that screen reader testing is still done somewhat manually.

Because parts of the website are rendered dynamically (ie., the site does not have content when using something like curl or other headless tools), there are additional challenges to automated testing.

Finally, I'm not clear that it is possible to build a feature-complete version of the website locally for testing purposes. That might be a question for TAB at some point.

@LiNk-NY
Copy link
Contributor

LiNk-NY commented Feb 13, 2025

I took a stab at this in PR #305. Your feeback is welcome.
FWIW, I was not able to test these changes in the provided
container as these tables are rendered dynamically.

@LizHareDogs
Copy link

Hi! Thanks @seandavi for making this an issue-- I've been meaning to do it for a couple of weeks and here it's already done! I'm the screen reader user who finds the tables to be empty. So thanks to everyone contributing to this discussion.

There are automated accessibility checkers but they vary in their effectiveness. Does anyone have advice about what particular web software we're looking to test?
Thanks again everyone.

@lshep lshep closed this as completed in b3360ce Feb 19, 2025
@lshep
Copy link
Contributor

lshep commented Feb 19, 2025

I'll monitor to make sure the next autobuild of the website works correctly and gets pushed forward; after which we will need to test

@seandavi
Copy link
Author

@lshep could we leave this open until we have @LizHareDogs confirm what works and what doesn't? When should she check the site?

@lshep lshep reopened this Feb 19, 2025
@lshep
Copy link
Contributor

lshep commented Feb 19, 2025

sure. marcel had added the issue to the PR so it auto closed

@lshep
Copy link
Contributor

lshep commented Feb 19, 2025

the site should have regenerated and propagated so should be good to test

@LiNk-NY
Copy link
Contributor

LiNk-NY commented Feb 19, 2025

The changes seem to work based on my cursory testing with orca on Ubuntu. It reads the cell contents when I click into the cell. Your feedback is appreciated, @LizHareDogs. Thanks!

@LizHareDogs
Copy link

LizHareDogs commented Feb 26, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants