accessibility-and-inclusive-visualization

name	accessibility-and-inclusive-visualization
description	Make data visualizations accessible and inclusive. Use when the user needs chart or diagram accessibility guidance, text alternatives for complex visuals, color and contrast review, keyboard support, reduced-motion behavior for animation or parallax, or an accessibility QA workflow for exported figures, UML-like diagrams, and dashboards.

Accessibility and Inclusive Visualization

Overview

Use this skill when a visualization must be understandable by more people, in more contexts, with more assistive needs. Accessibility is not a post-processing step. It shapes chart selection, color, labeling, interaction, fallback text, and export strategy.

Default assumption: every important visualization should have a non-visual path to the key insight, whether through surrounding text, direct labels, data tables, or formal text alternatives.

Working Pattern

1. Identify whether the chart is exploratory, explanatory, interactive, or exported.
2. Decide which information must remain available without hover, color discrimination, pointer precision, expanded panels, private persisted state, permission-gated capabilities, or a strong connection.
3. If the story uses generated imagery, illustration, WebGL, particles, 3D, maps, scrollytelling, parallax, or animation, separate what the asset shows from what the data proves.
4. If Codex image generation was used for a layout, figure, page-integration, asset, or key-frame concept, verify that the large-screen and mobile concept images were shown with concise plan and interaction bullets, the user approved the generated design set before project changes or implementation code began, and the semantic design contract from references/foundations/meaning-preserving-visual-design-workflow.md exists: the accessible path must preserve the same claim, caveat, source context, evidence hierarchy, locked layout elements, mobile continuation, and interaction meaning as the visual design.
5. If the view is a UML-like, ERD, state machine, workflow, dependency, or architecture diagram, preserve a text outline of nodes, groups, relationships, and selected paths; use ../uml-and-software-architecture-visualization/SKILL.md for diagram-specific semantics.
6. Use references/foundations/mobile-first-responsive-visualization.md to verify touch targets, drag alternatives, keyboard-open visual viewport behavior, main-visualization visibility, spotty-connection states, and fallbacks for AR, camera, motion, vibration, notifications, and geolocation.
7. Provide direct labels, strong contrast, redundant encodings, keyboard paths, reduced-motion alternatives, accessible disclosure controls, and text alternatives.
8. For interactive visualizations, check that shared URLs, saved views, refresh, and back/forward navigation preserve the same accessible state summaries as the visual surface.
9. Test both the chart or diagram and the surrounding narrative.

Output Expectations

• Name the accessibility risks specific to the chart, not just generic WCAG items.
• Provide fallback strategies for screen readers, PDFs, and static exports.
• Explain what to keep visible without relying on hover or color alone.
• Explain which active filters, selections, caveats, and summary values remain visible when configuration or drill-down panels are collapsed.
• For color guidance, name the semantic color roles, contrast risks, redundant encodings, and grayscale or color-deficiency review path.
• For image-supported visual stories, provide alt text or long descriptions that cover the scene, the data layer, the main takeaway, and the caveat without overstating generated imagery.
• For concepted visualizations, make sure the user approval record exists and the long description, reduced-motion path, static export, and source/caveat text preserve the approved semantic design contract and locked concept elements, not just the final rendered pixels.
• For mobile visualizations, make sure the main evidence is not pushed below settings, touch targets and hit areas are large enough, drag has alternatives, hover has tap/focus equivalents, keyboard-open states remain operable, stale/offline states are named, and sensor/camera/notification features have non-permission fallbacks.
• For animation, specify reduced-motion behavior and key-frame or final-state fallback.
• For scrollytelling or parallax, preserve native scroll and keyboard behavior, specify static key frames or stacked fallback, and make sure motion can be disabled without losing the evidence.
• For WebGL or particle effects, describe the data meaning in text, expose keyboard-accessible focus or selection paths for important marks, and provide a non-animated fallback that preserves flow, direction, focus, and uncertainty.
• For interactive diagrams, make search, selection, details panels, reset, export, expand/collapse, and drill-down reachable without pointer-only interaction.
• For shareable visualizations, make copy-link, saved-view, reset, expanded/collapsed panels, and restored URL state reachable and understandable by keyboard and screen-reader users.

References

• Shared theory:
  • references/foundations/perception-color-and-encoding.md
  • references/foundations/storytelling-annotation-and-critique.md
  • references/foundations/meaning-preserving-visual-design-workflow.md
  • references/foundations/mobile-first-responsive-visualization.md
• Skill references:
  • ./references/text-alternatives-and-complex-images.md
  • ./references/color-contrast-and-redundant-encoding.md
  • ./references/keyboard-screen-reader-and-export.md
  • ./references/testing-and-review-workflow.md
  • ../uml-and-software-architecture-visualization/SKILL.md
  • ../scrollytelling-and-parallax-data-visualization/references/accessibility-testing-and-review.md

Representative Prompts

• "Make this chart accessible."
• "How should I write alt text or a long description for this visualization?"
• "Review this dashboard for color, keyboard, and screen-reader issues."
• "What needs to change before this chart goes into a PDF report?"
• "How do I design tooltips and hover interactions without excluding people?"
• "Make this parallax scrollytelling visualization safe for reduced-motion users."
• "Make this UML, ERD, workflow, state machine, or architecture diagram accessible."