DAAF-Contribution-Community/daaf / .claude/skills/science-communication
science-communication
VerifiedTranslating technical findings for non-technical audiences. Narrative frameworks (Pyramid Principle, SCQA), plain-language translation, executive summaries, policy briefs, causal language. Use when presenting to stakeholders or reviewing deliverables
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.0 KB |
| references/accessibility-equity.md | markdown | 19.3 KB |
| references/audience-analysis.md | markdown | 16.5 KB |
| references/communication-review.md | markdown | 16.8 KB |
| references/deliverable-templates.md | markdown | 19.8 KB |
| references/narrative-frameworks.md | markdown | 19.4 KB |
| references/plain-language.md | markdown | 30.3 KB |
references/accessibility-equity.md
View on GitHub# Accessibility and Equity in Data Communication
Standards and guidance for ensuring that data communication is accessible to all audiences and equitable in how it frames findings about people. This reference covers two intertwined concerns: **accessibility** (can everyone perceive and understand the communication?) and **equity** (does the communication respect and accurately represent the people in the data?).
This file focuses on communication-level accessibility and equity framing. For chart construction standards (color palettes, encoding hierarchy, export specifications), see the data-scientist visualization references. For audience-specific adaptation, see `audience-analysis.md`.
## WCAG Compliance for Data Communication
Web Content Accessibility Guidelines (WCAG) 2.1 establish the baseline standards for accessible data presentation. Even for non-web deliverables (PDFs, presentations, printed reports), WCAG principles provide a useful framework.
### Contrast Requirements
| Element Type | WCAG Criterion | Minimum Ratio | Applies To |
|--------------|---------------|---------------|------------|
| Text (standard) | 1.4.3 (Level AA) | 4.5:1 | Axis labels, tick marks, titles, legends, annotations, source notes |
| Text (large, ≥18pt or ≥14pt bold) | 1.4.3 (Level AA) | 3:1 | Chart titles, large annotations |
| Graphical objects | 1.4.11 (Level AA) | 3:1 | Bars, lines, data points, pie segments, area fills — measured against adjacent/neighboring colors |
| Interactive states | 1.4.11 (Level AA) | 3:1 | Hover, focus, and selection states each require their own contrast pass |
**Practical tips:**
- Adjacent bars in a bar chart each need 3:1 contrast against the background; separating bars with white space simplifies compliance
- Pie chart segments can use a contrasting border between adjacent slices
- Light gray gridlines on white backgrounds often fail contrast requirements — check with a contrast checker tool
### Non-Text Content (WCAG 1.1.1)
Every chart or data visualization must have a text alternative. The approach depends on complexity:
| Chart Complexity | Recommended Approach |
|------------------|---------------------|
| Simple chart (single message) | Concise alt text describing the finding, not just the chart type: "Bar chart showing that literacy programs produced 14-point gains vs. 5-point gains for class-size reduction" |
| Multi-series or comparative | Short alt text + adjacent prose summary of key takeaways |
| Complex/interactive visualization | `aria-describedby` linking to full description + data table |
**Writing effective alt text for charts:**
- State what the chart shows AND what the key finding is
- Not: "Bar chart of graduation rates" (says the type but not the finding)
- Better: "Bar chart showing graduation rates by selectivity tier; highly selective institutions graduate 89% vs. 42% at open-access institutions"
- For published documents, the UK Government Analysis Function recommends marking the chart image as decorative (empty alt) and placing the meaningful description in adjacent body text — this serves both screen reader users and sighted readers
### Color-Alone Encoding Prohibition (WCAG 1.4.1)
Color must never be the sole means of conveying information. Every use of color must be paired with at least one redundant encoding:
| Chart Type | Color-Alone Failure | Accessible Alternative |
|------------|---------------------|----------------------|
| Bar chart | Different colored bars with color-key legend only | Direct labels on bars, or pattern fills in addition to color |
| Line chart | Multiple colored lines distinguished only by color | Different line styles (solid, dashed, dotted) + markers (circle, square, triangle) + direct labels |
| Pie chart | Segments distinguished only by fill color | Direct labels on each segment |
| Scatter plot | Groups distinguished only by dot color | Different shapes for each group + direct labels |
| Any chart | Color-matched legend as the only identifier | Direct labeling eliminates the need for color matching entirely |
**The golden rule:** Never rely on color alone. Always pair color with shape, pattern, line style, direct label, or position.
### Multi-Format Presentation Strategy
The evidence-based approach is to present data through multiple concurrent formats:
1. **Visual chart** — for at-a-glance pattern recognition
2. **Prose summary** — immediately adjacent, stating the headline finding in plain language
3. **Data table** — for precise values, screen readers, and independent verification
4. **Accessible download** — Excel/ODS file for further analysis (when applicable)
This strategy simultaneously satisfies WCAG requirements, serves diverse user needs, and extends the IES advice to "Lead with the headline" (Miller & Piver-Renna, 2022) to both visual and text form.
### Screen Reader Considerations
When data tables accompany charts:
- Use semantic HTML: `<table>`, `<th>` with `scope` attributes, `<caption>` elements
- Ensure header-to-cell relationships are programmatically determinable
- For downloadable tables, provide Excel or ODS files with clear link text stating file type and content
- SVG format for chart images retains clarity at high zoom levels and can embed accessible text
### Accessible Chart Type Selection
Based on the UK Government Analysis Function checklist:
| Chart Type | Accessibility Notes |
|------------|-------------------|
| **Bar charts** | Most accessible when bars are sorted by value, gap between bars is narrower than bar width, axis starts at zero, direct value labels used |
| **Line charts** | Accessible when limited to 4 lines maximum, lines directly labeled at endpoints, different line styles and markers supplement color |
| **Pie/donut charts** | Use sparingly — maximum 5 categories, segments directly labeled, ranked from 12 o'clock by size |
| **Small multiples** | Preferred over complex multi-series charts — require identical axes across panels |
| **3D charts** | Avoid entirely — add no information and harm all users |
---
## People-First Language
Default to language that foregrounds personhood, then describes characteristics. This is not political correctness — it is precision. "Students experiencing poverty" conveys something different from "poor students": the former describes a circumstance; the latter defines an identity.
### General Principles
| Instead Of | Use | Why |
|------------|-----|-----|
| The poor, the homeless, the disabled | People experiencing poverty, people without housing, people with disabilities | Person first, condition second |
| Inmates, offenders, convicts | People in prison, incarcerated people, people with criminal convictions | "Inmate" defines people by their punishment |
| Minorities | Communities of color, specific group names | "Minority" implies lesser status; also increasingly inaccurate demographically |
| The elderly, seniors | Older adults | Avoids reductive categorization |
| Illegals, illegal immigrants | Undocumented immigrants, undocumented residents | People are not "illegal" — actions may be |
| Dropouts | Students who left school, students who did not complete | "Dropout" implies choice and blame |
| At-risk youth | Young people facing systemic barriers | "At-risk" locates the problem in the person, not the system |
| Blacks, Whites (as nouns) | Black people, White people | Use as adjectives, not nouns, as AMA style directs — people first. Capitalize racial and ethnic group names, including White, per APA 7 and AMA style |
| Diabetics, asthmatics | People with diabetes, people with asthma | Condition modifies the person, not the other way around |
### Nuance: Identity-First Language
People-first language is the default, but some communities prefer identity-first language. Many autistic adults prefer "autistic person" over "person with autism." Many Deaf community members prefer "Deaf" as an identity marker. The consistent principle across all groups: **talk with the communities you are studying to understand their preferred terminology**, rather than imposing a universal rule.
### Evolving Terminology
Language evolves continuously. Some notes on current usage in research contexts:
- **Hispanic/Latino/Latina/Latinx/Latine:** A Pew Research Center survey of U.S. Hispanic adults (December 2019, published 2020) found that 23% had heard of "Latinx" and 3% used it to describe themselves (Noé-Bustamante, Mora, & Lopez, 2020). "Latine" is an emerging alternative. When survey data use one term, you may use updated language in your communication if explicitly noted. When uncertain, use the term the community uses most widely in your context.
- **BIPOC:** Useful as shorthand but can obscure meaningful differences between the groups it aggregates. Prefer specific group names when the analysis supports disaggregation.
- **Gender language:** Many major surveys still offer only "male/female." When such groups are absent from data, call it out explicitly: "This survey did not offer nonbinary response options."
---
## Urban Institute Do No Harm Principles
The Urban Institute's "Do No Harm Guide: Applying Equity Awareness in Data Visualization" (Schwabish & Feng, 2021) provides a comprehensive framework for equity-aware data communication. Its recurring diagnostic question, from journalist Kim Bui, is: *"If I were one of the data points on this visualization, would I feel offended?"*
### Core Principles
1. **Put people first.** Data reflect real lives. As Jacob Harris wrote: "If your data is about people, make it extremely clear who they are or were."
2. **Critically examine the data before visualizing.** Applying equity thinking to a visualization will not fix inherently biased underlying data. Ask: How were these data generated? Who is included and excluded? Whose voices are missing?
3. **Name forces of oppression directly.** Titles and annotations are prime real estate for naming racism, sexism, and structural discrimination — don't bury these forces in body text or leave them for the reader to infer.
4. **Frame around systems, not deficits.** The guide warns that charts comparing every group with the best-performing one can invite a "deficit-based perspective", and it shows D'Ignazio and Klein retitling a jail chart to name the force at work ("Racism in Jail: People of color less likely to get mental health diagnosis"). DAAF example: "Schools suspend Black students at 3x the rate" names the actor; "Black students are suspended at 3x the rate" does not. The guide notes that a deficit reading is less likely when enough historical context is given.
5. **Question default comparison groups.** Major US surveys (the decennial census, the Current Population Survey, the Federal Reserve's Survey of Consumer Finances, and Michigan's Panel Study of Income Dynamics) list "White" first and code it "1" (Schwabish & Feng, 2021). This causes analysts to default to White as the comparison baseline — not by active choice, but by data structure. Consider: if your study focuses on a particular community, present that group first. Sort by the variable of interest, not by dataset order.
6. **Be thoughtful about aggregation.** Combining racial or ethnic subgroups into broad categories can mask critical variation. Aggregated "Asian or Pacific Islander" poverty rates hide a range from 4.5% (people identifying as both Chinese and Japanese) to 27.8% (Mongolian) across detailed subgroups in the 2019 American Community Survey (Schwabish & Feng, 2021). When you must aggregate, note what is hidden.
7. **Acknowledge absent groups.** When data exist for a group but sample sizes are too small, say so explicitly rather than silently omitting the group. Transparency about absence is better than invisible exclusion.
### Stereotype-Aware Color Choices
| Avoid | Why | Alternative |
|-------|-----|-------------|
| Pink for women, blue for men | Reinforces gender stereotypes | Use distinct non-gendered hues from a qualitative palette |
| Colors matching skin tones for racial groups | Associates identity with color in a literal, reductive way | Use the Okabe-Ito or ColorBrewer qualitative palette |
| Graduated/sequential palette for demographic categories | Implies hierarchy or ranking among groups (e.g., darker = worse) | Use distinct categorical colors — each group gets an independent color, not a shade |
| Red for groups receiving services or experiencing disadvantage | Red carries "threat" and "danger" connotations — can frame affected communities as problems | Use neutral colors; reserve red for emphasis only when the thing being emphasized is genuinely alarming |
### Ordering Data Purposefully
The order in which demographic groups appear in charts and tables communicates values:
- **Do not default to dataset order.** Raw data ordering inherits historical biases (White first, male first).
- **Consider your study's focus.** If your analysis centers a particular community, present that group first.
- **Sort by the variable of interest** when there is a natural ordering (e.g., by magnitude of the result).
- **Alphabetical order** is a neutral default when no other ordering is justified.
- **Interactive selection** (when the medium allows it) lets readers choose their own comparison group, avoiding any static hierarchy.
### Titles as Equity Instruments
Titles are among the first things readers scan. They present an opportunity to frame the narrative:
| Deficit Framing | Systems Framing |
|-----------------|-----------------|
| "Black Students Underperform in Math" | "Math Achievement Gaps Reflect Decades of Unequal Investment" |
| "Low-Income Families Struggle to Access Care" | "Healthcare Systems Fail Low-Income Communities" |
| "Minority Students Drop Out at Higher Rates" | "Schools Retain White Students at Higher Rates Than Students of Color" |
Systems framing is often the more accurate choice, because outcomes are produced by systems, not only by the characteristics of affected people; give enough historical context that readers do not read gaps as deficits of the group.
### Do No Harm Checklist
Before finalizing any deliverable containing demographic data:
- [ ] Has the team communicated with the people/communities represented in the data?
- [ ] Does the team understand the data's sourcing, inclusion/exclusion criteria, and who benefits or is harmed?
- [ ] Have words, phrases, and labels been carefully reviewed for people-first language?
- [ ] Have colors been chosen to avoid stereotypes and meet accessibility standards?
- [ ] Has the ordering of groups in charts and tables been considered deliberately (not defaulting to dataset order)?
- [ ] Have alternatives to "Other" been considered? ("Other" literally others individuals)
- [ ] Have all icons and images been reviewed with an equity lens?
- [ ] Would alternative chart types better serve the data and the communities represented?
- [ ] Does the framing locate problems in systems rather than in affected communities? (DAAF addition; not in the guide's checklist)
- [ ] Does the final product meet the needs of its audience, including members of the communities studied?
---
## Colorblind-Safe Communication Design
Inherited red-green color vision deficiency affects about 8% of men and 0.4% of women of European ancestry, and 4-6.5% of Chinese and Japanese men (Birch, 2012). The data-scientist visualization references cover color palette selection and redundant encoding in detail. This section covers the **communication-level** considerations that go beyond chart construction.
### Communication-Level Principles
1. **Never describe findings using color alone.** "The red line shows..." fails if the reader cannot distinguish red. Use: "The dashed line (labeled 'District A') shows..."
2. **Reference chart elements by label or position, not color.** In narrative text accompanying a chart: "The top bar (high-poverty districts) shows..." not "The dark blue bar shows..."
3. **Test all deliverables in grayscale.** Print or display in black and white. If any information is lost, the design relies too heavily on hue.
4. **Provide data tables alongside every chart.** Tables are inherently colorblind-accessible — the information is in the numbers, not the colors.
5. **In presentations, describe visual elements verbally.** "You can see in the chart that the solid line — representing literacy programs — rises steeply while the dashed line — class-size reduction — remains flat." This also benefits audience members with visual impairments.
---
## Comprehensive Accessibility Review Checklist
Apply before releasing any deliverable:
### Content Accessibility
- [ ] All charts have text alternatives (alt text or adjacent prose descriptions)
- [ ] Data tables accompany complex visualizations
- [ ] Text contrast meets 4.5:1 minimum (standard text) or 3:1 (large text)
- [ ] No information is conveyed by color alone — redundant encoding is present
- [ ] Chart elements are referenced by label/position in narrative text, not by color
- [ ] Font is sans-serif, minimum 12pt (print) or 11px (screen)
- [ ] Reading level is appropriate for the target audience
### Structural Accessibility
- [ ] Document has proper heading hierarchy (H1 → H2 → H3, no skipped levels)
- [ ] Tables use proper header markup
- [ ] Links have descriptive text ("View the full dataset" not "click here")
- [ ] Document is navigable by keyboard (for digital deliverables)
### Equity Review
- [ ] People-first language used throughout
- [ ] Demographic groups named respectfully and specifically
- [ ] Default comparison group considered deliberately
- [ ] Aggregation does not mask meaningful subgroup variation
- [ ] Absent groups acknowledged rather than silently excluded
- [ ] Framing locates problems in systems, not in affected communities
- [ ] Color choices avoid demographic stereotypes
- [ ] Group ordering reflects the analysis purpose, not dataset defaults
## References and Further Reading
Schwabish, J., & Feng, A. (2021, June 9). *Do No Harm Guide: Applying Equity Awareness in Data Visualization*. Urban Institute. https://www.urban.org/research/publication/do-no-harm-guide-applying-equity-awareness-data-visualization
Birch, J. (2012). "Worldwide prevalence of red-green color deficiency." *Journal of the Optical Society of America A*, 29(3), 313. https://doi.org/10.1364/josaa.29.000313
Noé-Bustamante, L., Mora, L., & Lopez, M. H. (2020, August 11). "About One-in-Four U.S. Hispanics Have Heard of Latinx, but Just 3% Use It." Pew Research Center. https://www.pewresearch.org/race-and-ethnicity/2020/08/11/about-one-in-four-u-s-hispanics-have-heard-of-latinx-but-just-3-use-it/
Miller, L. C., & Piver-Renna, J. (2022, October 27). "Six strategies for effectively communicating research findings to decision makers." Institute of Education Sciences. https://ies.ed.gov/learn/blog/six-strategies-effectively-communicating-research-findings-decision-makers
Urban Institute. "Data Visualization Style Guide." https://urbaninstitute.github.io/graphics-styleguide/
WCAG 2.1. W3C Recommendation. https://www.w3.org/TR/WCAG21/
UK Government Analysis Function. "Accessible Charts: A Checklist of the Basics." https://analysisfunction.civilservice.gov.uk/policy-store/charts-a-checklist/
Elavsky, F. "Chartability." https://chartability.fizz.studio/
Schwabish, J. (2021). *Better Data Visualizations: A Guide for Scholars, Researchers, and Wonks*. Columbia University Press.
Tufte, E.R. (1983). *The Visual Display of Quantitative Information*. Graphics Press.
D'Ignazio, C. and Klein, L.F. (2020). *Data Feminism*. MIT Press. https://datafeminism.io/
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |