Repository navigation
a11y: check whether Starlight sites render markdown tables with display:block #4608
Description
#4605 replaces display: block on .prose table with a scrollable wrapper region. display: block on a <table> drops its implicit table role in Safari + VoiceOver.
The guides and api sites use Starlight and don't use .prose, so #4605 doesn't touch them. But a comment in web/packages/ui/src/styles/starlight-theme.css (around lines 174-177) says Starlight itself styles markdown tables with display: block; overflow: auto. If so, guides and api tables would have the same assistive-technology gap. That hasn't been verified against Starlight's shipped CSS.
To do:
- Check Starlight's rendered CSS for markdown tables on guides.wheels.dev.
- If it uses
display: block, wire the sharedrehype-table-scrollplugin from fix(web): wrap markdown tables in an accessible scroll region #4605 into the guides and apirehypePlugins, and override Starlight's table display. The api parameter tables already sit in their own.wd-params-tablewrapper.
Activity
bpamiri commentedon Oct 15, 2026
Related, for the same Starlight pass:
web/packages/ui/src/styles/starlight-theme.css(around lines 50-56) styles.sl-markdown-content :not(pre) > code, but sets no wrap rule. On phones, long inline code in guides and api pages can push the page wide, the same way #4609 does on the blog.overflow-wrap: anywhereto that Starlight inline-code rule, mirroring the.prose :not(pre) > codefix for web/blog: long inline code makes posts scroll sideways at phone width #4609.fix(web): restore table semantics on the guides and API sites (#4615)