[nfbcs] Google Accessibility was RE: evaluation display of a web page

[Jim Barbour]

It is true that Google, and every other web application developer,
releases code far more frequently than older PC based software did.
However, it's still a good idea to let google know when you find thuff
that doesn't work.

The same is true for Apple.

I don't know why, but we blind folks seem especially unwilling to
speak up and let companies know when stuff isn't working for us.  We
seem to have the rather toxic idea that "they should know if
accessibility is broken and if they don't want to fix it then I'm
going to help them."

Jim

On Mon, Nov 04, 2013 at 01:40:37PM -0800, Mike Freeman wrote:
> The problem is that "fixes" may not stick. Google is tinkering with its
> stuff constantly. The phrase "if it ain't broke, don't fix it" is not in
> their vocabulary.
> 
> Mike Freeman
> 
> 
> -----Original Message-----
> From: nfbcs [mailto:nfbcs-bounces at nfbnet.org] On Behalf Of Nicole Torcolini
> Sent: Saturday, November 02, 2013 3:16 PM
> To: 'NFB in Computer Science Mailing List'
> Subject: [nfbcs] Google Accessibility was RE: evaluation display of a web
> page
> 
> April and all, if you are having problems with Google products, please let
> them know. They may not be able to fix it right away, but they still want to
> know and might be able to tell you some kind of work around. 
> 
> -----Original Message-----
> From: nfbcs [mailto:nfbcs-bounces at nfbnet.org] On Behalf Of April Brown
> Sent: Saturday, November 02, 2013 2:05 PM
> To: nfbcs at nfbnet.org
> Subject: Re: [nfbcs] evaluation display of a web page
> 
> Ten years or so ago, I learned HTMl and attempted to code accessible from
> W3schools.  They do have Code check.  I don't think it's that good.  In the
> last year I have lost most of my vision, and much of my hearing, so it's
> even more important than ever!  And I always wanted to code accessible.
> Though, knowing some varying issues, especially with vision, I'm not 100%
> sure it is possible to code for every variation.  I may be wrong.
> 
> Hi *Susan Stanzel,  It would be wonderful if programs on both ends could fix
> the issues to make websites more accessible.  And I agree.  I have tried to
> learn NVDA, and well, learning keyboard workarounds is ten times harder than
> HTML ever was!
> 
> Hi ***Mike Jolls - Since you evaluate websites for accessibility, can I ask
> you a question?  For the last few years, my author website has been on a
> Google site.  Are Google websites accessible?  I can change some of the
> coding, though much of what I think would need to be adjusted is not
> accessible to the page holders that I can find.
> 
> Thanks.  Still new to the world of mostly deaf and blind, and the screen
> readers that confuse me when they don't just work when I open the page.*
> 
> *
> 
> 
> _______________________________________________
> nfbcs mailing list
> nfbcs at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for nfbcs:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/ntorcolini%40wavecable.co
> m
> 
> 
> _______________________________________________
> nfbcs mailing list
> nfbcs at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for nfbcs:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/k7uij%40panix.com
> 
> 
> _______________________________________________
> nfbcs mailing list
> nfbcs at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for nfbcs:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/jbar%40barcore.com
>