a11y issues - contrast about markdown-badges HOT 7 CLOSED

It was easier just to write an automated way to do the whole thing. Thanks for the inspiration! Check out the limitations section though... Nothing we can do about the text in many cases, until it's fixed on their end.

https://github.com/ctcpip/a11y-markdown-badges

from markdown-badges.

Hey @ctcpip , we do not have any guidelines to meet a11y requirements. If you do find any errors, you can create a Pull Request and I would gladly merge it.

@Ileriayo can we think of any pre-commit hook/action that can check for these guidelines? It can be easily managed then.

from markdown-badges.

@mehtaAnsh - I've been busy... check out a11y badges -- and my readme for a full demo. thanks again for the inspiration!

from markdown-badges.

FWIW, I did spend some time writing a parser to extract each fg and bg color and check the contrast ratio, and output any that did not meet the requirement. However, due to inconsistencies and lack of uniformity, it became clear it would need to handle all these edge cases.

To move forward, I would have to first write a general validator for each entry, fix the anomalies by updating the readme, and then could run it through the contract check parser. Ideally, both of these tasks would be part of either a pre-commit hook, or an action required to pass in order to merge. (But only after fixing all the existing issues first, or it would never pass.)

from markdown-badges.

That's a great way to implement. We can have something similar like this here in the form of a pre-commit hook.

from markdown-badges.

The implementation looks great. Can't think of any way to integrate this with this repository as of now. Great work!

from markdown-badges.

closing in favor of a11y-markdown-badges / a11y-badges

from markdown-badges.