On Tuesday, March 12, 2019 at 5:45:36 PM UTC-4, Robert Engels wrote: > > I did just encounter a case though where trying to copy and paste a table > wasn’t happening, and there is no way I am going to type it all in or get > the author to change it, so screen shot it is... >
I have done the same -- but it is really an upstream instance of the same problem that Ohir points out: If all that is needed is text, then text is good, and pictures of text are bad. And when I had to deal with pictures of text, I was furious, and it came through loud and clear in the bug report for which the pictures should not have been necessary. There's lots of details for accessibility, it would be nice if we had tools to help us remember because otherwise we're certain to forget from time to time. See/hear for example Julia Ferraioli's Gophercon talk on increasing accessibility in the code that we write: https://www.youtube.com/watch?v=cVaDY0ChvOQ (Her eyes apparently do not focus dependably, hence the screen reader.) Sorry if I committed a quoting mistake, I can't tell if that is an issue or not, though I saw some mention. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
