Personally a lot of this a11y stuff is complicated and confusing to me. I am trying my best to be a responsible dev, but it feels overwhelming sometimes.
Personally a lot of this a11y stuff is complicated and confusing to me. I am trying my best to be a responsible dev, but it feels overwhelming sometimes.
I quite dislike this post because my impression is that it just boils down to "no option is adequate to me, and I'm unwilling to present an alternative".
Well, it's a blog about software accessibility...
If you just go down the checklist and do what you can, you'll be way ahead of most websites: https://webaim.org/standards/wcag/checklist
Microsoft also has a great interactive test that can probe your website for you and highlight issues: https://accessibilityinsights.io/
I think similar but less powerful checks are also built into some IDEs (Jetbrains) and linters (Eslint).
Edit: I am a sighted user with color vision. I can't promise these fixes are enough to make your site super accessible, but it's a lot better than nothing!