Skip to content

Commit

Permalink
Update accessibility_intro.md
Browse files Browse the repository at this point in the history
  • Loading branch information
pzaldonis committed Apr 29, 2024
1 parent b529a92 commit 46ee6e4
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions docs/_accessibility/accessibility_intro.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,30 +14,30 @@ Federally-funded agencies are required to make their content accessible to peopl
We should all prioritize accessibility from the start of our data visualization process and should consider hearing, motor, cognitive, and visual accessibility. Use these guidelines as a starting place for designing accessible data visualizations.

#### Table of Contents
##### [Data](/data-visualization-guidelines/accessibility/data/data_intro)
##### [Data](/data-visualization-guidelines/accessibility/data/intro)
1. [Provide access to the data in an accessible table format](/data-visualization-guidelines/accessibility/data/table_format)
2. [Use data visualizations that are familiar to viewers](/data-visualization-guidelines/accessibility/data/familiar_visualizations)

##### [Color](/data-visualization-guidelines/accessibility/color/color_intro)
##### [Color](/data-visualization-guidelines/accessibility/color/intro)
1. [Avoid relying on color as the only way to convey information](/data-visualization-guidelines/accessibility/color/color_alone)
2. [Ensure that there is sufficient contrast between colors used in your data visualization or dashboard](/data-visualization-guidelines/accessibility/color/color_contrast)
3. [Choose colors that are accessible and colorblind friendly](/data-visualization-guidelines/accessibility/color/colorblind_friendly)
4. [Use white space](/data-visualization-guidelines/accessibility/color/white_space)

##### [Text](/data-visualization-guidelines/accessibility/text/text_intro)
##### [Text](/data-visualization-guidelines/accessibility/text/intro)
1. [Provide a text-based equivalent for every data visualization](/data-visualization-guidelines/accessibility/text/text_equivalent)
2. [Use alternative text (alt text) to describe all non-decorative visuals](/data-visualization-guidelines/accessibility/text/alt_text)
3. [Use plain language](/data-visualization-guidelines/accessibility/text/plain_language)
4. [Ensure text is readable](/data-visualization-guidelines/accessibility/text/readable_text)
5. [Create meaningful labels and titles](/data-visualization-guidelines/accessibility/text/labels_and_titles)

##### [Interaction](/data-visualization-guidelines/accessibility/interaction/interaction_intro)
##### [Interaction](/data-visualization-guidelines/accessibility/interaction/intro)
1. [Make interactive visualizations keyboard-accessible](/data-visualization-guidelines/accessibility/interaction/keyboard)
2. [Ensure the keyboard focus indicator is easily visible](/data-visualization-guidelines/accessibility/interaction/focus_indicator)
3. [Check that the tab order is logical and intuitive for keyboard and assistive technology users](/data-visualization-guidelines/accessibility/interaction/tab_order)
4. [Don’t require interactions to access key information](/data-visualization-guidelines/accessibility/interaction/key_information)

##### [Testing](/data-visualization-guidelines/accessibility/testing/testing_intro)
##### [Testing](/data-visualization-guidelines/accessibility/testing/intro)
1. [Test your visualization or dashboard with a screen reader](/data-visualization-guidelines/accessibility/testing/screen_reader)
2. [Test for low vision](/data-visualization-guidelines/accessibility/testing/low_vision)
3. [Test on mobile](/data-visualization-guidelines/accessibility/testing/mobile)
Expand Down

0 comments on commit 46ee6e4

Please sign in to comment.