-
Notifications
You must be signed in to change notification settings - Fork 40
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
badge accessibility effort #133
Comments
additional discussion: community/community#8974 |
@jennybc so was the suggested change on the mailing list to add into all the Bioconductor badges on landing pages a |
I feel like it's not yet clear exactly what the right combination of badge change + badge usage change is. I'm waiting for more progress in community/community#8974. |
okay. please keep us posted. short version: we downloaded templates (so probably older without this information) from shield.io and then use the templates to make all the badges on package landing pages. We do it this way instead of interactively with shield.io because we were hitting limits due to how many packages we have and that many badges were being regenerated nightly or weekly (and would get pinged by maintainers if not updated frequently). We keep the badges in svg so to make updates to them to include any relevant information would not be difficult, I just need to know what should be added. |
I'm assuming / hoping that GitHub has more accessibility firepower than the tidyverse team or bioconductor does and that they will show us the way re: features the badge SVG should have. And will also give example markdown and HTML for badge inclusion in READMEs and the like. If the GitHub effort doesn't progress on a reasonable time scale, we'll have to see if we can make progress ourselves. |
can we adopt suggestions at https://usethis.r-lib.org/dev/articles/badge-accessibility.html
The text was updated successfully, but these errors were encountered: