Re: Microsoft Edge Personal
Amanda, I don't know about JAWS. And Unfortunately I've laid dear Window-Eyes to rest and don't have it on my system. But it works fine with NVDA and Narrator. Good luck, Tom On 7/9/2020 11:04 PM, Amanda Lee via Talk wrote: This is true. I have found an issue so far though. If you go to www.landsend.com pick your gender or other category. Then it will offer a means to break out the product selection by category such as for women, tops, bottoms, sleepwear, etc. These categories are presented as Radio Buttons but the associated text is not reading with Window-Eyes at least. Therefore, it's not readily as easy to narrow down the list to say Women's Tops or Men's Shirts, etc. I certainly will try with JAWS. I have JAWS 19 and need to upgrade it. Still, it's much more responsive so I sure will use Edge now moreso. -Original Message- From: Talk On Behalf Of Tom Kingston via Talk Sent: Thursday, July 9, 2020 10:27 PM To: Sky Mundell via Talk Cc: Tom Kingston Subject: Re: Microsoft Edge Personal It's because the new Edge uses chromium, which is to say it's the Chrome browser with Microsoft's front end on it. And making Chrome accessible was one of the last things done, but not completed, with Window-Eyes. Enjoy, Tom On 7/9/2020 9:54 PM, Sky Mundell via Talk wrote: That's amazing! It still shows the power of the program. -Original Message- From: Talk On Behalf Of Amanda Lee via Talk Sent: July 9, 2020 6:43 PM To: 'Window-Eyes Discussion List' Cc: Amanda Lee Subject: Microsoft Edge Personal Hello, With this latest update of Windows 10, I was very pleasantly surprised to see that Edge is very much changed. I know this was coming but I didn't initiate the download to install the most current version prior to this latest Windows Update. I was amazed! To find that when I navigated to a site which causes IE to kind of do a huge deep knees bend! Edge brought up the site up and now we can navigate with what seems to be the majority, if not all of the navigation keys that we'd typically use in IE. Window-Eyes isn't dead yet! It performed awesomely! I'm still using Window-Eyes for Office as well which isn't quite as up-to-date as the last version. ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/skyt%40s haw.ca . For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/tom.kingston%4 0charter.net. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/amandainparadi se777%40gmail.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/tom.kingston%40charter.net. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
Re: Microsoft Edge Personal
is there any hot keys to stop edge from talking when it is reading the entire page? -Original Message- From: Darrell Bowles via Talk Sent: Thursday, July 09, 2020 6:55 PM To: Window-Eyes Discussion List Cc: Darrell Bowles Subject: RE: Microsoft Edge Personal And edge, has a reader view, that I highly recommend you try! It's an amazing bit of accessibility on microsoft's part! Darrell -Original Message- From: Talk On Behalf Of Amanda Lee via Talk Sent: Thursday, July 9, 2020 9:43 PM To: 'Window-Eyes Discussion List' Cc: Amanda Lee Subject: Microsoft Edge Personal Hello, With this latest update of Windows 10, I was very pleasantly surprised to see that Edge is very much changed. I know this was coming but I didn't initiate the download to install the most current version prior to this latest Windows Update. I was amazed! To find that when I navigated to a site which causes IE to kind of do a huge deep knees bend! Edge brought up the site up and now we can navigate with what seems to be the majority, if not all of the navigation keys that we'd typically use in IE. Window-Eyes isn't dead yet! It performed awesomely! I'm still using Window-Eyes for Office as well which isn't quite as up-to-date as the last version. ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.window-eyes.com%2Foptions.cgi%2Ftalk-window-eyes.com%2Fdgbowles%2540msn.comdata=02%7C01%7C%7C69166ef728cb41ece40308d82472898c%7C84df9e7fe9f640afb435%7C1%7C0%7C637299421630466476sdata=UOMHe3mBO%2FPhrW16J9qR6hiO3tTJXIikpL%2BOjktB25k%3Dreserved=0. For subscription options, visit https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.window-eyes.com%2Flistinfo.cgi%2Ftalk-window-eyes.comdata=02%7C01%7C%7C69166ef728cb41ece40308d82472898c%7C84df9e7fe9f640afb435%7C1%7C0%7C637299421630466476sdata=5ZzWqdnX8KGBz9Z87HasChoULbk%2FEH1CkGLz%2Fq9Yf54%3Dreserved=0 List archives can be found at https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.window-eyes.com%2Fprivate.cgi%2Ftalk-window-eyes.comdata=02%7C01%7C%7C69166ef728cb41ece40308d82472898c%7C84df9e7fe9f640afb435%7C1%7C0%7C637299421630466476sdata=wD5eO7n5Tc7IhRNnumcYMZrYuwJgEmpzvO0p6et4xo0%3Dreserved=0 ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/netbat%40comcast.net. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
RE: Microsoft Edge Personal
This is true. I have found an issue so far though. If you go to www.landsend.com pick your gender or other category. Then it will offer a means to break out the product selection by category such as for women, tops, bottoms, sleepwear, etc. These categories are presented as Radio Buttons but the associated text is not reading with Window-Eyes at least. Therefore, it's not readily as easy to narrow down the list to say Women's Tops or Men's Shirts, etc. I certainly will try with JAWS. I have JAWS 19 and need to upgrade it. Still, it's much more responsive so I sure will use Edge now moreso. -Original Message- From: Talk On Behalf Of Tom Kingston via Talk Sent: Thursday, July 9, 2020 10:27 PM To: Sky Mundell via Talk Cc: Tom Kingston Subject: Re: Microsoft Edge Personal It's because the new Edge uses chromium, which is to say it's the Chrome browser with Microsoft's front end on it. And making Chrome accessible was one of the last things done, but not completed, with Window-Eyes. Enjoy, Tom On 7/9/2020 9:54 PM, Sky Mundell via Talk wrote: > That's amazing! It still shows the power of the program. > > -Original Message- > From: Talk On Behalf > Of Amanda Lee via Talk > Sent: July 9, 2020 6:43 PM > To: 'Window-Eyes Discussion List' > Cc: Amanda Lee > Subject: Microsoft Edge Personal > > Hello, > > > > With this latest update of Windows 10, I was very pleasantly surprised > to see that Edge is very much changed. > > > > I know this was coming but I didn't initiate the download to install > the most current version prior to this latest Windows Update. > > > > I was amazed! To find that when I navigated to a site which causes IE > to kind of do a huge deep knees bend! > > > > Edge brought up the site up and now we can navigate with what seems to > be the majority, if not all of the navigation keys that we'd typically > use in IE. > > > > Window-Eyes isn't dead yet! It performed awesomely! > > > > I'm still using Window-Eyes for Office as well which isn't quite as > up-to-date as the last version. > > > > > > > > > > ___ > Any views or opinions presented in this email are solely those of the > author and do not necessarily represent those of Ai Squared. > > For membership options, visit > http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/skyt%40s > haw.ca > . > For subscription options, visit > http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com > List archives can be found at > http://lists.window-eyes.com/private.cgi/talk-window-eyes.com > > ___ > Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. > > For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/tom.kingston%4 0charter.net. > For subscription options, visit > http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com > List archives can be found at > http://lists.window-eyes.com/private.cgi/talk-window-eyes.com > ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/amandainparadi se777%40gmail.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
Re: Microsoft Edge Personal
It's because the new Edge uses chromium, which is to say it's the Chrome browser with Microsoft's front end on it. And making Chrome accessible was one of the last things done, but not completed, with Window-Eyes. Enjoy, Tom On 7/9/2020 9:54 PM, Sky Mundell via Talk wrote: That's amazing! It still shows the power of the program. -Original Message- From: Talk On Behalf Of Amanda Lee via Talk Sent: July 9, 2020 6:43 PM To: 'Window-Eyes Discussion List' Cc: Amanda Lee Subject: Microsoft Edge Personal Hello, With this latest update of Windows 10, I was very pleasantly surprised to see that Edge is very much changed. I know this was coming but I didn't initiate the download to install the most current version prior to this latest Windows Update. I was amazed! To find that when I navigated to a site which causes IE to kind of do a huge deep knees bend! Edge brought up the site up and now we can navigate with what seems to be the majority, if not all of the navigation keys that we'd typically use in IE. Window-Eyes isn't dead yet! It performed awesomely! I'm still using Window-Eyes for Office as well which isn't quite as up-to-date as the last version. ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/skyt%40shaw.ca . For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/tom.kingston%40charter.net. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
RE: Microsoft Edge Personal
And edge, has a reader view, that I highly recommend you try! It's an amazing bit of accessibility on microsoft's part! Darrell -Original Message- From: Talk On Behalf Of Amanda Lee via Talk Sent: Thursday, July 9, 2020 9:43 PM To: 'Window-Eyes Discussion List' Cc: Amanda Lee Subject: Microsoft Edge Personal Hello, With this latest update of Windows 10, I was very pleasantly surprised to see that Edge is very much changed. I know this was coming but I didn't initiate the download to install the most current version prior to this latest Windows Update. I was amazed! To find that when I navigated to a site which causes IE to kind of do a huge deep knees bend! Edge brought up the site up and now we can navigate with what seems to be the majority, if not all of the navigation keys that we'd typically use in IE. Window-Eyes isn't dead yet! It performed awesomely! I'm still using Window-Eyes for Office as well which isn't quite as up-to-date as the last version. ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.window-eyes.com%2Foptions.cgi%2Ftalk-window-eyes.com%2Fdgbowles%2540msn.comdata=02%7C01%7C%7C69166ef728cb41ece40308d82472898c%7C84df9e7fe9f640afb435%7C1%7C0%7C637299421630466476sdata=UOMHe3mBO%2FPhrW16J9qR6hiO3tTJXIikpL%2BOjktB25k%3Dreserved=0. For subscription options, visit https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.window-eyes.com%2Flistinfo.cgi%2Ftalk-window-eyes.comdata=02%7C01%7C%7C69166ef728cb41ece40308d82472898c%7C84df9e7fe9f640afb435%7C1%7C0%7C637299421630466476sdata=5ZzWqdnX8KGBz9Z87HasChoULbk%2FEH1CkGLz%2Fq9Yf54%3Dreserved=0 List archives can be found at https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.window-eyes.com%2Fprivate.cgi%2Ftalk-window-eyes.comdata=02%7C01%7C%7C69166ef728cb41ece40308d82472898c%7C84df9e7fe9f640afb435%7C1%7C0%7C637299421630466476sdata=wD5eO7n5Tc7IhRNnumcYMZrYuwJgEmpzvO0p6et4xo0%3Dreserved=0 ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
RE: Microsoft Edge Personal
That's amazing! It still shows the power of the program. -Original Message- From: Talk On Behalf Of Amanda Lee via Talk Sent: July 9, 2020 6:43 PM To: 'Window-Eyes Discussion List' Cc: Amanda Lee Subject: Microsoft Edge Personal Hello, With this latest update of Windows 10, I was very pleasantly surprised to see that Edge is very much changed. I know this was coming but I didn't initiate the download to install the most current version prior to this latest Windows Update. I was amazed! To find that when I navigated to a site which causes IE to kind of do a huge deep knees bend! Edge brought up the site up and now we can navigate with what seems to be the majority, if not all of the navigation keys that we'd typically use in IE. Window-Eyes isn't dead yet! It performed awesomely! I'm still using Window-Eyes for Office as well which isn't quite as up-to-date as the last version. ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/skyt%40shaw.ca . For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
Microsoft Edge Personal
Hello, With this latest update of Windows 10, I was very pleasantly surprised to see that Edge is very much changed. I know this was coming but I didn't initiate the download to install the most current version prior to this latest Windows Update. I was amazed! To find that when I navigated to a site which causes IE to kind of do a huge deep knees bend! Edge brought up the site up and now we can navigate with what seems to be the majority, if not all of the navigation keys that we'd typically use in IE. Window-Eyes isn't dead yet! It performed awesomely! I'm still using Window-Eyes for Office as well which isn't quite as up-to-date as the last version. ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
RE: microsoft edge support:
Absolutely. Although, I will say that, having a built in screen reader, like Apple does, would have made getting jobs easier and that would have ensured that employers wouldn't have to go spending out for a screen reader. The other advantage of MS having Narrator is that they can control and test for accessibility using Narrator. However, there is a downside to this. The downside is that if you want tech support with Narrator, you won't be able to get it. Also, Narrator in windows 10 doesn't have braille display support, scripting, etc, etc, etc, like JAWS, Window-Eyes, or NVDA does. I think their will still be a need for 3rd party screen readers to exist. You guys should also be aware that Microsoft has blind people working for them as well. One guy that works for them is named Kelly ford. -Original Message- From: Talk [mailto:talk-bounces+skyt=shaw...@lists.window-eyes.com] On Behalf Of Vaughan Dodd via Talk Sent: Thursday, November 03, 2016 12:32 PM To: 'Don H'; 'Window-Eyes Discussion List' Subject: RE: microsoft edge support: Agree with the below. Adding that Promoting Narrator as being friendly with the Edge browser was an insult to people who use far better screen readers, such as Window-Eyes. Becausew there appears to be no hurry to have Edge available to specialist screen reader developers, and also given that internet Explorer is now legacy, Microsoft is insideously shutting us out of cutting edge web developments, and making it almost impossible for screen reader manufacturers to continue to develop products which respond to today's (and tomorrow's) access requirements. Vaughan. -Original Message- From: Talk [mailto:talk-bounces+vaughan.dodd001=msd.govt...@lists.window-eyes.com] On Behalf Of Don H via Talk Sent: Friday, 4 November 2016 1:55 a.m. To: p.wildcat1...@gmail.com; Window-Eyes Discussion List Subject: Re: microsoft edge support: I would bet not soon if ever. On 11/2/2016 8:04 PM, via Talk wrote: > Hi when will Microsoft edge support be available in window-eyes? > Kenny Peyatt jr. > > Sent from Mail for Windows 10 > > ___ > Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. > > For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/lmddh50%40comc ast.net. > For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com > List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com > ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/vaughan.dodd00 1%40msd.govt.nz. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com --- This email and any attachments may contain information that is confidential and subject to legal privilege. If you are not the intended recipient, any use, dissemination, distribution or duplication of this email and attachments is prohibited. If you have received this email in error please notify the author immediately and erase all copies of the email and attachments. The Ministry of Social Development accepts no responsibility for changes made to this message or attachments after transmission from the Ministry. --- ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/skyt%40shaw.ca . For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
RE: microsoft edge support:
Agree with the below. Adding that Promoting Narrator as being friendly with the Edge browser was an insult to people who use far better screen readers, such as Window-Eyes. Becausew there appears to be no hurry to have Edge available to specialist screen reader developers, and also given that internet Explorer is now legacy, Microsoft is insideously shutting us out of cutting edge web developments, and making it almost impossible for screen reader manufacturers to continue to develop products which respond to today's (and tomorrow's) access requirements. Vaughan. -Original Message- From: Talk [mailto:talk-bounces+vaughan.dodd001=msd.govt...@lists.window-eyes.com] On Behalf Of Don H via Talk Sent: Friday, 4 November 2016 1:55 a.m. To: p.wildcat1...@gmail.com; Window-Eyes Discussion List Subject: Re: microsoft edge support: I would bet not soon if ever. On 11/2/2016 8:04 PM, via Talk wrote: > Hi when will Microsoft edge support be available in window-eyes? > Kenny Peyatt jr. > > Sent from Mail for Windows 10 > > ___ > Any views or opinions presented in this email are solely those of the author > and do not necessarily represent those of Ai Squared. > > For membership options, visit > http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/lmddh50%40comcast.net. > For subscription options, visit > http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com > List archives can be found at > http://lists.window-eyes.com/private.cgi/talk-window-eyes.com > ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/vaughan.dodd001%40msd.govt.nz. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com --- This email and any attachments may contain information that is confidential and subject to legal privilege. If you are not the intended recipient, any use, dissemination, distribution or duplication of this email and attachments is prohibited. If you have received this email in error please notify the author immediately and erase all copies of the email and attachments. The Ministry of Social Development accepts no responsibility for changes made to this message or attachments after transmission from the Ministry. --- ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
Re: microsoft edge support:
I would bet not soon if ever. On 11/2/2016 8:04 PM, via Talk wrote: Hi when will Microsoft edge support be available in window-eyes? Kenny Peyatt jr. Sent from Mail for Windows 10 ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/lmddh50%40comcast.net. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
microsoft edge support:
Hi when will Microsoft edge support be available in window-eyes? Kenny Peyatt jr. Sent from Mail for Windows 10 ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
RE: update on Microsoft Edge (my final response on this thread, maybe? )
Could you folks who have a problem contact your congressman / woman and do something constructive instead of clogging up the list with allot of nonproductive noise? That or do some homework and make productive suggestions instead of just flaming people and companies? I am getting well over a hundred hits from this list every week and 90 percent of it is junk mail from folks just looking for someplace to spout their frustrations with no value of any thought. Thanks for your professionalism. Rick USA -Original Message- From: Talk [mailto:talk-bounces+ofbgmail=mi.rr@lists.window-eyes.com] On Behalf Of Kevin Huber via Talk Sent: Wednesday, August 3, 2016 11:03 AM To: Marc Solomon <msolo...@aisquared.com>; Window-Eyes Discussion List <talk@lists.window-eyes.com> Subject: Re: update on Microsoft Edge (my final response on this thread, maybe? ) Amen Mark! Sometimes we all get too impatient because we think that we are being ignored by the Microsofts of the world when they are actually working hard behind the scenes to make their products more usable and accessible for all of us. Kevin Huber On 8/2/16, Marc Solomon via Talk <talk@lists.window-eyes.com> wrote: > Fact 6, Rome was not built in a day. Does that mean Rome doesn't exist > today? In other words, accessibility is not trivial to implement. In fact, > it is downright hard to do and requires the efforts of brilliant and > passionate engineers. I sure wish you could appreciate that fact if no > other. Recognizing this truth might encourage you to stop attacking the > people that are trying to help. In closing, can't we all just get along? > > Sent with AquaMail for Android > http://www.aqua-mail.com > > On August 2, 2016 7:53:00 PM Kevin Barry <krba...@gmail.com> wrote: > > fact number five, the edge browser is not accessible to screen readers. > Making your fax immaterial > > On Wednesday, August 3, 2016, Marc Solomon via Talk > <talk@lists.window-eyes.com<mailto:talk@lists.window-eyes.com>> wrote: > Hi Vaughn, > Regretfully, I don't have any specifics to share regarding how close > Window-Eyes is to adding official support for Edge. But, the advancements we > are seeing in Edge seem like a good indicator that 3rd party screen reader > support is not too far off in the distance. > Best, > Marc > > Sent with AquaMail for Android > http://www.aqua-mail.com > > > On August 2, 2016 7:23:53 PM Vaughan Dodd > <vaughan.dodd...@msd.govt.nz<javascript:;>> wrote: > >> Hi Marc. >> >> I'm perhaps tempting fate - are you signaling that in fact, Window-eyes is >> close to having the interface we need? >> >> I can check for myself as to the real user's experience of course when the >> anniversary of Windows 10 gets to a machine near me. >> >> Vaughan. >> >> >> Understand if non-disclosure still applies. >> >> Vaughan. >> >> >> >> Please telephone the Regional Disability and Health Team prior to emailing >> or faxing any new referrals. >> >> Vaughan Dodd, Regional Disability Advisor. >> >> Desk2desk: 97187. >> Email: vaughan.dodd...@msd.govt.nz<javascript:;>. >> For referrals: email >> fax_gnlis001_health_disabil...@msd.govt.nz<javascript:;>. >> >> Our up-to-date desk file is located at: >> http://doogle.ssi.govt.nz/resources/publications/reports-research/regional/auckland/auckland-health-disability-resources.html >> >> >> -Original Message- >> From: Talk >> [mailto:talk-bounces+vaughan.dodd001<javascript:;>=msd.govt...@lists.window-eyes.com<javascript:;>] >> On Behalf Of Marc Solomon via Talk >> Sent: Wednesday, 3 August 2016 11:07 a.m. >> To: Kevin Barry >> Cc: Window-Eyes Discussion List >> Subject: RE: update on Microsoft Edge (my final response on this thread, I >> promise ) >> >> Fact number 1: Microsoft Edge used to accessibly support 0 percent of >> HTML5 features. >> Fact number 2: In less than 12 months, Microsoft Edge now accessibly >> supports 100 percent of HTML5 features. >> Fact number 3: Microsoft Edge now accessibly supports more HTML5 features >> than any other major browser. >> Fact number 4: Web browsers accessibly supporting HTML5 features will make >> the web more usable for people who use assistive technology including >> screen reader users >> Source: >> www.html5accessibility.com<http://www.html5accessibility.com><http://www.html5accessibility.com> >> (curated by The Paciello Group, a globally recognized leader in digital >> accessibility) Explanation of terms – HTML5 features “accessibly >> supported” by a web
Re: update on Microsoft Edge (my final response on this thread, maybe? )
There's a very big difference between not trashing Microsoft, and spouting there nonsensical party line. On Wednesday, August 3, 2016, Jim via Talk <talk@lists.window-eyes.com> wrote: > That's very tru! I think we should all just set back and wait and see what > happens. Personally I would like to see a product that functions well even > if it takes more time to produce it. There is no real reason for them to > release a product that is going to have to be continually updated an > repaired for weeks and or months. I have gotten edge to work to some > degree and what I have saw I have liked. Just be patient for a while > longer and we might all be surprised! P.S. If I am not correct please > remember that I didn't make any promises<SMILE!>. Catch Ya All Later! de > > . > > > On 02-Aug-16 20:54, Marc Solomon via Talk wrote: > >> Fact 6, Rome was not built in a day. Does that mean Rome doesn't exist >> today? In other words, accessibility is not trivial to implement. In fact, >> it is downright hard to do and requires the efforts of brilliant and >> passionate engineers. I sure wish you could appreciate that fact if no >> other. Recognizing this truth might encourage you to stop attacking the >> people that are trying to help. In closing, can't we all just get along? >> >> Sent with AquaMail for Android >> http://www.aqua-mail.com >> >> On August 2, 2016 7:53:00 PM Kevin Barry <krba...@gmail.com> wrote: >> >> fact number five, the edge browser is not accessible to screen readers. >> Making your fax immaterial >> >> On Wednesday, August 3, 2016, Marc Solomon via Talk < >> talk@lists.window-eyes.com<mailto:talk@lists.window-eyes.com>> wrote: >> Hi Vaughn, >> Regretfully, I don't have any specifics to share regarding how close >> Window-Eyes is to adding official support for Edge. But, the advancements >> we are seeing in Edge seem like a good indicator that 3rd party screen >> reader support is not too far off in the distance. >> Best, >> Marc >> >> Sent with AquaMail for Android >> http://www.aqua-mail.com >> >> >> On August 2, 2016 7:23:53 PM Vaughan Dodd >> <vaughan.dodd...@msd.govt.nz<javascript:;>> >> wrote: >> >> Hi Marc. >>> >>> I'm perhaps tempting fate - are you signaling that in fact, Window-eyes >>> is close to having the interface we need? >>> >>> I can check for myself as to the real user's experience of course when >>> the anniversary of Windows 10 gets to a machine near me. >>> >>> Vaughan. >>> >>> >>> Understand if non-disclosure still applies. >>> >>> Vaughan. >>> >>> >>> >>> Please telephone the Regional Disability and Health Team prior to >>> emailing or faxing any new referrals. >>> >>> Vaughan Dodd, Regional Disability Advisor. >>> >>> Desk2desk: 97187. >>> Email: vaughan.dodd...@msd.govt.nz<javascript:;>. >>> For referrals: email fax_gnlis001_health_disabil...@msd.govt.nz >>> <javascript:;>. >>> >>> Our up-to-date desk file is located at: >>> >>> http://doogle.ssi.govt.nz/resources/publications/reports-research/regional/auckland/auckland-health-disability-resources.html >>> >>> >>> -Original Message- >>> From: Talk [mailto:talk-bounces+vaughan.dodd001<javascript:;>= >>> msd.govt...@lists.window-eyes.com<javascript:;>] On Behalf Of Marc >>> Solomon via Talk >>> Sent: Wednesday, 3 August 2016 11:07 a.m. >>> To: Kevin Barry >>> Cc: Window-Eyes Discussion List >>> Subject: RE: update on Microsoft Edge (my final response on this thread, >>> I promise ) >>> >>> Fact number 1: Microsoft Edge used to accessibly support 0 percent of >>> HTML5 features. >>> Fact number 2: In less than 12 months, Microsoft Edge now accessibly >>> supports 100 percent of HTML5 features. >>> Fact number 3: Microsoft Edge now accessibly supports more HTML5 >>> features than any other major browser. >>> Fact number 4: Web browsers accessibly supporting HTML5 features will >>> make the web more usable for people who use assistive technology including >>> screen reader users >>> Source: www.html5accessibility.com<http://www.html5accessibility.com>< >>> http://www.html5accessibility.com> (curated by The Paciello Group, a >>> globally recognized leader in digital accessibility) Explanation of terms – >>>
Re: update on Microsoft Edge (my final response on this thread, maybe? )
That's very tru! I think we should all just set back and wait and see what happens. Personally I would like to see a product that functions well even if it takes more time to produce it. There is no real reason for them to release a product that is going to have to be continually updated an repaired for weeks and or months. I have gotten edge to work to some degree and what I have saw I have liked. Just be patient for a while longer and we might all be surprised! P.S. If I am not correct please remember that I didn't make any promises<SMILE!>. Catch Ya All Later! de . On 02-Aug-16 20:54, Marc Solomon via Talk wrote: Fact 6, Rome was not built in a day. Does that mean Rome doesn't exist today? In other words, accessibility is not trivial to implement. In fact, it is downright hard to do and requires the efforts of brilliant and passionate engineers. I sure wish you could appreciate that fact if no other. Recognizing this truth might encourage you to stop attacking the people that are trying to help. In closing, can't we all just get along? Sent with AquaMail for Android http://www.aqua-mail.com On August 2, 2016 7:53:00 PM Kevin Barry <krba...@gmail.com> wrote: fact number five, the edge browser is not accessible to screen readers. Making your fax immaterial On Wednesday, August 3, 2016, Marc Solomon via Talk <talk@lists.window-eyes.com<mailto:talk@lists.window-eyes.com>> wrote: Hi Vaughn, Regretfully, I don't have any specifics to share regarding how close Window-Eyes is to adding official support for Edge. But, the advancements we are seeing in Edge seem like a good indicator that 3rd party screen reader support is not too far off in the distance. Best, Marc Sent with AquaMail for Android http://www.aqua-mail.com On August 2, 2016 7:23:53 PM Vaughan Dodd <vaughan.dodd...@msd.govt.nz<javascript:;>> wrote: Hi Marc. I'm perhaps tempting fate - are you signaling that in fact, Window-eyes is close to having the interface we need? I can check for myself as to the real user's experience of course when the anniversary of Windows 10 gets to a machine near me. Vaughan. Understand if non-disclosure still applies. Vaughan. Please telephone the Regional Disability and Health Team prior to emailing or faxing any new referrals. Vaughan Dodd, Regional Disability Advisor. Desk2desk: 97187. Email: vaughan.dodd...@msd.govt.nz<javascript:;>. For referrals: email fax_gnlis001_health_disabil...@msd.govt.nz<javascript:;>. Our up-to-date desk file is located at: http://doogle.ssi.govt.nz/resources/publications/reports-research/regional/auckland/auckland-health-disability-resources.html -Original Message- From: Talk [mailto:talk-bounces+vaughan.dodd001<javascript:;>=msd.govt...@lists.window-eyes.com<javascript:;>] On Behalf Of Marc Solomon via Talk Sent: Wednesday, 3 August 2016 11:07 a.m. To: Kevin Barry Cc: Window-Eyes Discussion List Subject: RE: update on Microsoft Edge (my final response on this thread, I promise ) Fact number 1: Microsoft Edge used to accessibly support 0 percent of HTML5 features. Fact number 2: In less than 12 months, Microsoft Edge now accessibly supports 100 percent of HTML5 features. Fact number 3: Microsoft Edge now accessibly supports more HTML5 features than any other major browser. Fact number 4: Web browsers accessibly supporting HTML5 features will make the web more usable for people who use assistive technology including screen reader users Source: www.html5accessibility.com<http://www.html5accessibility.com><http://www.html5accessibility.com> (curated by The Paciello Group, a globally recognized leader in digital accessibility) Explanation of terms – HTML5 features “accessibly supported” by a web browser includes if they are keyboard accessible, mapped to the platform accessibility APIs, and if any accessibility related features are supported. An accessibly supported feature means it is usable by people who rely on assistive technology, without developers having to supplement with ARIA or other additional workarounds. From: Kevin Barry [mailto:krba...@gmail.com<javascript:;>] Sent: Tuesday, August 2, 2016 6:23 PM To: Marc Solomon <msolo...@aisquared.com<javascript:;>> Cc: Rick Thomas <ofbgm...@mi.rr.com<javascript:;>>; Window-Eyes Discussion List <talk@lists.window-eyes.com<javascript:;>>; Portia Scott <porti...@sbcglobal.net<javascript:;>> Subject: Re: update on Microsoft Edge As soon as Microsoft make some progress, please share it with us. In the meantime, please stop apologizing for their inexcusable choices. On Wednesday, August 3, 2016, Marc Solomon <msolo...@aisquared.com<javascript:;><mailto:msolo...@aisquared.com<javascript:;>>> wrote: Kevin, You are entitled to your opinion. As an advocate for the screen reader and accessibility communities, I bel
Re: update on Microsoft Edge (my final response on this thread, maybe? )
Sent from my iPhone On Aug 2, 2016, at 8:54 PM, Marc Solomon via Talk <talk@lists.window-eyes.com> wrote: Fact 6, Rome was not built in a day. Does that mean Rome doesn't exist today? In other words, accessibility is not trivial to implement. In fact, it is downright hard to do and requires the efforts of brilliant and passionate engineers. I sure wish you could appreciate that fact if no other. Recognizing this truth might encourage you to stop attacking the people that are trying to help. In closing, can't we all just get along? Sent with AquaMail for Android http://www.aqua-mail.com On August 2, 2016 7:53:00 PM Kevin Barry <krba...@gmail.com> wrote: fact number five, the edge browser is not accessible to screen readers. Making your fax immaterial On Wednesday, August 3, 2016, Marc Solomon via Talk <talk@lists.window-eyes.com<mailto:talk@lists.window-eyes.com>> wrote: Hi Vaughn, Regretfully, I don't have any specifics to share regarding how close Window-Eyes is to adding official support for Edge. But, the advancements we are seeing in Edge seem like a good indicator that 3rd party screen reader support is not too far off in the distance. Best, Marc Sent with AquaMail for Android http://www.aqua-mail.com > On August 2, 2016 7:23:53 PM Vaughan Dodd > <vaughan.dodd...@msd.govt.nz<javascript:;>> wrote: > > Hi Marc. > > I'm perhaps tempting fate - are you signaling that in fact, Window-eyes is > close to having the interface we need? > > I can check for myself as to the real user's experience of course when the > anniversary of Windows 10 gets to a machine near me. > > Vaughan. > > > Understand if non-disclosure still applies. > > Vaughan. > > > > Please telephone the Regional Disability and Health Team prior to emailing or > faxing any new referrals. > > Vaughan Dodd, Regional Disability Advisor. > > Desk2desk: 97187. > Email: vaughan.dodd...@msd.govt.nz<javascript:;>. > For referrals: email fax_gnlis001_health_disabil...@msd.govt.nz<javascript:;>. > > Our up-to-date desk file is located at: > http://doogle.ssi.govt.nz/resources/publications/reports-research/regional/auckland/auckland-health-disability-resources.html > > > -Original Message- > From: Talk > [mailto:talk-bounces+vaughan.dodd001<javascript:;>=msd.govt...@lists.window-eyes.com<javascript:;>] > On Behalf Of Marc Solomon via Talk > Sent: Wednesday, 3 August 2016 11:07 a.m. > To: Kevin Barry > Cc: Window-Eyes Discussion List > Subject: RE: update on Microsoft Edge (my final response on this thread, I > promise ) > > Fact number 1: Microsoft Edge used to accessibly support 0 percent of HTML5 > features. > Fact number 2: In less than 12 months, Microsoft Edge now accessibly supports > 100 percent of HTML5 features. > Fact number 3: Microsoft Edge now accessibly supports more HTML5 features > than any other major browser. > Fact number 4: Web browsers accessibly supporting HTML5 features will make > the web more usable for people who use assistive technology including screen > reader users > Source: > www.html5accessibility.com<http://www.html5accessibility.com><http://www.html5accessibility.com> > (curated by The Paciello Group, a globally recognized leader in digital > accessibility) Explanation of terms – HTML5 features “accessibly supported” > by a web browser includes if they are keyboard accessible, mapped to the > platform accessibility APIs, and if any accessibility related features are > supported. An accessibly supported feature means it is usable by people who > rely on assistive technology, without developers having to supplement with > ARIA or other additional workarounds. > > From: Kevin Barry [mailto:krba...@gmail.com<javascript:;>] > Sent: Tuesday, August 2, 2016 6:23 PM > To: Marc Solomon <msolo...@aisquared.com<javascript:;>> > Cc: Rick Thomas <ofbgm...@mi.rr.com<javascript:;>>; Window-Eyes Discussion > List <talk@lists.window-eyes.com<javascript:;>>; Portia Scott > <porti...@sbcglobal.net<javascript:;>> > Subject: Re: update on Microsoft Edge > > As soon as Microsoft make some progress, please share it with us. In the > meantime, please stop apologizing for their inexcusable choices. > > On Wednesday, August 3, 2016, Marc Solomon > <msolo...@aisquared.com<javascript:;><mailto:msolo...@aisquared.com<javascript:;>>> > wrote: > Kevin, > You are entitled to your opinion. As an advocate for the screen reader and > accessibility communities, I believe that constructive dialogue, eduction, > and cooperation is a formula for positive change. I will continue to share > facts a
RE: update on Microsoft Edge (my final response on this thread, maybe? )
Hey guys: whilst I'm cynical about Microsoft's commitment, we have to understand that AI Squared staffers cannot use this list to flame Microsoft. Their employer has a professional relationship with MS, and whilst users can and do express opinions contrary to those of AI Squared employees, it would just be bad form for Marc et al to join the anti Microsoft band wagon. If they did, MS will simply put its energies into other activities which would not advance the cause of Window-eyes users. Vaughan. -Original Message- From: Talk [mailto:talk-bounces+vaughan.dodd001=msd.govt...@lists.window-eyes.com] On Behalf Of Nick Sarames via Talk Sent: Wednesday, 3 August 2016 1:03 p.m. To: Marc Solomon; Window-Eyes Discussion List; Kevin Barry Subject: Re: update on Microsoft Edge (my final response on this thread, maybe? ) Not to mention that there are varying degrees of what accessibility means to a user. This doesn't mean there aren't standards, only that I don't need every feature to be accessible in order for me to use the product. On 8/2/2016 8:54 PM, Marc Solomon via Talk wrote: > Fact 6, Rome was not built in a day. Does that mean Rome doesn't exist today? > In other words, accessibility is not trivial to implement. In fact, it is > downright hard to do and requires the efforts of brilliant and passionate > engineers. I sure wish you could appreciate that fact if no other. > Recognizing this truth might encourage you to stop attacking the people that > are trying to help. In closing, can't we all just get along? > > Sent with AquaMail for Android > http://www.aqua-mail.com > > On August 2, 2016 7:53:00 PM Kevin Barry <krba...@gmail.com> wrote: > > fact number five, the edge browser is not accessible to screen > readers. Making your fax immaterial > > On Wednesday, August 3, 2016, Marc Solomon via Talk > <talk@lists.window-eyes.com<mailto:talk@lists.window-eyes.com>> wrote: > Hi Vaughn, > Regretfully, I don't have any specifics to share regarding how close > Window-Eyes is to adding official support for Edge. But, the advancements we > are seeing in Edge seem like a good indicator that 3rd party screen reader > support is not too far off in the distance. > Best, > Marc > > Sent with AquaMail for Android > http://www.aqua-mail.com > > > On August 2, 2016 7:23:53 PM Vaughan Dodd > <vaughan.dodd...@msd.govt.nz<javascript:;>> wrote: > >> Hi Marc. >> >> I'm perhaps tempting fate - are you signaling that in fact, Window-eyes is >> close to having the interface we need? >> >> I can check for myself as to the real user's experience of course when the >> anniversary of Windows 10 gets to a machine near me. >> >> Vaughan. >> >> >> Understand if non-disclosure still applies. >> >> Vaughan. >> >> >> >> Please telephone the Regional Disability and Health Team prior to emailing >> or faxing any new referrals. >> >> Vaughan Dodd, Regional Disability Advisor. >> >> Desk2desk: 97187. >> Email: vaughan.dodd...@msd.govt.nz<javascript:;>. >> For referrals: email >> fax_gnlis001_health_disabil...@msd.govt.nz<javascript:;>. >> >> Our up-to-date desk file is located at: >> http://doogle.ssi.govt.nz/resources/publications/reports-research/reg >> ional/auckland/auckland-health-disability-resources.html >> >> >> -Original Message- >> From: Talk >> [mailto:talk-bounces+vaughan.dodd001<javascript:;>=msd.govt.nz@lists. >> window-eyes.com<javascript:;>] On Behalf Of Marc Solomon via Talk >> Sent: Wednesday, 3 August 2016 11:07 a.m. >> To: Kevin Barry >> Cc: Window-Eyes Discussion List >> Subject: RE: update on Microsoft Edge (my final response on this >> thread, I promise ) >> >> Fact number 1: Microsoft Edge used to accessibly support 0 percent of HTML5 >> features. >> Fact number 2: In less than 12 months, Microsoft Edge now accessibly >> supports 100 percent of HTML5 features. >> Fact number 3: Microsoft Edge now accessibly supports more HTML5 features >> than any other major browser. >> Fact number 4: Web browsers accessibly supporting HTML5 features will >> make the web more usable for people who use assistive technology >> including screen reader users >> Source: >> www.html5accessibility.com<http://www.html5accessibility.com><http://www.html5accessibility.com> >> (curated by The Paciello Group, a globally recognized leader in digital >> accessibility) Explanation of terms - HTML5 features "accessibly supported" >> by a web browser includes if they are keyboard accessible,
Re: update on Microsoft Edge (my final response on this thread, maybe? )
Not to mention that there are varying degrees of what accessibility means to a user. This doesn't mean there aren't standards, only that I don't need every feature to be accessible in order for me to use the product. On 8/2/2016 8:54 PM, Marc Solomon via Talk wrote: > Fact 6, Rome was not built in a day. Does that mean Rome doesn't exist today? > In other words, accessibility is not trivial to implement. In fact, it is > downright hard to do and requires the efforts of brilliant and passionate > engineers. I sure wish you could appreciate that fact if no other. > Recognizing this truth might encourage you to stop attacking the people that > are trying to help. In closing, can't we all just get along? > > Sent with AquaMail for Android > http://www.aqua-mail.com > > On August 2, 2016 7:53:00 PM Kevin Barry <krba...@gmail.com> wrote: > > fact number five, the edge browser is not accessible to screen readers. > Making your fax immaterial > > On Wednesday, August 3, 2016, Marc Solomon via Talk > <talk@lists.window-eyes.com<mailto:talk@lists.window-eyes.com>> wrote: > Hi Vaughn, > Regretfully, I don't have any specifics to share regarding how close > Window-Eyes is to adding official support for Edge. But, the advancements we > are seeing in Edge seem like a good indicator that 3rd party screen reader > support is not too far off in the distance. > Best, > Marc > > Sent with AquaMail for Android > http://www.aqua-mail.com > > > On August 2, 2016 7:23:53 PM Vaughan Dodd > <vaughan.dodd...@msd.govt.nz<javascript:;>> wrote: > >> Hi Marc. >> >> I'm perhaps tempting fate - are you signaling that in fact, Window-eyes is >> close to having the interface we need? >> >> I can check for myself as to the real user's experience of course when the >> anniversary of Windows 10 gets to a machine near me. >> >> Vaughan. >> >> >> Understand if non-disclosure still applies. >> >> Vaughan. >> >> >> >> Please telephone the Regional Disability and Health Team prior to emailing >> or faxing any new referrals. >> >> Vaughan Dodd, Regional Disability Advisor. >> >> Desk2desk: 97187. >> Email: vaughan.dodd...@msd.govt.nz<javascript:;>. >> For referrals: email >> fax_gnlis001_health_disabil...@msd.govt.nz<javascript:;>. >> >> Our up-to-date desk file is located at: >> http://doogle.ssi.govt.nz/resources/publications/reports-research/regional/auckland/auckland-health-disability-resources.html >> >> >> -Original Message- >> From: Talk >> [mailto:talk-bounces+vaughan.dodd001<javascript:;>=msd.govt...@lists.window-eyes.com<javascript:;>] >> On Behalf Of Marc Solomon via Talk >> Sent: Wednesday, 3 August 2016 11:07 a.m. >> To: Kevin Barry >> Cc: Window-Eyes Discussion List >> Subject: RE: update on Microsoft Edge (my final response on this thread, I >> promise ) >> >> Fact number 1: Microsoft Edge used to accessibly support 0 percent of HTML5 >> features. >> Fact number 2: In less than 12 months, Microsoft Edge now accessibly >> supports 100 percent of HTML5 features. >> Fact number 3: Microsoft Edge now accessibly supports more HTML5 features >> than any other major browser. >> Fact number 4: Web browsers accessibly supporting HTML5 features will make >> the web more usable for people who use assistive technology including screen >> reader users >> Source: >> www.html5accessibility.com<http://www.html5accessibility.com><http://www.html5accessibility.com> >> (curated by The Paciello Group, a globally recognized leader in digital >> accessibility) Explanation of terms – HTML5 features “accessibly supported” >> by a web browser includes if they are keyboard accessible, mapped to the >> platform accessibility APIs, and if any accessibility related features are >> supported. An accessibly supported feature means it is usable by people who >> rely on assistive technology, without developers having to supplement with >> ARIA or other additional workarounds. >> >> From: Kevin Barry [mailto:krba...@gmail.com<javascript:;>] >> Sent: Tuesday, August 2, 2016 6:23 PM >> To: Marc Solomon <msolo...@aisquared.com<javascript:;>> >> Cc: Rick Thomas <ofbgm...@mi.rr.com<javascript:;>>; Window-Eyes Discussion >> List <talk@lists.window-eyes.com<javascript:;>>; Portia Scott >> <porti...@sbcglobal.net<javascript:;>> >> Subject: Re: update on Microsoft Edge >> >> As soon as Microsoft make some p
Re: update on Microsoft Edge (my final response on this thread, maybe? )
Fact 6, Rome was not built in a day. Does that mean Rome doesn't exist today? In other words, accessibility is not trivial to implement. In fact, it is downright hard to do and requires the efforts of brilliant and passionate engineers. I sure wish you could appreciate that fact if no other. Recognizing this truth might encourage you to stop attacking the people that are trying to help. In closing, can't we all just get along? Sent with AquaMail for Android http://www.aqua-mail.com On August 2, 2016 7:53:00 PM Kevin Barry <krba...@gmail.com> wrote: fact number five, the edge browser is not accessible to screen readers. Making your fax immaterial On Wednesday, August 3, 2016, Marc Solomon via Talk <talk@lists.window-eyes.com<mailto:talk@lists.window-eyes.com>> wrote: Hi Vaughn, Regretfully, I don't have any specifics to share regarding how close Window-Eyes is to adding official support for Edge. But, the advancements we are seeing in Edge seem like a good indicator that 3rd party screen reader support is not too far off in the distance. Best, Marc Sent with AquaMail for Android http://www.aqua-mail.com On August 2, 2016 7:23:53 PM Vaughan Dodd <vaughan.dodd...@msd.govt.nz<javascript:;>> wrote: > Hi Marc. > > I'm perhaps tempting fate - are you signaling that in fact, Window-eyes is > close to having the interface we need? > > I can check for myself as to the real user's experience of course when the > anniversary of Windows 10 gets to a machine near me. > > Vaughan. > > > Understand if non-disclosure still applies. > > Vaughan. > > > > Please telephone the Regional Disability and Health Team prior to emailing or > faxing any new referrals. > > Vaughan Dodd, Regional Disability Advisor. > > Desk2desk: 97187. > Email: vaughan.dodd...@msd.govt.nz<javascript:;>. > For referrals: email fax_gnlis001_health_disabil...@msd.govt.nz<javascript:;>. > > Our up-to-date desk file is located at: > http://doogle.ssi.govt.nz/resources/publications/reports-research/regional/auckland/auckland-health-disability-resources.html > > > -Original Message- > From: Talk > [mailto:talk-bounces+vaughan.dodd001<javascript:;>=msd.govt...@lists.window-eyes.com<javascript:;>] > On Behalf Of Marc Solomon via Talk > Sent: Wednesday, 3 August 2016 11:07 a.m. > To: Kevin Barry > Cc: Window-Eyes Discussion List > Subject: RE: update on Microsoft Edge (my final response on this thread, I > promise ) > > Fact number 1: Microsoft Edge used to accessibly support 0 percent of HTML5 > features. > Fact number 2: In less than 12 months, Microsoft Edge now accessibly supports > 100 percent of HTML5 features. > Fact number 3: Microsoft Edge now accessibly supports more HTML5 features > than any other major browser. > Fact number 4: Web browsers accessibly supporting HTML5 features will make > the web more usable for people who use assistive technology including screen > reader users > Source: > www.html5accessibility.com<http://www.html5accessibility.com><http://www.html5accessibility.com> > (curated by The Paciello Group, a globally recognized leader in digital > accessibility) Explanation of terms – HTML5 features “accessibly supported” > by a web browser includes if they are keyboard accessible, mapped to the > platform accessibility APIs, and if any accessibility related features are > supported. An accessibly supported feature means it is usable by people who > rely on assistive technology, without developers having to supplement with > ARIA or other additional workarounds. > > From: Kevin Barry [mailto:krba...@gmail.com<javascript:;>] > Sent: Tuesday, August 2, 2016 6:23 PM > To: Marc Solomon <msolo...@aisquared.com<javascript:;>> > Cc: Rick Thomas <ofbgm...@mi.rr.com<javascript:;>>; Window-Eyes Discussion > List <talk@lists.window-eyes.com<javascript:;>>; Portia Scott > <porti...@sbcglobal.net<javascript:;>> > Subject: Re: update on Microsoft Edge > > As soon as Microsoft make some progress, please share it with us. In the > meantime, please stop apologizing for their inexcusable choices. > > On Wednesday, August 3, 2016, Marc Solomon > <msolo...@aisquared.com<javascript:;><mailto:msolo...@aisquared.com<javascript:;>>> > wrote: > Kevin, > You are entitled to your opinion. As an advocate for the screen reader and > accessibility communities, I believe that constructive dialogue, eduction, > and cooperation is a formula for positive change. I will continue to share > facts about the progress being made by Microsoft in the realm of > accessibility. And, I sincerely hope that in the near future users of screen >
RE: update on Microsoft Edge (my final response on this thread, I promise )
Hi Vaughn, Regretfully, I don't have any specifics to share regarding how close Window-Eyes is to adding official support for Edge. But, the advancements we are seeing in Edge seem like a good indicator that 3rd party screen reader support is not too far off in the distance. Best, Marc Sent with AquaMail for Android http://www.aqua-mail.com On August 2, 2016 7:23:53 PM Vaughan Dodd <vaughan.dodd...@msd.govt.nz> wrote: > Hi Marc. > > I'm perhaps tempting fate - are you signaling that in fact, Window-eyes is > close to having the interface we need? > > I can check for myself as to the real user's experience of course when the > anniversary of Windows 10 gets to a machine near me. > > Vaughan. > > > Understand if non-disclosure still applies. > > Vaughan. > > > > Please telephone the Regional Disability and Health Team prior to emailing or > faxing any new referrals. > > Vaughan Dodd, Regional Disability Advisor. > > Desk2desk: 97187. > Email: vaughan.dodd...@msd.govt.nz. > For referrals: email fax_gnlis001_health_disabil...@msd.govt.nz. > > Our up-to-date desk file is located at: > http://doogle.ssi.govt.nz/resources/publications/reports-research/regional/auckland/auckland-health-disability-resources.html > > > -Original Message- > From: Talk > [mailto:talk-bounces+vaughan.dodd001=msd.govt...@lists.window-eyes.com] On > Behalf Of Marc Solomon via Talk > Sent: Wednesday, 3 August 2016 11:07 a.m. > To: Kevin Barry > Cc: Window-Eyes Discussion List > Subject: RE: update on Microsoft Edge (my final response on this thread, I > promise ) > > Fact number 1: Microsoft Edge used to accessibly support 0 percent of HTML5 > features. > Fact number 2: In less than 12 months, Microsoft Edge now accessibly supports > 100 percent of HTML5 features. > Fact number 3: Microsoft Edge now accessibly supports more HTML5 features > than any other major browser. > Fact number 4: Web browsers accessibly supporting HTML5 features will make > the web more usable for people who use assistive technology including screen > reader users > Source: www.html5accessibility.com<http://www.html5accessibility.com> > (curated by The Paciello Group, a globally recognized leader in digital > accessibility) Explanation of terms – HTML5 features “accessibly supported” > by a web browser includes if they are keyboard accessible, mapped to the > platform accessibility APIs, and if any accessibility related features are > supported. An accessibly supported feature means it is usable by people who > rely on assistive technology, without developers having to supplement with > ARIA or other additional workarounds. > > From: Kevin Barry [mailto:krba...@gmail.com] > Sent: Tuesday, August 2, 2016 6:23 PM > To: Marc Solomon <msolo...@aisquared.com> > Cc: Rick Thomas <ofbgm...@mi.rr.com>; Window-Eyes Discussion List > <talk@lists.window-eyes.com>; Portia Scott <porti...@sbcglobal.net> > Subject: Re: update on Microsoft Edge > > As soon as Microsoft make some progress, please share it with us. In the > meantime, please stop apologizing for their inexcusable choices. > > On Wednesday, August 3, 2016, Marc Solomon > <msolo...@aisquared.com<mailto:msolo...@aisquared.com>> wrote: > Kevin, > You are entitled to your opinion. As an advocate for the screen reader and > accessibility communities, I believe that constructive dialogue, eduction, > and cooperation is a formula for positive change. I will continue to share > facts about the progress being made by Microsoft in the realm of > accessibility. And, I sincerely hope that in the near future users of screen > readers will have access to another web browser under Windows. > Marc > > Sent with AquaMail for Android > http://www.aqua-mail.com > > On August 2, 2016 5:31:15 PM Kevin Barry <krba...@gmail.com<javascript:;>> > wrote: > > Simply put, I believe edge shall never be accessible. Microsoft has decided > to screw screen reader users over and that is that. To add insult to injury, > we must evidently put up with people who should know better making apologies > for microsoft and trying to explain why black is white. > > On Wednesday, August 3, 2016, Marc Solomon > <msolo...@aisquared.com<javascript:;><mailto:msolo...@aisquared.com<javascript:;>>> > wrote: > Well said Rick! To reiterate an important point in my previous post, end to > end accessibility is a team effort. Microsoft only has control over the OS > and browser. The screen reader has to be updated to support the accessibility > architecture of the OS and browser. VFO is actively working on making this > happen. > -
RE: update on Microsoft Edge (my final response on this thread, I promise )
Hi Marc. I'm perhaps tempting fate - are you signaling that in fact, Window-eyes is close to having the interface we need? I can check for myself as to the real user's experience of course when the anniversary of Windows 10 gets to a machine near me. Vaughan. Understand if non-disclosure still applies. Vaughan. Please telephone the Regional Disability and Health Team prior to emailing or faxing any new referrals. Vaughan Dodd, Regional Disability Advisor. Desk2desk: 97187. Email: vaughan.dodd...@msd.govt.nz. For referrals: email fax_gnlis001_health_disabil...@msd.govt.nz. Our up-to-date desk file is located at: http://doogle.ssi.govt.nz/resources/publications/reports-research/regional/auckland/auckland-health-disability-resources.html -Original Message- From: Talk [mailto:talk-bounces+vaughan.dodd001=msd.govt...@lists.window-eyes.com] On Behalf Of Marc Solomon via Talk Sent: Wednesday, 3 August 2016 11:07 a.m. To: Kevin Barry Cc: Window-Eyes Discussion List Subject: RE: update on Microsoft Edge (my final response on this thread, I promise ) Fact number 1: Microsoft Edge used to accessibly support 0 percent of HTML5 features. Fact number 2: In less than 12 months, Microsoft Edge now accessibly supports 100 percent of HTML5 features. Fact number 3: Microsoft Edge now accessibly supports more HTML5 features than any other major browser. Fact number 4: Web browsers accessibly supporting HTML5 features will make the web more usable for people who use assistive technology including screen reader users Source: www.html5accessibility.com<http://www.html5accessibility.com> (curated by The Paciello Group, a globally recognized leader in digital accessibility) Explanation of terms – HTML5 features “accessibly supported” by a web browser includes if they are keyboard accessible, mapped to the platform accessibility APIs, and if any accessibility related features are supported. An accessibly supported feature means it is usable by people who rely on assistive technology, without developers having to supplement with ARIA or other additional workarounds. From: Kevin Barry [mailto:krba...@gmail.com] Sent: Tuesday, August 2, 2016 6:23 PM To: Marc Solomon <msolo...@aisquared.com> Cc: Rick Thomas <ofbgm...@mi.rr.com>; Window-Eyes Discussion List <talk@lists.window-eyes.com>; Portia Scott <porti...@sbcglobal.net> Subject: Re: update on Microsoft Edge As soon as Microsoft make some progress, please share it with us. In the meantime, please stop apologizing for their inexcusable choices. On Wednesday, August 3, 2016, Marc Solomon <msolo...@aisquared.com<mailto:msolo...@aisquared.com>> wrote: Kevin, You are entitled to your opinion. As an advocate for the screen reader and accessibility communities, I believe that constructive dialogue, eduction, and cooperation is a formula for positive change. I will continue to share facts about the progress being made by Microsoft in the realm of accessibility. And, I sincerely hope that in the near future users of screen readers will have access to another web browser under Windows. Marc Sent with AquaMail for Android http://www.aqua-mail.com On August 2, 2016 5:31:15 PM Kevin Barry <krba...@gmail.com<javascript:;>> wrote: Simply put, I believe edge shall never be accessible. Microsoft has decided to screw screen reader users over and that is that. To add insult to injury, we must evidently put up with people who should know better making apologies for microsoft and trying to explain why black is white. On Wednesday, August 3, 2016, Marc Solomon <msolo...@aisquared.com<javascript:;><mailto:msolo...@aisquared.com<javascript:;>>> wrote: Well said Rick! To reiterate an important point in my previous post, end to end accessibility is a team effort. Microsoft only has control over the OS and browser. The screen reader has to be updated to support the accessibility architecture of the OS and browser. VFO is actively working on making this happen. -Original Message- From: Talk [mailto:talk-bounces+msolomon<javascript:;><javascript:;>=aisquared@lists.window-eyes.com<javascript:;><javascript:;>] On Behalf Of Rick Thomas via Talk Sent: Tuesday, August 2, 2016 4:51 PM To: 'Kevin Barry' <krba...@gmail.com<javascript:;><javascript:;>>; 'Window-Eyes Discussion List' <talk@lists.window-eyes.com<javascript:;><javascript:;>>; 'Portia Scott' <porti...@sbcglobal.net<javascript:;><javascript:;>> Subject: RE: update on Microsoft Edge If the Accessibility Tree reflects the browser and the page contents it is then up to the screen reader to use the tree properly and produce the audio outputs accordingly. Thus if the browser handles the new objects and the tree reflects the browser contents it is up to the screen reader to produce quality output. Rick USA -Origina
RE: update on Microsoft Edge (my final response on this thread, I promise )
Fact number 1: Microsoft Edge used to accessibly support 0 percent of HTML5 features. Fact number 2: In less than 12 months, Microsoft Edge now accessibly supports 100 percent of HTML5 features. Fact number 3: Microsoft Edge now accessibly supports more HTML5 features than any other major browser. Fact number 4: Web browsers accessibly supporting HTML5 features will make the web more usable for people who use assistive technology including screen reader users Source: www.html5accessibility.com<http://www.html5accessibility.com> (curated by The Paciello Group, a globally recognized leader in digital accessibility) Explanation of terms – HTML5 features “accessibly supported” by a web browser includes if they are keyboard accessible, mapped to the platform accessibility APIs, and if any accessibility related features are supported. An accessibly supported feature means it is usable by people who rely on assistive technology, without developers having to supplement with ARIA or other additional workarounds. From: Kevin Barry [mailto:krba...@gmail.com] Sent: Tuesday, August 2, 2016 6:23 PM To: Marc Solomon <msolo...@aisquared.com> Cc: Rick Thomas <ofbgm...@mi.rr.com>; Window-Eyes Discussion List <talk@lists.window-eyes.com>; Portia Scott <porti...@sbcglobal.net> Subject: Re: update on Microsoft Edge As soon as Microsoft make some progress, please share it with us. In the meantime, please stop apologizing for their inexcusable choices. On Wednesday, August 3, 2016, Marc Solomon <msolo...@aisquared.com<mailto:msolo...@aisquared.com>> wrote: Kevin, You are entitled to your opinion. As an advocate for the screen reader and accessibility communities, I believe that constructive dialogue, eduction, and cooperation is a formula for positive change. I will continue to share facts about the progress being made by Microsoft in the realm of accessibility. And, I sincerely hope that in the near future users of screen readers will have access to another web browser under Windows. Marc Sent with AquaMail for Android http://www.aqua-mail.com On August 2, 2016 5:31:15 PM Kevin Barry <krba...@gmail.com<javascript:;>> wrote: Simply put, I believe edge shall never be accessible. Microsoft has decided to screw screen reader users over and that is that. To add insult to injury, we must evidently put up with people who should know better making apologies for microsoft and trying to explain why black is white. On Wednesday, August 3, 2016, Marc Solomon <msolo...@aisquared.com<javascript:;><mailto:msolo...@aisquared.com<javascript:;>>> wrote: Well said Rick! To reiterate an important point in my previous post, end to end accessibility is a team effort. Microsoft only has control over the OS and browser. The screen reader has to be updated to support the accessibility architecture of the OS and browser. VFO is actively working on making this happen. -Original Message- From: Talk [mailto:talk-bounces+msolomon<javascript:;><javascript:;>=aisquared@lists.window-eyes.com<javascript:;><javascript:;>] On Behalf Of Rick Thomas via Talk Sent: Tuesday, August 2, 2016 4:51 PM To: 'Kevin Barry' <krba...@gmail.com<javascript:;><javascript:;>>; 'Window-Eyes Discussion List' <talk@lists.window-eyes.com<javascript:;><javascript:;>>; 'Portia Scott' <porti...@sbcglobal.net<javascript:;><javascript:;>> Subject: RE: update on Microsoft Edge If the Accessibility Tree reflects the browser and the page contents it is then up to the screen reader to use the tree properly and produce the audio outputs accordingly. Thus if the browser handles the new objects and the tree reflects the browser contents it is up to the screen reader to produce quality output. Rick USA -Original Message- From: Talk [mailto:talk-bounces+ofbgmail<javascript:;><javascript:;>=mi.rr@lists.window-eyes.com<javascript:;><javascript:;>] On Behalf Of Kevin Barry via Talk Sent: Tuesday, August 2, 2016 4:37 PM To: Portia Scott <porti...@sbcglobal.net<javascript:;><javascript:;>>; Window-Eyes Discussion List <talk@lists.window-eyes.com<javascript:;><javascript:;>> Subject: Re: update on Microsoft Edge So, he edge browser is accessible for HTML5, but not accessible for screen readers. This does not appear to demonstrate Microsoft's commitment to anything. Unless you count wishing to appear committed. If we cannot use the browser, all else is irrelevant. On Wednesday, August 3, 2016, Portia Scott via Talk < talk@lists.window-eyes.com<javascript:;><javascript:;>> wrote: > I definitely find this pretty interesting. Someone on Twitter was > saying that edge is actually accessible. Although, you have to tab a lot. > > I haven't really tested this, and I am not on my Win
Re: update on Microsoft Edge
As soon as Microsoft make some progress, please share it with us. In the meantime, please stop apologizing for their inexcusable choices. On Wednesday, August 3, 2016, Marc Solomon <msolo...@aisquared.com> wrote: > Kevin, > You are entitled to your opinion. As an advocate for the screen reader and > accessibility communities, I believe that constructive dialogue, eduction, > and cooperation is a formula for positive change. I will continue to share > facts about the progress being made by Microsoft in the realm of > accessibility. And, I sincerely hope that in the near future users of > screen readers will have access to another web browser under Windows. > Marc > > Sent with AquaMail for Android > http://www.aqua-mail.com > > On August 2, 2016 5:31:15 PM Kevin Barry <krba...@gmail.com <javascript:;>> > wrote: > > Simply put, I believe edge shall never be accessible. Microsoft has > decided to screw screen reader users over and that is that. To add insult > to injury, we must evidently put up with people who should know better > making apologies for microsoft and trying to explain why black is white. > > On Wednesday, August 3, 2016, Marc Solomon <msolo...@aisquared.com > <javascript:;><mailto:msolo...@aisquared.com <javascript:;>>> wrote: > Well said Rick! To reiterate an important point in my previous post, end > to end accessibility is a team effort. Microsoft only has control over the > OS and browser. The screen reader has to be updated to support the > accessibility architecture of the OS and browser. VFO is actively working > on making this happen. > -Original Message- > From: Talk [mailto:talk-bounces+msolomon <javascript:;><javascript:;>= > aisquared@lists.window-eyes.com <javascript:;><javascript:;>] On > Behalf Of Rick Thomas via Talk > Sent: Tuesday, August 2, 2016 4:51 PM > To: 'Kevin Barry' <krba...@gmail.com <javascript:;><javascript:;>>; > 'Window-Eyes Discussion List' <talk@lists.window-eyes.com > <javascript:;><javascript:;>>; > 'Portia Scott' <porti...@sbcglobal.net <javascript:;><javascript:;>> > Subject: RE: update on Microsoft Edge > > If the Accessibility Tree reflects the browser and the page contents it is > then up to the screen reader to use the tree properly and produce the audio > outputs accordingly. > Thus if the browser handles the new objects and the tree reflects the > browser contents it is up to the screen reader to produce quality output. > Rick USA > > -Original Message- > From: Talk [mailto:talk-bounces+ofbgmail <javascript:;><javascript:;>= > mi.rr@lists.window-eyes.com <javascript:;><javascript:;>] On Behalf > Of Kevin Barry via Talk > Sent: Tuesday, August 2, 2016 4:37 PM > To: Portia Scott <porti...@sbcglobal.net <javascript:;><javascript:;>>; > Window-Eyes Discussion List <talk@lists.window-eyes.com <javascript:;> > <javascript:;>> > Subject: Re: update on Microsoft Edge > > So, he edge browser is accessible for HTML5, but not accessible for screen > readers. This does not appear to demonstrate Microsoft's commitment to > anything. Unless you count wishing to appear committed. If we cannot use > the browser, all else is irrelevant. > > On Wednesday, August 3, 2016, Portia Scott via Talk < > talk@lists.window-eyes.com <javascript:;><javascript:;>> wrote: > > > I definitely find this pretty interesting. Someone on Twitter was > > saying that edge is actually accessible. Although, you have to tab a lot. > > > > I haven't really tested this, and I am not on my Windows machine at > > the moment. But I thought I would mention this to the list. > > > > Portia. > > > On Aug 2, 2016, at 11:22 AM, Marc Solomon via Talk < > > talk@lists.window-eyes.com <javascript:;><javascript:;> <javascript:;>> > wrote: > > > > > > Many of you on the list have voiced concerns about the lack of > > accessibility and screen reader compatibility in Microsoft Edge (the > > new web browser in Windows 10). Yes, Microsoft dropped the ball by > > releasing a non-accessible solution when Windows 10 first shipped. > > There is nothing we can do to change that. But, I wanted to share some > > information that was just released that helps demonstrate Microsoft's > > commitment to accessibility and the improvements that have been made to > Edge. > > > First, a little background. HTML5 is the latest version of the > > > markup > > language used to write web pages. This new specification includes many > > new elements that ha
Re: update on Microsoft Edge
Kevin, You are entitled to your opinion. As an advocate for the screen reader and accessibility communities, I believe that constructive dialogue, eduction, and cooperation is a formula for positive change. I will continue to share facts about the progress being made by Microsoft in the realm of accessibility. And, I sincerely hope that in the near future users of screen readers will have access to another web browser under Windows. Marc Sent with AquaMail for Android http://www.aqua-mail.com On August 2, 2016 5:31:15 PM Kevin Barry <krba...@gmail.com> wrote: Simply put, I believe edge shall never be accessible. Microsoft has decided to screw screen reader users over and that is that. To add insult to injury, we must evidently put up with people who should know better making apologies for microsoft and trying to explain why black is white. On Wednesday, August 3, 2016, Marc Solomon <msolo...@aisquared.com<mailto:msolo...@aisquared.com>> wrote: Well said Rick! To reiterate an important point in my previous post, end to end accessibility is a team effort. Microsoft only has control over the OS and browser. The screen reader has to be updated to support the accessibility architecture of the OS and browser. VFO is actively working on making this happen. -Original Message- From: Talk [mailto:talk-bounces+msolomon<javascript:;>=aisquared@lists.window-eyes.com<javascript:;>] On Behalf Of Rick Thomas via Talk Sent: Tuesday, August 2, 2016 4:51 PM To: 'Kevin Barry' <krba...@gmail.com<javascript:;>>; 'Window-Eyes Discussion List' <talk@lists.window-eyes.com<javascript:;>>; 'Portia Scott' <porti...@sbcglobal.net<javascript:;>> Subject: RE: update on Microsoft Edge If the Accessibility Tree reflects the browser and the page contents it is then up to the screen reader to use the tree properly and produce the audio outputs accordingly. Thus if the browser handles the new objects and the tree reflects the browser contents it is up to the screen reader to produce quality output. Rick USA -Original Message- From: Talk [mailto:talk-bounces+ofbgmail<javascript:;>=mi.rr@lists.window-eyes.com<javascript:;>] On Behalf Of Kevin Barry via Talk Sent: Tuesday, August 2, 2016 4:37 PM To: Portia Scott <porti...@sbcglobal.net<javascript:;>>; Window-Eyes Discussion List <talk@lists.window-eyes.com<javascript:;>> Subject: Re: update on Microsoft Edge So, he edge browser is accessible for HTML5, but not accessible for screen readers. This does not appear to demonstrate Microsoft's commitment to anything. Unless you count wishing to appear committed. If we cannot use the browser, all else is irrelevant. On Wednesday, August 3, 2016, Portia Scott via Talk < talk@lists.window-eyes.com<javascript:;>> wrote: > I definitely find this pretty interesting. Someone on Twitter was > saying that edge is actually accessible. Although, you have to tab a lot. > > I haven't really tested this, and I am not on my Windows machine at > the moment. But I thought I would mention this to the list. > > Portia. > > On Aug 2, 2016, at 11:22 AM, Marc Solomon via Talk < > talk@lists.window-eyes.com<javascript:;> <javascript:;>> wrote: > > > > Many of you on the list have voiced concerns about the lack of > accessibility and screen reader compatibility in Microsoft Edge (the > new web browser in Windows 10). Yes, Microsoft dropped the ball by > releasing a non-accessible solution when Windows 10 first shipped. > There is nothing we can do to change that. But, I wanted to share some > information that was just released that helps demonstrate Microsoft's > commitment to accessibility and the improvements that have been made to Edge. > > First, a little background. HTML5 is the latest version of the > > markup > language used to write web pages. This new specification includes many > new elements that have potential to make web pages more accessible and operable > from the keyboard. In order for this all to work, both the web browser > and assistive technology have to implement support for the HTML5 specification. > And, the web page developer has to use the HTML5 markup correctly when > authoring the page. There are more technical complexities involved for > creating an accessible experience, but this is a good place to start. > > Here is an example of how a new HTML5 element could improve > accessibility. A web page author can use the new element to > indicate the main content on a web page. The web browser can map the > element to a landmark element in the accessibility API (application > programming interface). This API can then communicate to a screen > reader that there is a main content landmark available on the page. > The screen reader
Re: update on Microsoft Edge
Simply put, I believe edge shall never be accessible. Microsoft has decided to screw screen reader users over and that is that. To add insult to injury, we must evidently put up with people who should know better making apologies for microsoft and trying to explain why black is white. On Wednesday, August 3, 2016, Kevin Barry <krba...@gmail.com> wrote: > Simply put, I believe edge shall never be accessible. Microsoft has > decided to screw screen reader users over and that is that. To add insult > to injury, we must evidently put up with people who should know better > making apologies for microsoft and trying to explain why black is white. > > On Wednesday, August 3, 2016, Marc Solomon <msolo...@aisquared.com > <javascript:_e(%7B%7D,'cvml','msolo...@aisquared.com');>> wrote: > >> Well said Rick! To reiterate an important point in my previous post, end >> to end accessibility is a team effort. Microsoft only has control over the >> OS and browser. The screen reader has to be updated to support the >> accessibility architecture of the OS and browser. VFO is actively working >> on making this happen. >> -Original Message- >> From: Talk [mailto:talk-bounces+msolomon= >> aisquared@lists.window-eyes.com] On Behalf Of Rick Thomas via Talk >> Sent: Tuesday, August 2, 2016 4:51 PM >> To: 'Kevin Barry' <krba...@gmail.com>; 'Window-Eyes Discussion List' < >> talk@lists.window-eyes.com>; 'Portia Scott' <porti...@sbcglobal.net> >> Subject: RE: update on Microsoft Edge >> >> If the Accessibility Tree reflects the browser and the page contents it >> is then up to the screen reader to use the tree properly and produce the >> audio outputs accordingly. >> Thus if the browser handles the new objects and the tree reflects the >> browser contents it is up to the screen reader to produce quality output. >> Rick USA >> >> -Original Message- >> From: Talk [mailto:talk-bounces+ofbgmail=mi.rr@lists.window-eyes.com] >> On Behalf Of Kevin Barry via Talk >> Sent: Tuesday, August 2, 2016 4:37 PM >> To: Portia Scott <porti...@sbcglobal.net>; Window-Eyes Discussion List < >> talk@lists.window-eyes.com> >> Subject: Re: update on Microsoft Edge >> >> So, he edge browser is accessible for HTML5, but not accessible for >> screen readers. This does not appear to demonstrate Microsoft's commitment >> to anything. Unless you count wishing to appear committed. If we cannot use >> the browser, all else is irrelevant. >> >> On Wednesday, August 3, 2016, Portia Scott via Talk < >> talk@lists.window-eyes.com> wrote: >> >> > I definitely find this pretty interesting. Someone on Twitter was >> > saying that edge is actually accessible. Although, you have to tab a >> lot. >> > >> > I haven't really tested this, and I am not on my Windows machine at >> > the moment. But I thought I would mention this to the list. >> > >> > Portia. >> > > On Aug 2, 2016, at 11:22 AM, Marc Solomon via Talk < >> > talk@lists.window-eyes.com <javascript:;>> wrote: >> > > >> > > Many of you on the list have voiced concerns about the lack of >> > accessibility and screen reader compatibility in Microsoft Edge (the >> > new web browser in Windows 10). Yes, Microsoft dropped the ball by >> > releasing a non-accessible solution when Windows 10 first shipped. >> > There is nothing we can do to change that. But, I wanted to share some >> > information that was just released that helps demonstrate Microsoft's >> > commitment to accessibility and the improvements that have been made to >> Edge. >> > > First, a little background. HTML5 is the latest version of the >> > > markup >> > language used to write web pages. This new specification includes many >> > new elements that have potential to make web pages more accessible and >> operable >> > from the keyboard. In order for this all to work, both the web browser >> > and assistive technology have to implement support for the HTML5 >> specification. >> > And, the web page developer has to use the HTML5 markup correctly when >> > authoring the page. There are more technical complexities involved for >> > creating an accessible experience, but this is a good place to start. >> > > Here is an example of how a new HTML5 element could improve >> > accessibility. A web page author can use the new element to >> > indicate the main content on a web page. The web browser can map the >> >> > ele
Re: update on Microsoft Edge
Simply put, I believe edge shall never be accessible. Microsoft has decided to screw screen reader users over and that is that. To add insult to injury, we must evidently put up with people who should know better making apologies for microsoft and trying to explain why black is white. On Wednesday, August 3, 2016, Marc Solomon <msolo...@aisquared.com> wrote: > Well said Rick! To reiterate an important point in my previous post, end > to end accessibility is a team effort. Microsoft only has control over the > OS and browser. The screen reader has to be updated to support the > accessibility architecture of the OS and browser. VFO is actively working > on making this happen. > -Original Message- > From: Talk [mailto:talk-bounces+msolomon <javascript:;>= > aisquared@lists.window-eyes.com <javascript:;>] On Behalf Of Rick > Thomas via Talk > Sent: Tuesday, August 2, 2016 4:51 PM > To: 'Kevin Barry' <krba...@gmail.com <javascript:;>>; 'Window-Eyes > Discussion List' <talk@lists.window-eyes.com <javascript:;>>; 'Portia > Scott' <porti...@sbcglobal.net <javascript:;>> > Subject: RE: update on Microsoft Edge > > If the Accessibility Tree reflects the browser and the page contents it is > then up to the screen reader to use the tree properly and produce the audio > outputs accordingly. > Thus if the browser handles the new objects and the tree reflects the > browser contents it is up to the screen reader to produce quality output. > Rick USA > > -Original Message- > From: Talk [mailto:talk-bounces+ofbgmail <javascript:;>= > mi.rr@lists.window-eyes.com <javascript:;>] On Behalf Of Kevin Barry > via Talk > Sent: Tuesday, August 2, 2016 4:37 PM > To: Portia Scott <porti...@sbcglobal.net <javascript:;>>; Window-Eyes > Discussion List <talk@lists.window-eyes.com <javascript:;>> > Subject: Re: update on Microsoft Edge > > So, he edge browser is accessible for HTML5, but not accessible for screen > readers. This does not appear to demonstrate Microsoft's commitment to > anything. Unless you count wishing to appear committed. If we cannot use > the browser, all else is irrelevant. > > On Wednesday, August 3, 2016, Portia Scott via Talk < > talk@lists.window-eyes.com <javascript:;>> wrote: > > > I definitely find this pretty interesting. Someone on Twitter was > > saying that edge is actually accessible. Although, you have to tab a lot. > > > > I haven't really tested this, and I am not on my Windows machine at > > the moment. But I thought I would mention this to the list. > > > > Portia. > > > On Aug 2, 2016, at 11:22 AM, Marc Solomon via Talk < > > talk@lists.window-eyes.com <javascript:;> <javascript:;>> wrote: > > > > > > Many of you on the list have voiced concerns about the lack of > > accessibility and screen reader compatibility in Microsoft Edge (the > > new web browser in Windows 10). Yes, Microsoft dropped the ball by > > releasing a non-accessible solution when Windows 10 first shipped. > > There is nothing we can do to change that. But, I wanted to share some > > information that was just released that helps demonstrate Microsoft's > > commitment to accessibility and the improvements that have been made to > Edge. > > > First, a little background. HTML5 is the latest version of the > > > markup > > language used to write web pages. This new specification includes many > > new elements that have potential to make web pages more accessible and > operable > > from the keyboard. In order for this all to work, both the web browser > > and assistive technology have to implement support for the HTML5 > specification. > > And, the web page developer has to use the HTML5 markup correctly when > > authoring the page. There are more technical complexities involved for > > creating an accessible experience, but this is a good place to start. > > > Here is an example of how a new HTML5 element could improve > > accessibility. A web page author can use the new element to > > indicate the main content on a web page. The web browser can map the > > > element to a landmark element in the accessibility API (application > > programming interface). This API can then communicate to a screen > > reader that there is a main content landmark available on the page. > > The screen reader can provide the user with a hotkey to navigate to > > the main content landmark. As you can see, a carefully orchestrated > > effort must take place in order for accessibility to happen. Okay, > > that is the end of the > lecture. > > Than
RE: update on Microsoft Edge
Well said Rick! To reiterate an important point in my previous post, end to end accessibility is a team effort. Microsoft only has control over the OS and browser. The screen reader has to be updated to support the accessibility architecture of the OS and browser. VFO is actively working on making this happen. -Original Message- From: Talk [mailto:talk-bounces+msolomon=aisquared@lists.window-eyes.com] On Behalf Of Rick Thomas via Talk Sent: Tuesday, August 2, 2016 4:51 PM To: 'Kevin Barry' <krba...@gmail.com>; 'Window-Eyes Discussion List' <talk@lists.window-eyes.com>; 'Portia Scott' <porti...@sbcglobal.net> Subject: RE: update on Microsoft Edge If the Accessibility Tree reflects the browser and the page contents it is then up to the screen reader to use the tree properly and produce the audio outputs accordingly. Thus if the browser handles the new objects and the tree reflects the browser contents it is up to the screen reader to produce quality output. Rick USA -Original Message- From: Talk [mailto:talk-bounces+ofbgmail=mi.rr@lists.window-eyes.com] On Behalf Of Kevin Barry via Talk Sent: Tuesday, August 2, 2016 4:37 PM To: Portia Scott <porti...@sbcglobal.net>; Window-Eyes Discussion List <talk@lists.window-eyes.com> Subject: Re: update on Microsoft Edge So, he edge browser is accessible for HTML5, but not accessible for screen readers. This does not appear to demonstrate Microsoft's commitment to anything. Unless you count wishing to appear committed. If we cannot use the browser, all else is irrelevant. On Wednesday, August 3, 2016, Portia Scott via Talk < talk@lists.window-eyes.com> wrote: > I definitely find this pretty interesting. Someone on Twitter was > saying that edge is actually accessible. Although, you have to tab a lot. > > I haven't really tested this, and I am not on my Windows machine at > the moment. But I thought I would mention this to the list. > > Portia. > > On Aug 2, 2016, at 11:22 AM, Marc Solomon via Talk < > talk@lists.window-eyes.com <javascript:;>> wrote: > > > > Many of you on the list have voiced concerns about the lack of > accessibility and screen reader compatibility in Microsoft Edge (the > new web browser in Windows 10). Yes, Microsoft dropped the ball by > releasing a non-accessible solution when Windows 10 first shipped. > There is nothing we can do to change that. But, I wanted to share some > information that was just released that helps demonstrate Microsoft's > commitment to accessibility and the improvements that have been made to Edge. > > First, a little background. HTML5 is the latest version of the > > markup > language used to write web pages. This new specification includes many > new elements that have potential to make web pages more accessible and operable > from the keyboard. In order for this all to work, both the web browser > and assistive technology have to implement support for the HTML5 specification. > And, the web page developer has to use the HTML5 markup correctly when > authoring the page. There are more technical complexities involved for > creating an accessible experience, but this is a good place to start. > > Here is an example of how a new HTML5 element could improve > accessibility. A web page author can use the new element to > indicate the main content on a web page. The web browser can map the > element to a landmark element in the accessibility API (application > programming interface). This API can then communicate to a screen > reader that there is a main content landmark available on the page. > The screen reader can provide the user with a hotkey to navigate to > the main content landmark. As you can see, a carefully orchestrated > effort must take place in order for accessibility to happen. Okay, > that is the end of the lecture. > Thanks for staying awake. > > The website www.html5accessibility<http://www.html5accessibility> > > was > created to document the current level of HTML5 accessibility support > in each of the major browsers (Chrome, Edge, Firefox, Internet > Explorer and Safari). The website first lists each browser and the > percentage of HTML5 elements that are accessibly supported. Then, > there are tables showing each > HTML5 element's current support in the major browsers. This website is > updated frequently. At the beginning of this year, Edge had a score of 0%. > As of today, it now has a score of 100%. And, it is the only major > browser that now accessibly supports all HTML5 features. Edge has > leapfrogged all of the other browsers, even the mighty Firefox which > had been at the top of > the list for quite some time. This robust HTML5 support in Edge is a > true testament to Microsoft's comm
RE: update on Microsoft Edge
If the Accessibility Tree reflects the browser and the page contents it is then up to the screen reader to use the tree properly and produce the audio outputs accordingly. Thus if the browser handles the new objects and the tree reflects the browser contents it is up to the screen reader to produce quality output. Rick USA -Original Message- From: Talk [mailto:talk-bounces+ofbgmail=mi.rr@lists.window-eyes.com] On Behalf Of Kevin Barry via Talk Sent: Tuesday, August 2, 2016 4:37 PM To: Portia Scott <porti...@sbcglobal.net>; Window-Eyes Discussion List <talk@lists.window-eyes.com> Subject: Re: update on Microsoft Edge So, he edge browser is accessible for HTML5, but not accessible for screen readers. This does not appear to demonstrate Microsoft's commitment to anything. Unless you count wishing to appear committed. If we cannot use the browser, all else is irrelevant. On Wednesday, August 3, 2016, Portia Scott via Talk < talk@lists.window-eyes.com> wrote: > I definitely find this pretty interesting. Someone on Twitter was saying > that edge is actually accessible. Although, you have to tab a lot. > > I haven't really tested this, and I am not on my Windows machine at the > moment. But I thought I would mention this to the list. > > Portia. > > On Aug 2, 2016, at 11:22 AM, Marc Solomon via Talk < > talk@lists.window-eyes.com <javascript:;>> wrote: > > > > Many of you on the list have voiced concerns about the lack of > accessibility and screen reader compatibility in Microsoft Edge (the new > web browser in Windows 10). Yes, Microsoft dropped the ball by releasing a > non-accessible solution when Windows 10 first shipped. There is nothing we > can do to change that. But, I wanted to share some information that was > just released that helps demonstrate Microsoft's commitment to > accessibility and the improvements that have been made to Edge. > > First, a little background. HTML5 is the latest version of the markup > language used to write web pages. This new specification includes many new > elements that have potential to make web pages more accessible and operable > from the keyboard. In order for this all to work, both the web browser and > assistive technology have to implement support for the HTML5 specification. > And, the web page developer has to use the HTML5 markup correctly when > authoring the page. There are more technical complexities involved for > creating an accessible experience, but this is a good place to start. > > Here is an example of how a new HTML5 element could improve > accessibility. A web page author can use the new element to > indicate the main content on a web page. The web browser can map the > element to a landmark element in the accessibility API (application > programming interface). This API can then communicate to a screen reader > that there is a main content landmark available on the page. The screen > reader can provide the user with a hotkey to navigate to the main content > landmark. As you can see, a carefully orchestrated effort must take place > in order for accessibility to happen. Okay, that is the end of the lecture. > Thanks for staying awake. > > The website www.html5accessibility<http://www.html5accessibility> was > created to document the current level of HTML5 accessibility support in > each of the major browsers (Chrome, Edge, Firefox, Internet Explorer and > Safari). The website first lists each browser and the percentage of HTML5 > elements that are accessibly supported. Then, there are tables showing each > HTML5 element's current support in the major browsers. This website is > updated frequently. At the beginning of this year, Edge had a score of 0%. > As of today, it now has a score of 100%. And, it is the only major browser > that now accessibly supports all HTML5 features. Edge has leapfrogged all > of the other browsers, even the mighty Firefox which had been at the top of > the list for quite some time. This robust HTML5 support in Edge is a true > testament to Microsoft's commitment to accessibility. And, I for one give > them kudos for this outstanding accomplishment. Now, back to your regular > programming. > > Best, > > Marc > > ___ > > Any views or opinions presented in this email are solely those of the > author and do not necessarily represent those of Ai Squared. > > > > For membership options, visit > http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/portia89%40sbc global.net > . > > For subscription options, visit > http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com > > List archives can be found at > http://lists.window-eyes.com/private.cgi/talk-window-eyes.com > > __
RE: update on Microsoft Edge
Kevin: I appreciate Marc posting the explanation, and your comment below is the true reality check. If I understand Microsoft's presentation via Main Menu correctly, Microsoft chose to deal with security issues as these relate to Edge, effectively side lining screen readers. Assuming that the reference Marc has given is independent of Microsoft, it seems that we can have all of the accessible coding we want and need, but the screen reader interaction limitations make the discussion of best browser and Edge's top ranking nothing more than of academic interest. It is clearly tough for small screen reader companies to keep abreast of Microsoft's antics. A Window-Eyes update is clearly necessary for Windows 10 Anniversary, but why did not Microsoft have all of its Edge security concerns dealt with in time for this update? Vaughan. Please telephone the Regional Disability and Health Team prior to emailing or faxing any new referrals. Vaughan Dodd, Regional Disability Advisor. Desk2desk: 97187. Email: vaughan.dodd...@msd.govt.nz. For referrals: email fax_gnlis001_health_disabil...@msd.govt.nz. Our up-to-date desk file is located at: http://doogle.ssi.govt.nz/resources/publications/reports-research/regional/auckland/auckland-health-disability-resources.html -Original Message- From: Talk [mailto:talk-bounces+vaughan.dodd001=msd.govt...@lists.window-eyes.com] On Behalf Of Kevin Barry via Talk Sent: Wednesday, 3 August 2016 8:37 a.m. To: Portia Scott; Window-Eyes Discussion List Subject: Re: update on Microsoft Edge So, he edge browser is accessible for HTML5, but not accessible for screen readers. This does not appear to demonstrate Microsoft's commitment to anything. Unless you count wishing to appear committed. If we cannot use the browser, all else is irrelevant. On Wednesday, August 3, 2016, Portia Scott via Talk < talk@lists.window-eyes.com> wrote: > I definitely find this pretty interesting. Someone on Twitter was > saying that edge is actually accessible. Although, you have to tab a lot. > > I haven't really tested this, and I am not on my Windows machine at > the moment. But I thought I would mention this to the list. > > Portia. > > On Aug 2, 2016, at 11:22 AM, Marc Solomon via Talk < > talk@lists.window-eyes.com <javascript:;>> wrote: > > > > Many of you on the list have voiced concerns about the lack of > accessibility and screen reader compatibility in Microsoft Edge (the > new web browser in Windows 10). Yes, Microsoft dropped the ball by > releasing a non-accessible solution when Windows 10 first shipped. > There is nothing we can do to change that. But, I wanted to share some > information that was just released that helps demonstrate Microsoft's > commitment to accessibility and the improvements that have been made to Edge. > > First, a little background. HTML5 is the latest version of the > > markup > language used to write web pages. This new specification includes many > new elements that have potential to make web pages more accessible and > operable from the keyboard. In order for this all to work, both the > web browser and assistive technology have to implement support for the HTML5 > specification. > And, the web page developer has to use the HTML5 markup correctly when > authoring the page. There are more technical complexities involved for > creating an accessible experience, but this is a good place to start. > > Here is an example of how a new HTML5 element could improve > accessibility. A web page author can use the new element to > indicate the main content on a web page. The web browser can map the > element to a landmark element in the accessibility API > (application programming interface). This API can then communicate to > a screen reader that there is a main content landmark available on the > page. The screen reader can provide the user with a hotkey to navigate > to the main content landmark. As you can see, a carefully orchestrated > effort must take place in order for accessibility to happen. Okay, that is > the end of the lecture. > Thanks for staying awake. > > The website www.html5accessibility<http://www.html5accessibility> > > was > created to document the current level of HTML5 accessibility support > in each of the major browsers (Chrome, Edge, Firefox, Internet > Explorer and Safari). The website first lists each browser and the > percentage of HTML5 elements that are accessibly supported. Then, > there are tables showing each > HTML5 element's current support in the major browsers. This website is > updated frequently. At the beginning of this year, Edge had a score of 0%. > As of today, it now has a score of 100%. And, it is the only major > browser that now accessibly supports all HTML5 features
Re: update on Microsoft Edge
I definitely find this pretty interesting. Someone on Twitter was saying that edge is actually accessible. Although, you have to tab a lot. I haven't really tested this, and I am not on my Windows machine at the moment. But I thought I would mention this to the list. Portia. > On Aug 2, 2016, at 11:22 AM, Marc Solomon via Talk > <talk@lists.window-eyes.com> wrote: > > Many of you on the list have voiced concerns about the lack of accessibility > and screen reader compatibility in Microsoft Edge (the new web browser in > Windows 10). Yes, Microsoft dropped the ball by releasing a non-accessible > solution when Windows 10 first shipped. There is nothing we can do to change > that. But, I wanted to share some information that was just released that > helps demonstrate Microsoft's commitment to accessibility and the > improvements that have been made to Edge. > First, a little background. HTML5 is the latest version of the markup > language used to write web pages. This new specification includes many new > elements that have potential to make web pages more accessible and operable > from the keyboard. In order for this all to work, both the web browser and > assistive technology have to implement support for the HTML5 specification. > And, the web page developer has to use the HTML5 markup correctly when > authoring the page. There are more technical complexities involved for > creating an accessible experience, but this is a good place to start. > Here is an example of how a new HTML5 element could improve accessibility. A > web page author can use the new element to indicate the main content > on a web page. The web browser can map the element to a landmark > element in the accessibility API (application programming interface). This > API can then communicate to a screen reader that there is a main content > landmark available on the page. The screen reader can provide the user with a > hotkey to navigate to the main content landmark. As you can see, a carefully > orchestrated effort must take place in order for accessibility to happen. > Okay, that is the end of the lecture. Thanks for staying awake. > The website www.html5accessibility<http://www.html5accessibility> was created > to document the current level of HTML5 accessibility support in each of the > major browsers (Chrome, Edge, Firefox, Internet Explorer and Safari). The > website first lists each browser and the percentage of HTML5 elements that > are accessibly supported. Then, there are tables showing each HTML5 element's > current support in the major browsers. This website is updated frequently. At > the beginning of this year, Edge had a score of 0%. As of today, it now has a > score of 100%. And, it is the only major browser that now accessibly supports > all HTML5 features. Edge has leapfrogged all of the other browsers, even the > mighty Firefox which had been at the top of the list for quite some time. > This robust HTML5 support in Edge is a true testament to Microsoft's > commitment to accessibility. And, I for one give them kudos for this > outstanding accomplishment. Now, back to your regular programming. > Best, > Marc > ___ > Any views or opinions presented in this email are solely those of the author > and do not necessarily represent those of Ai Squared. > > For membership options, visit > http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/portia89%40sbcglobal.net. > For subscription options, visit > http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com > List archives can be found at > http://lists.window-eyes.com/private.cgi/talk-window-eyes.com ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
update on Microsoft Edge
Many of you on the list have voiced concerns about the lack of accessibility and screen reader compatibility in Microsoft Edge (the new web browser in Windows 10). Yes, Microsoft dropped the ball by releasing a non-accessible solution when Windows 10 first shipped. There is nothing we can do to change that. But, I wanted to share some information that was just released that helps demonstrate Microsoft's commitment to accessibility and the improvements that have been made to Edge. First, a little background. HTML5 is the latest version of the markup language used to write web pages. This new specification includes many new elements that have potential to make web pages more accessible and operable from the keyboard. In order for this all to work, both the web browser and assistive technology have to implement support for the HTML5 specification. And, the web page developer has to use the HTML5 markup correctly when authoring the page. There are more technical complexities involved for creating an accessible experience, but this is a good place to start. Here is an example of how a new HTML5 element could improve accessibility. A web page author can use the new element to indicate the main content on a web page. The web browser can map the element to a landmark element in the accessibility API (application programming interface). This API can then communicate to a screen reader that there is a main content landmark available on the page. The screen reader can provide the user with a hotkey to navigate to the main content landmark. As you can see, a carefully orchestrated effort must take place in order for accessibility to happen. Okay, that is the end of the lecture. Thanks for staying awake. The website www.html5accessibility<http://www.html5accessibility> was created to document the current level of HTML5 accessibility support in each of the major browsers (Chrome, Edge, Firefox, Internet Explorer and Safari). The website first lists each browser and the percentage of HTML5 elements that are accessibly supported. Then, there are tables showing each HTML5 element's current support in the major browsers. This website is updated frequently. At the beginning of this year, Edge had a score of 0%. As of today, it now has a score of 100%. And, it is the only major browser that now accessibly supports all HTML5 features. Edge has leapfrogged all of the other browsers, even the mighty Firefox which had been at the top of the list for quite some time. This robust HTML5 support in Edge is a true testament to Microsoft's commitment to accessibility. And, I for one give them kudos for this outstanding accomplishment. Now, back to your regular programming. Best, Marc ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
Re: MICROSOFT EDGE
Edge is not accessible to any screen reader as far as I know -Original Message- From: Stephen Thacker via Talk Sent: Thursday, December 17, 2015 11:09 AM To: talk@lists.window-eyes.com Subject: MICROSOFT EDGE Is WE9.3 compatible with Microsoft Edge browser now? Compliments of the season to you all, Steve Thacker ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/tch828%40mediacombb.net. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
MICROSOFT EDGE
Is WE9.3 compatible with Microsoft Edge browser now? Compliments of the season to you all, Steve Thacker ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
RE: microsoft edge
Hi, how do you make sure you have apps enabled please? Thanks, Steve - Original Message - From: Chris Grabowski via Talk <talk@lists.window-eyes.com To: Don H <lmdd...@comcast.net>, Window-Eyes Discussion List<talk@lists.window-eyes.com Date sent: Mon, 7 Dec 2015 19:25:25 + Subject: RE: microsoft edge Make sure you have apps enabled. The message came up for me. Also there is a check box that says don't show this again. Chris Window-Eyes Product Support Ai Squared 725 Airport North Office Park Fort Wayne, IN 46825 (802) 362-3612 www.aisquared.com -Original Message- From: Talk [mailto:talk-bounces+cgrabowski=aisquared.com@lists.window-eyes.c om] On Behalf Of Don H via Talk Sent: Monday, December 7, 2015 2:16 PM To: Window-Eyes Discussion List <talk@lists.window-eyes.com Subject: microsoft edge Noticed today that the warning message that was coming up with Microsoft Edge to switch to IE as your default browser no longer comes up. Running latest version of Windows 10. Hopefully Ai Squared will now release an app or what ever it takes to make Edge more user friendly with WE. ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/cgr abowski%40aisquared.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/ste ve.thacker%40btinternet.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
microsoft edge
Noticed today that the warning message that was coming up with Microsoft Edge to switch to IE as your default browser no longer comes up. Running latest version of Windows 10. Hopefully Ai Squared will now release an app or what ever it takes to make Edge more user friendly with WE. ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
RE: microsoft edge
Make sure you have apps enabled. The message came up for me. Also there is a check box that says don't show this again. Chris Window-Eyes Product Support Ai Squared 725 Airport North Office Park Fort Wayne, IN 46825 (802) 362-3612 www.aisquared.com -Original Message- From: Talk [mailto:talk-bounces+cgrabowski=aisquared@lists.window-eyes.com] On Behalf Of Don H via Talk Sent: Monday, December 7, 2015 2:16 PM To: Window-Eyes Discussion List <talk@lists.window-eyes.com> Subject: microsoft edge Noticed today that the warning message that was coming up with Microsoft Edge to switch to IE as your default browser no longer comes up. Running latest version of Windows 10. Hopefully Ai Squared will now release an app or what ever it takes to make Edge more user friendly with WE. ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/cgrabowski%40aisquared.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com ___ Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Ai Squared. For membership options, visit http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com. For subscription options, visit http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com List archives can be found at http://lists.window-eyes.com/private.cgi/talk-window-eyes.com
