RE: update on Microsoft Edge (my final response on this thread, maybe? )

[Rick Thomas via Talk]

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? )

[Kevin Barry via Talk]

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? )

[Jim via Talk]

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? )

[Marcie Brink-Chaney via Talk]

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? )

[Vaughan Dodd via Talk]

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? )

[Nick Sarames via Talk]

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? )

[Marc Solomon via Talk]

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 )

[Marc Solomon via Talk]

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 )

[Vaughan Dodd via Talk]

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 )

[Marc Solomon via Talk]

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

[Kevin Barry via Talk]

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

[Marc Solomon via Talk]

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

[Kevin Barry via Talk]

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

[Kevin Barry via Talk]

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

[Marc Solomon via Talk]

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

[Rick Thomas via Talk]

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

[Vaughan Dodd via Talk]

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

[Portia Scott via Talk]

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 
>  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 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