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 <main> element to > indicate the main content on a web page. The web browser can map the <main> > 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/krbarry%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 > -- Sent from Kevin's iPhone. _______________________________________________ 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
