[Colorado-Talk] Disney Plus Not Accessible to the Blind

[Nancy Feldman]

I completed the task with JAWS and Internet Explorer.

You are right that there are numerous tools for completing the process. I
was also able to do this with Internet Explorer and Narrator. That was
surprising.




-----Original Message-----
From: Colorado-Talk <colorado-talk-bounces at nfbnet.org> On Behalf Of Curtis
Chong via Colorado-Talk
Sent: Monday, November 11, 2019 8:45 PM
To: 'NFB of Colorado Discussion List' <colorado-talk at nfbnet.org>
Cc: Curtis Chong <chong.curtis at gmail.com>
Subject: [Colorado-Talk] Disney Plus Not Accessible to the Blind

Greetings:

Please read the email shown below along with the attached file. Clearly,
there are accessibility issues with the Disney Plus website. This entire
business of determining accessibility is quite complicated these days in
light of the wide variety of operating system/screen reader/web browser
combinations that are now being used by blind people everywhere. Some
persistent folks have been able to sign up for the service, but I believe
that a lot more people are now stymied by the construction of the Disney
Plus website.

A corporation as large and widespread as Disney certainly ought to know
better.

Cordially,

Curtis Chong


-----Original Message-----
From: Greg Kearney <gkearney at gmail.com>
Sent: Monday, November 11, 2019 1:54 PM
To: Curtis Chong <chong.curtis at gmail.com>
Cc: slstanzel at kc.rr.com
Subject: Re: [NFBCS] Disney Plus Not Accessible to the Blind

Because I have access to nearly every kind of computer system and screen
reader here at work I did a quick review of this here is what I found:

MacOS/iOS with Safari and VoiceOver. Most things work, fields are reachable
and can be filled out, tabbing works.

MacOS with Chrome. Again the forms works and fields are reachable and can be
filled out. tabbing to fields works.

Windows10 with Chrome and NVDA. The NVDA cursor will not navigate to the
form field. Shift tab will eventually have you land on the fields but of
course you would need to know a field was there for this to work.  Generally
this website is not accessible with NVDA

Windows10 with Chrome and JAWS. The field is active when the page opens but
JAWS will not announce when it is over the field. So while you could enter
text in the fields there is no way to really know what information goes into
what field.

ChromeOS with ChromeVox. Interesting that this platform routed the Chromevox
cursor to the field and also announced the name of the field and that the
edit text was active. I can not offer an explanation as to why this version
of Chrome on this platform works but it fails on Windows.

I suspect we have developers with little or no accessibility background
doing their work on MacOS computers and so they only have access to
VoiceOver, this would explain the generally better performance on that
platform. However I am unable to offer an explanation as to why ChromeOS
would work as well as it does, perhaps they just got lucky.

Because I do so much of this kind of auditing I have developed all sorts of
tools to generate audit reports for this sort of thing. Enclosed is one such
report I generated from an internal page, the one asking for credit card
information, of this site.

Greg Kearney