Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Current »

Interactive PowerBI charts are typically embedded to a web page via an iFrame. 

It's important that this data is fully accessible to both keyboard only and screen reader users.

Guidelines for PowerBI Charts

Here are some general guidelines to follow.

  • Add ALT text to graphics.

  • Provide keyboard only users with instructions on how to navigate and interact with the charts. This would include instructions on specific keystrokes for users to press.

  • Provide keyboard only users and screen reader users with instructions on how to interact with the filters.

  • PowerBI charts often rely on using colors to convey data. However, screen reader users would not be able to pick up this type of information. Make sure that there is a text based equivalent. 

  • For users with learning disabilities and users who find it challenging to interact with the PowerBI charts, please provide a text based equivalent of the raw data presented within the chart. The link to the text based equivalent should be placed in close proximity to the actual chart.

  • Ensure that all chart labels are displayed horizontally.

  • Ensure that there is enough color contrast between chart legends and chart graphs.

Please see additional guidelines and standards provided by Data SF and the Controller’s Office.

https://datasf.gitbook.io/public-data-visualization-guide/

Any time that CCSF is displaying data to the public, it should also be made accessible as a dataset on http://data.sfgov.org

Please contact support@datasf.org if you like to publish new data to the open data website.

Guidelines for Interactive Maps

Here are some general guidelines to follow.

  • Keyboard only users, screen reader users and users with learning disabilities who are unable to interact with the map, must be provided with a text based equivalent of the raw data presented within the map.

  • The link to the text based equivalent should be placed in close proximity to the actual map.






  • No labels