My personal analysis after a few keyboard & screen reader tests.

Anja Petry

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

A review of the accessibility of shadcn/ui Charts reveals multiple critical issues. Claims of 'screen reader support' are found to be false, with no data presented to screen readers during navigation. The documentation lacks details on expected keyboard and screen reader interactions, undermining the library's accessibility claims. The review stresses the importance of genuinely addressing accessibility features in popular libraries, emphasizing that current claims appear performative and do not inspire trust.

A Quick-ish Accessibility Review: shadcn/ui Charts

Great review. I completely agree with the following point:
<blockquote>
Since charts are an “advanced” accessibility topic, many likely don’t know how to verify the claim.
</blockquote>
Many developers today don’t fully understand a11y or how to test with screen readers. This is a problem because web accessibility laws are getting stricter. UI libraries should be built or at least documented in a way that helps developers make sure their projects are accessible.

Which screen reader did you use for testing?
Also, can you recommend some libraries that have accessible charts? I’d love to see how they handle accessibility.