Project Enquiry

Published on

February 12, 2026

Impact Measurement Visualisation for Nonprofit Websites

View all Insights

I recently reviewed a charity website featuring a prominent "Our Impact" page with a single infographic—beautiful design, comprehensive data, completely inaccessible to screen reader users.

When I asked about accessibility, the Communications Director said: "But we made it visual specifically so people could understand the impact quickly."

The organisation had created barrier preventing blind and low-vision stakeholders from accessing the very impact evidence proving their effectiveness—whilst simultaneously claiming commitment to inclusion.

The problem wasn't the visualisation itself. It was treating data accessibility and visual design as competing priorities rather than complementary requirements.

Through my nonprofit work building 100+ websites, I've learned that impact measurement visualisation serves legitimate communication needs—making complex outcomes data understandable, engaging stakeholders emotionally, demonstrating effectiveness efficiently—but only when accessibility is architectural requirement rather than afterthought consideration.

Why Impact Visualisation Often Excludes Stakeholders

Nonprofits invest significant resources in impact measurement: defining outcomes, collecting data, analysing results, demonstrating effectiveness. Then they present findings through visualisations that exclude substantial portions of their stakeholder audience.

The common visualisation failures I see:

Failure 1: Image-Only Infographics

What organisations create: Comprehensive infographic showing outcomes data, programme reach, beneficiary demographics, effectiveness evidence—all in single beautiful visual.

Who this excludes:

  • Screen reader users (can't access information in images)
  • Low-vision users (can't enlarge or reformat fixed images)
  • Cognitive disability users (can't process dense visual information)
  • Mobile users (can't read small text in images)

The accessibility violation: No alternative text describing data. No HTML equivalent providing same information. Impact evidence completely unavailable to substantial stakeholder segment.

Why organisations do this: "We want impact to be visually engaging" without understanding that accessibility and visual design are complementary, not competing.

Failure 2: Colour-Dependent Data Presentation

What organisations create: Charts using colour to convey meaning—red vs. green for outcomes, colour-coded categories, heat maps showing intensity through colour gradients.

Who this excludes:

  • Colour-blind users (approximately 8% of men, 0.5% of women—can't distinguish colour-coded information)
  • Screen reader users (colour information not conveyed in alternative text)
  • Print users (colour distinctions disappear in black-and-white printing)

The accessibility violation: Information conveyed solely through colour without redundant encoding (patterns, labels, position).

Why organisations do this:Standard data visualisation tools default to colour-dependent presentation without accessibility consideration.

Failure 3: Complex Interactive Charts Without Keyboard Access

What organisations create: Interactive data visualisations requiring mouse hover to reveal details, click interactions to filter data, drag gestures to explore outcomes.

Who this excludes:

  • Keyboard-only users (can't access mouse-dependent interactions)
  • Screen reader users (can't perceive visual-only state changes)
  • Touch-screen users without fine motor control (can't execute precise gestures)
  • Users with tremors or motor disabilities (can't perform mouse-dependent actions reliably)

The accessibility violation: Interactive functionality requires specific input methods without keyboard equivalents or alternative access.

Why organisations do this: Sophisticated data visualisation libraries don't include accessibility by default. Developers implement without considering alternative input methods.

Failure 4: PDF-Only Impact Reports

What organisations create: Comprehensive PDF impact report with charts, graphs, tables, narrative analysis—designed for print, uploaded as digital document.

Who this excludes:

  • Screen reader users (PDFs often lack proper tagging)
  • Mobile users (PDFs require pinch-zoom, horizontal scrolling)
  • Users with cognitive disabilities (can't reformat for readability)
  • Users needing text resizing (fixed PDF formatting prevents adjustment)

The accessibility violation: No HTML alternative providing equivalent information in accessible format.

Why organisations do this: "We already created the print version—just upload the PDF" without understanding digital accessibility requirements differ from print.

Failure 5: Data Tables Without Proper Structure

What organisations create: Tables showing outcomes data without proper HTML markup—using images of tables, or HTML tables lacking header associations, or complex merged cells confusing structure.

Who this excludes:

  • Screen reader users (can't navigate tables without proper markup)
  • Users needing data extraction (can't copy/process data from images)
  • Mobile users (improperly structured tables don't reflow)

The accessibility violation: Data presented in table format without semantic structure enabling assistive technology interpretation.

Why organisations do this: Visual table appearance prioritised over accessible structure. Developers don't understand proper table markup requirements.

The Multi-Format Impact Presentation Framework

After 7+ years specialising in nonprofits, I've learned that accessible impact visualisation requires presenting same information in multiple formats serving different stakeholder needs and abilities.

Format 1: Visual Data Presentation (For Sighted Users)

What this includes: Charts, graphs, infographics, visual representations making data patterns immediately recognisable.

Accessibility requirements:

  • Sufficient colour contrast (WCAG AA: 4.5:1 for text, 3:1 for graphics)
  • Information not conveyed by colour alone (use patterns, labels, position)
  • Descriptive alternative text summarising key findings
  • Scalable vector graphics enabling zoom without pixelation

When this works:Sighted users can quickly understand outcomes patterns, trends, and effectiveness evidence through visual perception.

Example:Bar chart showing programme reach over five years with clear axis labels, high-contrast colours, pattern fills distinguishing categories, alternative text: "Programme reach grew from 150 participants in 2019 to 650 in 2023, with particularly strong growth in 2021-2022 following programme expansion."

Format 2: Structured HTML Data (For Screen Reader Users)

What this includes:Same outcomes data presented in properly structured HTML with semantic markup enabling assistive technology interpretation.

Accessibility requirements:

  • Proper heading hierarchy (H2, H3, H4) structuring information
  • Data tables with header associations (<th scope="col">, <th scope="row">)
  • Clear labels describing data meaning
  • Logical reading order supporting sequential navigation

When this works:Screen reader users can navigate data structure, understand relationships, and access same information visual users perceive.

Example:

<h2>Programme Reach 2019-2023</h2>
<table>
 <caption>Annual participant numbers showing programme growth</caption>
 <thead>
   <tr>
     <th scope="col">Year</th>
     <th scope="col">Participants</th>
     <th scope="col">Change</th>
   </tr>
 </thead>
 <tbody>
   <tr>
     <th scope="row">2019</th>
     <td>150</td>
     <td>Baseline</td>
   </tr>
   <!-- Additional rows -->
 </tbody>
</table>

Format 3: Narrative Summary (For All Users)

What this includes: Plain language explanation of key findings, trends, and significance in paragraph format accessible to everyone.

Accessibility requirements:

  • Clear writing at appropriate reading level
  • Logical information flow
  • Key findings highlighted without relying on visual formatting alone
  • Context explaining data meaning and implications

When this works: All users—regardless of disability, technical capability, or data literacy—can understand impact meaning without interpreting raw data.

Example: "Our programme reached 650 young people in 2023, more than four times the 150 participants we served in 2019. This growth reflects programme expansion in 2021-2022 when we added three new community partnerships and increased capacity through additional staff. The sustained growth demonstrates both programme effectiveness and community demand for our services."

Format 4: Downloadable Data (For Researchers and Analysts)

What this includes: Raw data in accessible formats (CSV, Excel with proper structure) enabling independent analysis and verification.

Accessibility requirements:

  • Simple tabular structure without merged cells or complex formatting
  • Clear variable names and data definitions
  • Documentation explaining data collection and measurement
  • Machine-readable format supporting assistive technology

When this works: Funders, researchers, and data-literate stakeholders can verify claims, conduct additional analysis, and integrate data into their own systems.

Example: CSV file with columns: Year, Programme, Participants, Demographics, Outcomes—downloadable from "Our Impact" page with data dictionary explaining variables.

The Stakeholder-Specific Outcomes Presentation

Different stakeholders need impact data for different purposes—presentation should accommodate multiple legitimate uses:

For Funders: Evidence of Effectiveness and Accountability

What funders need: Verification that programmes achieve stated outcomes, resources are used effectively, impact measurement is rigorous, and institutional claims are credible.

Accessible presentation:

  • Clear outcomes data showing progress toward goals
  • Methodology explanation enabling credibility assessment
  • Comparison to targets or benchmarks
  • Evidence of data quality and measurement rigour
  • Multiple format options for verification

Example section: "Outcomes Achievement 2023: We exceeded our target of supporting 500 young people to employment, reaching 547 participants (109% of goal). Employment outcomes were tracked through 6-month follow-up surveys achieving 78% response rate. Of respondents, 64% were employed or in education six months after programme completion, compared to 31% baseline at programme entry."

All data available as: visual chart, HTML table, narrative summary, and downloadable CSV.

For Beneficiaries: Evidence of Community Benefit and Programme Quality

What beneficiaries need: Understanding whether programme serves people like them effectively, what outcomes they might expect, how the organisation demonstrates accountability to communities served.

Accessible presentation:

  • Outcomes described in beneficiary-relevant terms (not just funder metrics)
  • Evidence programme works for diverse participants
  • Clear explanation of what data means for potential participants
  • Dignity-preserving presentation avoiding exploitation
  • Plain language accessible to non-technical audiences

Example section: "What participants achieve: Most young people (64%) who complete our programme are working or studying six months later—double the rate when they started. Participants develop job skills, build confidence, and create professional networks supporting long-term career success. These outcomes are consistent across different backgrounds, showing the programme works for diverse young people."

Multiple formats ensure accessibility regardless of disability or technical capability.

For Board and Governance: Oversight Verification and Accountability

What trustees need: Evidence the organisation achieves its mission, resources create appropriate impact, measurement systems are credible, and institutional accountability exists.

Accessible presentation:

  • Mission alignment demonstration showing outcomes match purpose
  • Resource allocation transparency linking spending to impact
  • Measurement methodology enabling governance confidence
  • Multi-year trends showing institutional performance
  • Comparison to sector standards or benchmarks

Example section: "Mission Achievement 2023: Our charitable purpose centres on supporting young people into sustainable employment. This year, 547 participants achieved employment skills development with 64% employed or in education at six-month follow-up—demonstrating effective mission delivery. Investment of £847,000 created £15,000 average cost per participant employed, within sector benchmarks of £12,000-£18,000."

Accessible to Board members with varying technical sophistication and abilities.

For General Public: Transparency and Community Accountability

What public needs: Evidence the organisation creates genuine community benefit justifying tax-exempt status, resources are used responsibly, and institutional accountability exists.

Accessible presentation:

  • Clear community impact demonstration
  • Transparency about what organisation achieves
  • Honest presentation including challenges and limitations
  • Accessibility enabling broad public verification
  • Context explaining significance beyond raw numbers

Example section: "Community Impact 2023: We supported 547 young people to develop employment skills this year. While we're proud that most participants (64%) achieved employment or continued education, we acknowledge that 36% did not achieve these outcomes at six-month follow-up. We're analysing barriers preventing success to improve programme effectiveness and ensure we serve all participants appropriately."

Multiple formats ensure accessibility across diverse public audiences.

The WCAG Requirements for Data Visualisation

Accessible impact visualisation must meet Web Content Accessibility Guidelines standards:

Requirement 1: Perceivable Data Presentation

Non-text Content (WCAG 1.1.1):All charts, graphs, and infographics must have alternative text describing data content and key findings.

Use of Colour (WCAG 1.4.1):Information cannot be conveyed by colour alone. Use patterns, labels, or position as redundant encoding.

Contrast (WCAG 1.4.3):Minimum 4.5:1 contrast ratio for text, 3:1 for data visualisation elements. Higher contrast improves readability for everyone.

Resize Text (WCAG 1.4.4):Users must be able to resize text up to 200% without loss of content or functionality. SVG graphics scale appropriately.

Images of Text (WCAG 1.4.5):Avoid presenting data as images of text when HTML text could convey same information.

Requirement 2: Operable Data Interaction

Keyboard (WCAG 2.1.1):All interactive data visualisation functionality must be accessible via keyboard without requiring specific timings.

No Keyboard Trap (WCAG 2.1.2):Keyboard focus must be able to move away from interactive charts without getting trapped.

Focus Visible (WCAG 2.4.7):Interactive elements must have visible focus indicator showing keyboard users where they are.

Requirement 3: Understandable Data Communication

Language of Page (WCAG 3.1.1):Data visualisation language must be programmatically determinable.

On Input (WCAG 3.2.2):Interacting with data visualisation shouldn't unexpectedly change context.

Labels or Instructions (WCAG 3.3.2):Interactive data elements must have clear labels explaining their purpose.

Requirement 4: Robust Data Markup

Parsing (WCAG 4.1.1):HTML must be valid with proper element nesting and attribute usage.

Name, Role, Value (WCAG 4.1.2):Custom interactive components must have accessible names, roles, and values programmatically determinable.

The Common Visualisation Tools and Accessibility

Different data visualisation approaches have different accessibility characteristics:

Chart.js, D3.js, Highcharts (JavaScript Libraries)

Accessibility capabilities:Can be made accessible with proper implementation including alternative text, keyboard navigation, ARIA labels, and semantic HTML fallbacks.

Common failures:Developers implement without accessibility consideration. Mouse-only interactions. Missing alternative text. Colour-dependent encoding.

Making them accessible:Provide text alternative describing data. Ensure keyboard access. Use colour with patterns. Include data table fallback.

Infographic Images (Static Graphics)

Accessibility capabilities:Can provide comprehensive alternative text. High contrast and clear design benefit all users.

Common failures:Complex alternative text inadequate for conveying detailed data. No way to access underlying numbers. Can't be resized or reformatted.

Making them accessible:Provide detailed alternative text summarising key findings. Include HTML data table with same information. Ensure sufficient contrast and text size.

Interactive Dashboards (Tableau, Power BI)

Accessibility capabilities:Professional tools include some accessibility features. Can export to accessible formats.

Common failures:Embedded dashboards often inaccessible. Require mouse interaction. Complex navigation confusing screen reader users.

Making them accessible:Provide alternative HTML presentation. Include data download option. Ensure keyboard navigation works. Test with screen readers.

The Questions That Reveal Impact Visualisation Gaps

When I conduct Blueprint Audits, these questions consistently expose whether impact data is genuinely accessible:

"Can a blind stakeholder access the same impact information a sighted stakeholder perceives visually?"

If impact evidence is only available through visual charts without text alternatives—you're excluding screen reader users from effectiveness verification.

"Can a colour-blind stakeholder distinguish data categories in your visualisations?"

If information relies on colour alone without patterns, labels, or position—you're excluding substantial stakeholder segment.

"Can a keyboard-only user interact with your data visualisations?"

If charts require mouse hover or click without keyboard equivalents—you're excluding people who can't use mice.

"Can stakeholders download data to verify claims independently?"

If raw data isn't available in accessible format—you're preventing independent verification and analysis.

The Blueprint Audit Approach to Impact Visualisation

This is why Blueprint Audit process specifically addresses impact measurement accessibility as governance infrastructure component.

The impact visualisation analysis includes:

Current accessibility audit: How accessible are existing data presentations? What barriers exist for stakeholders with disabilities?

Multi-format presentation framework: How can same impact data be presented in visual, HTML, narrative, and downloadable formats serving different needs?

WCAG compliance verification: Do data visualisations meet accessibility standards? What remediation is required?

Stakeholder navigation strategy: How does impact presentation serve funders, beneficiaries, Board, and public simultaneously?

The output provides accessible impact communication framework treating data accessibility as institutional integrity requirement, not technical consideration.

The Core Insight

Impact measurement visualisation serves legitimate communication needs—making complex data understandable, engaging stakeholders, demonstrating effectiveness efficiently.

But visualisation that excludes stakeholders with disabilities contradicts institutional values whilst preventing legitimate verification of effectiveness claims.

Accessible impact communication requires presenting same information in multiple formats: visual for sighted users, structured HTML for screen readers, narrative for all audiences, downloadable data for analysis.

This isn't burden creating duplicate work—it's governance infrastructure ensuring impact evidence is actually accessible to all stakeholders who need to verify your effectiveness claims.

For organisations claiming inclusion values, inaccessible impact data isn't just technical failure—it's institutional values contradiction visible to everyone paying attention.

When your impact visualisation works for all stakeholders regardless of disability or technical capability, you demonstrate that accessibility is architectural commitment, not performative claim.

Need impact visualisation framework ensuring accessibility whilst maintaining engagement? The Blueprint Audit includes data presentation accessibility audit, multi-format communication strategy, and WCAG compliance verification providing governance infrastructure for inclusive outcomes reporting. £2,500 for accessible impact framework preventing stakeholder exclusion.

Learn more about the Blueprint Audit

Eric Phung has 7 years of Webflow experience building 100+ websites across industries. He specialises in nonprofit website migrations using the Lumos accessibility framework. Current clients include WHO Foundation, Do Good Daniels Family Foundation, and Territorio de Zaguates.

Eric Phung
Website Consultant for Nonprofits and International NGOs

In case you missed it

Related articles

Join our newsletter

Subscribe to my newsletter to receive latest news & updates

Subscribe
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Modern building with large triangular windows reflecting sunset light, surrounded by greenery and trees near a water body.