I don't think linking to the accessibility table will be enough, but perhaps. Also, a paged version of the table might be feasible, perhaps even using the Table chart. But the data is local already, actually, so it is not about fetching the data again. The problem is only the generation of a large amount of HTML to represent this table.
On Tue, Mar 10, 2015 at 11:59 PM, Dale Cox <[email protected]> wrote: > Happy to help and thanks for sharing your changes back. > > I've checked in your changes so same links will still work for future > testing if you need them. > > For the accessibility table what about embedding a hidden link that a > screen reader would still be able to pick-up? If the user wanted that data > then they could open the link and be served the data on demand using > something like a http GET operation. > >> > Thanks again for the help! :) > > -- > You received this message because you are subscribed to the Google Groups > "Google Visualization API" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to > [email protected]. > Visit this group at > http://groups.google.com/group/google-visualization-api. > For more options, visit https://groups.google.com/d/optout. > -- Daniel LaLiberte <https://plus.google.com/100631381223468223275?prsrc=2> - 978-394-1058 [email protected] <[email protected]> 5CC, Cambridge MA [email protected] <[email protected]> 9 Juniper Ridge Road, Acton MA -- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-visualization-api. For more options, visit https://groups.google.com/d/optout.
