On 5 Apr 2016, at 03:01, Kevin Chao <[email protected]> wrote: > On Mon, Apr 4, 2016 at 6:21 AM Sabahattin Gucukoglu <[email protected]> wrote: >> Well, to be fair, ChromeVox would be a better extension if it could actually >> announce the chrome in Chrome. > > It's built using web technology (HTML5/JavaScript) and content scripts are > injected to each page, so this was done by design. It still does better than > traditional/legacy desktop-based screen readers with advanced interactive web > apps (e.g. Twitter, FaceBook, Docs & Drive, Office 365, etc.).
Sure, but I’d say that this was a bug in the native screen reader, rather than an inherent advantage of injected javascript. Indeed the “Next” branch is moving away from this model, for added responsiveness. Really, I’d rather VoiceOver improved, and I think VoiceOver already has an edge over the other guys for more complex web applications. You can already use Twitter quite comfortably just using Safari, now, with VoiceOver. Google applications, far less well. Others have a positive opinion of the Firefox+NVDA combination, although I’m not sure what all the fuss is about personally (especially when you consider all the other failings of the WinBloze platform). >> You’d have to leave aside the fact that using a dedicated screen reader >> just for your web browser was kind of crazy to start with, but it’s >> basically the reality on ChromeBooks. > > Why is this "crazy"? There are so many great web apps that only require a > browser and will work mostly the same across Linux, Mac, Windows, and Chrome > OS. e.g. I'm using inbox.google.com with VoiceOver to interact with this > thread/bundle. Mmm, I’m not sold on that idea personally. You’re right, the web is becoming the new terminal, but native still has a place. This email brought to you from the native Mail app in Mac OS. :) But actually, my point was that having to use a different screen reader just for one application is madness. And, it is! It’s a boon to accessibility, of course, but it’s also the perfect indictment for your platform and its screen reader. Nothing is perfect, but it ought to be more perfect, and that includes being able to choose a browser / screen reader combination, IMO. And, as I said, you can always use a ChromeBook if you want to live the dream of the web-based utopia. I’m all for that choice, and (as an owner of such a ChromeBook) I’ll gladly acknowledge it. There’s a lot to be said for a web that’s so invisible it only takes a single application on a secure platform to use it and do the many things that can be done as the consumer wishes, if that meets your needs. But I think the fact it’s Google’s OS and Google’s browser and Google’s web applications go a long way to explaining why it works so well, rather than, as such, the use of the web. Remember, nobody else using Safari or Firefox on OS X have the problems we do. -- The following information is important for all members of the Mac Visionaries list. If you have any questions or concerns about the running of this list, or if you feel that a member's post is inappropriate, please contact the owners or moderators directly rather than posting on the list itself. Your Mac Visionaries list moderator is Mark Taylor and your owner is Cara Quinn - you can reach Cara at [email protected] The archives for this list can be searched at: http://www.mail-archive.com/[email protected]/ --- You received this message because you are subscribed to the Google Groups "MacVisionaries" 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 https://groups.google.com/group/macvisionaries. For more options, visit https://groups.google.com/d/optout.
