Accessibility in Scientific Tools Goes Beyond WCAG

Accessibility in research software has a dimension that standard WCAG checklists don't fully capture. Yes, we owe expert users with disabilities the same compliant baseline as anyone — keyboard navigation, contrast, screen-reader semantics. But scientific tooling layers on industry-specific accessibility challenges that I flag to engineering leaders early. Data visualizations are the obvious one: a chart that encodes meaning only through color fails a colorblind researcher and, often, fails everyone when printed or projected. So I insist on redundant encoding — shape, pattern, direct labeling — and on accessible data tables behind every visualization, which conveniently also serves power users who want the raw numbers. Then there's the harder problem of dense, data-heavy interfaces. A virtualized table of a hundred thousand rows can be a screen-reader nightmare if focus management and ARIA live regions aren't handled deliberately. Keyboard-driven querying matters enormously to expert users who never touch a mouse. My message to CTOs is that in this domain, accessibility and power-user design are the same investment — both demand structured, navigable, non-visual access to complex data. Build it once, and you serve disabled researchers and your most demanding experts in a single stroke.