I expect tests to always be passing before merging anything.
pypi metadata has the list of supported python versions, in text format
A link to your documentation? Ok but why can't it be a regular link?
I use forums or IRC, so the online users on whatever aren't super meaningful to me personally.
We will look into this, I think the info is still important to show but there probably is a better more inclusive way of doing it.
What, specifically, is the issue with the badges concerning accessibility? Most badges I see can be reduced to a div containing two spans and some text, which should be usable with a screen reader. Is there missing alt text, aria attributes, etc?
Re: tests, it comes down to developer culture. It may be acceptable for experimental or alpha/beta versions to not pass tests, live on a separate branch, etc. Distros should be live-testing any packages they ship, too; upstream releases aren't guaranteed to be tested, depending on the upstream you're working with. It's nice to know that the latest commit is actually working without having to double check CI locally. However, tests also aren't created equally. The project author(s) could be learning how to refine their tests, and not actually trust the CI's results (yet).
Can we argue that's sloppy, or that they should've never done that before merging and pushing? Sure. Not sure where it gets us. Actionable feedback and cautionary advice is useful, though.
If a test is not working/outdated, remove or fix the test. It's not what the badge is showing anyway.