While there are requirements for accessibility, using this checklist will ensure your dashboard is as accessible as possible, particularly for users with visual disabilities who use assistive technologies. If your dashboard does not meet all items in the accessibility checklist or uses inaccessible elements, please work with your accessibility coordinator to file an exception.
General Principles
- Design for screen reader compatibility (titles, captions, alt text)
- Ensure keyboard navigation is fully functional
- Use clear layout and language for cognitive accessibility
- Provide sufficient color contrast and visual cues
- Provide contact information for the department and/or Creator publishing the dashboard. Central emails addresses for the OTDI Data Visualization team (such as data-visualization@osu.edu) should not be used unless developed by that team
Dashboard Structure
- Include a descriptive dashboard title
- Use descriptive titles for all charts, graphs, tables, filters, parameters, and legends
- Convert text objects to worksheets or ensure captions are visible
- Use consistent naming for workbooks, dashboards, and sheets
- Use accessible dashboard elements
Links and Navigation
- Use descriptive link text (avoid “click here”)
- Add alt text to images used as links
- Use tooltips for image-based navigation buttons
- Ensure navigation objects have descriptive titles
Text and Labels
- Use narrative titles and captions
- Avoid placing critical text inside visual elements
- Use plain language: short sentences, common words, logical order
- Avoid jargon or abbreviations
Visual Design
- Use color and labels/shapes to convey meaning. Do not rely on color alone.
- Maintain a text contrast ratio of at least 4.5:1 (or 3.1 for large text)
- Avoid using scarlet.
- Use Ohio State’s branded, colorblind-friendly palette.
- Use less than 10 colors in a view
Data and Metadata
- Rename fields in the data source (not just aliasing)
Interactivity and Permissions
- Enable users to download summary data (not full data)
- Include at least one interactive element (such as filters)
Consistency and Cognitive Load
- Use consistent fonts, colors, and layout across dashboards
- Minimize cognitive overload (remove unnecessary elements). A good rule of thumb is between 5 – 9 objects on a dashboard
- Limit text to essential context and insights
Accessibility Testing
- Perform visual review (check for sensory-only cues). Test a copy of the dashboard in greyscale for understanding
- Test keyboard navigation (tab, shift + tab, enter)
- Use a screen reader (e.g., NVDA) to verify content is announced correctly
- Retest after updates to dashboards
Governance and Review
- Consult your area’s accessibility coordinator before publishing to production
- Work with your area’s accessibility coordinator to file an exception if the dashboard cannot meet accessibility standards
Important Information
To view a tutorial on designing accessible dashboards, please complete the Accessibility and Tableau Dashboard Design course in BuckeyeLearn.