Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Most Prism presets are failing a11y color contrast checks
See original GitHub issueDescribe the bug
Many of the prism themes are failing the color contrast checks that are run by cypress-axe. Many of the themes are close or are meeting “AA Large” but because of the font size the contrast needs to be a minimum of “AA”.
So far I have checked (and fixed, see https://github.com/system-ui/theme-ui/pull/565):
- Dracula (failed)
- Duotone Dark (failed)
- Duotone Light (failed)
- Github (failed)
- Night Owl (failed)
- Night Owl Light (failed)
- Oceanic Next (passed)
To Reproduce
Run a11y checks on a site using Theme-UI and prism presets.
Expected behavior
Pass all a11y checks.
Screenshots
N/A
Additional context
N/A
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
My original PR up above had some fixed versions. It was pretty simple to just use your Colorable tool and tweak the contrast until it met cutoffs. That PR could be reopened and worked on.
There is also this which I found, but haven’t looked into:
https://openbase.io/js/a11y-syntax-highlighting
I don’t think we should wait on 1 based on the comments in the other issue 😕
I think we should fork the existing ones, make them have sufficient color contrast, and promote the forked more accessible ones in the docs. We can still provide the official ones in code, but I don’t think we should promote them in docs.