Open jennybc opened 2 years ago
I'm going to try to do something about these:
use_bioc_badge()
I've reached out to Bioconductor and it looks like they can address it early in the new year.use_cran_badge()
already handled via METACRANuse_github_actions_badge()
request made; will use shields.io in a PRuse_lifecycle_badge()
usethis already writes a shields.io badge; request made for the lifecycle package to update its svgsusethis:::use_codecov_badge()
will use shields.io in a PRI'm not tackling these:
use_appveyor_badge()
use_circleci_badge()
use_travis_badge()
use_binder_badge()
This new article contains my analysis of where things stand:
https://usethis.r-lib.org/dev/articles/badge-accessibility.html
Since usethis is the package that adds a lot of badges to READMEs, maintainers have asked us to help make those badges more accessible to screen readers.
I suspect the best way to do this is via the badge SVGs themselves.
@gaborcsardi already added this to METACRAN's badges:
Any badge produced via https://shields.io/ is already accessible:
The features of https://shields.io/ badges mean we can often substitute an accessible badge, even if the "native" badge is not (e.g. for GitHub or Codecov). I am about to explore that idea further in a pull request.
I've already placed requests with the lifecycle package (https://github.com/r-lib/lifecycle/issues/117) and with GitHub Actions (community post, post in Actions and Packages Feedback).