Hi, I'm in the same position as OP. I'm creating line and table charts using google viz for government websites. The JavaScript part of it doesn't concern me. If a user has JS turned off, most of the governments sites wont work anyways and we've never heard any complaints on the JS part of it.
What i want to know is if I use the Table chart visualization, can it be read by screen readers? Can a line chart visualization be read by screen readers? Or is the more accessible way to use the google Line chart visualization and then hard code the Table version in HTML? I'd prefer not to code anything in HTML since the Line/Table visualizations are easily swappable. Thanks. On Tuesday, December 13, 2011 3:51:31 AM UTC-5, Riccardo Govoni wrote: > > Hi Scott, > I think your snippet refers to this page ( > http://www.filamentgroup.com/lab/update_to_jquery_visualize_accessible_charts_with_html5_from_designing_with/) > > ,right? > > You can still achieve the same results described in the article with > Google Charts. First, you have access to the container where the chart is > rendered into, so you can attach both the role and aria-label attributes to > it. Second, you can always render the chart contents as table, either using > a plain HTML table or using the Google Charts table visualization, which > actually renders using HTML elements, so it more screen-reader friendly > than other charts. > > Would that work? > > -R. > > On 12 December 2011 10:10, Scott Glenister <scottgl...@gmail.com<javascript:> > > wrote: > >> Hi Riccardo, >> >> Thanks for your help, I am so tempted to use Google interactive charts, >> and have google image charts as the fallback when javascript is disabled. >> However I need it to be super accessible because it's going to be on a >> government website: >> >> ARIA support now included >> >> Though this approach to creating charts and graphs is inherently >> accessible — the table data remains in the page markup for screen readers >> and browsers that don't support JavaScript — we realized that the canvas >> element needed ARIA attributes to better identify it as a visualization. In >> the latest update to Visualize, we edited the plugin to automatically >> assign two ARIA attributes to the chart container to more clearly identify >> its purpose to screen readers: >> >> - *role="image"* – tells screen readers that the chart is purely >> visual, and can therefore be skipped >> - *aria-label="Chart representing data from: [table caption value]"*– >> specifically identifies the chart's content as belonging to the >> associated table >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google Visualization API" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/google-visualization-api/-/6S_-XNDPWMsJ. >> >> To post to this group, send email to >> google-visua...@googlegroups.com<javascript:> >> . >> To unsubscribe from this group, send email to >> google-visualization-api+unsubscr...@googlegroups.com <javascript:>. >> For more options, visit this group at >> http://groups.google.com/group/google-visualization-api?hl=en. >> > > -- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-visualization-api/-/fPZdqDDle30J. To post to this group, send email to google-visualization-api@googlegroups.com. To unsubscribe from this group, send email to google-visualization-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en.
