Data visualizations are one form of data representation.

Charts, graphs, maps, dashboards, and infographics help many users understand patterns, trends, and insights more quickly than raw data alone. Visualizations are particularly effective for sighted users who interpret visual relationships efficiently.

However, visualization is not accessible to everyone by default.

Digital accessibility at UGA requires that data be represented in ways that support users with a wide range of abilities and technologies.

Data should be available in multiple formats so it can be interpreted visually, audibly, or programmatically.

Why Data Visualization Accessibility Matters at UGA

At UGA, data visualizations appear in:

• Research dashboards
• Institutional reporting
• Grant proposals
• Academic publications
• Course materials
• Public-facing websites
• Business intelligence tools

These materials are accessed by students, faculty, staff, administrators, researchers, and members of the public.

If visualizations are not accessible, critical information may be unavailable to users who rely on:

• Screen readers
• Keyboard navigation
• Magnification
• High-contrast settings
• Alternative input devices

Accessible data visualization supports equitable participation in research, instruction, and administration.

Key Accessibility Principles for Data Visualizations

Accessibility needs vary depending on visualization type and complexity. The following four principles apply broadly across most platforms and tools.

Principle 1: Focus on Essential Insights

Effective accessible design begins with clarity.

• Identify the key takeaway or primary message
• Remove unnecessary or decorative data
• Avoid excessive density or clutter
• Break complex, multi-dimensional data into separate views
• Allow users to toggle additional layers or dimensions

Clear visual design benefits all users and reduces cognitive load.

Principle 2: Use Clear, Structured Descriptions

Every data visualization should include descriptive context.

• Start with a summary of what the chart shows
• Identify axes, units, and time frames
• Describe trends or relationships when appropriate
• Ensure hover-revealed information is accessible by keyboard
• Ensure dynamic changes are communicated to assistive technologies

Avoid relying solely on static images of charts. If images are used, keep them simple and provide meaningful alternative text.

For complex visualizations, consider including a longer description below the chart.

Principle 3: Provide Multiple Representations of Data

Visual representation should not be the only way to access data.

Provide at least one additional format:

• Include a data table alongside the visualization
• For datasets with more than 20 rows, provide a representative sample in-page
• Offer the full dataset as a downloadable file
• Consider additional representations, such as data sonification, where appropriate

Providing multiple formats ensures the data can be interpreted using assistive technologies.

Principle 4: Apply Accessibility Standards

All visualizations and interactive elements must align with WCAG 2.1 AA standards.

Key requirements include:

• Sufficient color contrast between text, graphics, and backgrounds
• Do not rely on color alone to differentiate lines, bars, or categories
• Use patterns, shapes, labels, or size differences in addition to color
• Ensure all interactive elements are keyboard accessible
• Provide visible focus indicators
• Use readable text that can be resized
• Design responsive layouts that work across screen sizes without requiring horizontal scrolling

Accessibility standards apply to both static and interactive visualizations.

Tools and Platforms

Business Intelligence Platforms

Platforms such as Tableau and Power BI allow users to create dashboards without coding. While widely used across higher education, they may present accessibility challenges for screen reader and keyboard users, especially when visualizations are complex.

Accessibility requires intentional design and configuration.

When using business intelligence tools:

• Provide descriptive summaries
• Include data tables where possible
• Test dashboards using keyboard navigation
• Verify color contrast and labeling

Consult platform-specific accessibility documentation before publishing.

JavaScript Charting Libraries

JavaScript charting libraries enable custom visualizations for the web. Built-in accessibility support varies by library.

Web developers must evaluate output carefully and enhance accessibility where necessary.

When selecting a charting library:

• Review keyboard accessibility features
• Confirm screen reader compatibility
• Ensure ARIA roles and labels are properly implemented
• Test dynamic content announcements

Accessible implementation requires both tool selection and thoughtful configuration.

Additional Resources

Digital Accessibility Services provides guidance and support for accessible data visualization practices at UGA.

Recommended actions:

• Review the UGA Digital Accessibility guidance pages
• Test visualizations using keyboard-only navigation
• Verify color contrast
• Provide accompanying data tables
• Request consultation for complex dashboards

If you are developing research dashboards, institutional reports, or public-facing data tools, consult Digital Accessibility Services early in the design process.

Get Help

Accessibility support is available through UGA’s coordinated campus network.

You can:

• Contact your unit’s Digital Accessibility Liaison
• Request a consultation through EITS
• Attend accessibility training sessions
• Explore guidance within DASH

Accessible data representation strengthens research integrity, instructional quality, and public engagement at the University of Georgia.