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

Tue Nov 12 03:44:54 UTC 2019

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

-------------- next part --------------

  Warning Name: List item without list
  Warning Type: error
  Description: This <li> must be a child element of <ul>, <ol> or <menu type=\toolbar\>.
  Fix Suggestion: Correct the list structure to ensure the <li> has the correct parent element. <ul> or <ol> must be direct parent.

  Warning Name: Menu without menu item
  Warning Type: error
  Description: This menu must contain at least one <menuitem>, and menu items should be direct children of the menu.
  Fix Suggestion: Add <menuitem> as a direct child of the menu.

  Warning Name: Toolbar without list item
  Warning Type: error
  Description: This menu must contain at least one <li>, and list items should be direct children of the menu.
  Fix Suggestion: Add <li> as direct child of the <menu type=\toolbar\>

  Warning Name: List without <li>
  Warning Type: error
  Description: This list must contain at least one <li>, and list items should be direct children of the list.
  Fix Suggestion: Add <li> as direct child of <ul> or <ol>

  Warning Name: Deprecated element
  Warning Type: error
  Description: The page contains deprecated HTML elements.
  Fix Suggestion: Remove the deprecated elements and use CSS instead

  Warning Name: Generic page title
  Warning Type: error
  Description: The page title is too generic.
  Fix Suggestion: Use a title that better describes this page.

  Warning Name: Incorrect or missing page language
  Warning Type: error
  Description: The <html> element must have a lang attribute with a valid value.
  Fix Suggestion: The <html> element must have a valid lang attribute with a value matching the page language, as defined in RFC1766. Example: lang=\en-US\

  Warning Name: Element with invalid lang attribute
  Warning Type: error
  Description: The element has an invalid lang attribute value; it must be a valid language code as defined by RFC1766.
  Fix Suggestion: Use valid language codes as defined in RFC1766. Example: lang=\en-US\

  Warning Name: Fieldset without form control
  Warning Type: error
  Description: Fieldsets must contain at least one element that accepts input.
  Fix Suggestion: Only use a fielset for a group of form controls, e.g. for a group of radio buttons or checkboxes.

  Warning Name: Legend without text
  Warning Type: error
  Description: Legends must contain textual content.
  Fix Suggestion: Add text into the legend, it must not be empty.

  Warning Name: Missing label
  Warning Type: error
  Description: This input element has no associated label. Each input element must have a label assigned.
  Fix Suggestion: Assign an explicit label using a \label\ element. The value of its \for\ attribute needs to be the id value of this input element. 

  Warning Name: aria-labelledby doesn't point to text
  Warning Type: error
  Description: The element programmatically link to the input using the \aria-labelledby\ attribute must contain textual content.
  Fix Suggestion: Check if aria-labelledby points to the correct element. It needs to point to an element that contains text.

  Warning Name: Implicit label
  Warning Type: warning
  Description: The use of implicit labels is not recommended. A label is implicit when it does not have a valid \for\ attribute, but rather contains the input element that it relates to.
  Fix Suggestion: Use explicit labels instead, i.e. use <label> as sibling to the form element instead of its parent, and add a for= attribute to the label that points to the id of the form control.

  Warning Name: <button> without text
  Warning Type: error
  Description: Button tags must have textual content.
  Fix Suggestion: A button must have text. Add text content (preferred) or aria-label where text is not possible

  Warning Name: <input type=\image\> without alt
  Warning Type: error
  Description: Inputs of type \image\ must contain an \alt\ attribute describing the content of the image.
  Fix Suggestion: Add an alt attribute, its value needs to be text that describes the action of the input.

  Warning Name: Input button without label.
  Warning Type: error
  Description: Buttons must have a meaningful label.
  Fix Suggestion: Use the value attribute to add the label of the input button, e.g. <input type=\button\ value=\button label\>.

  Warning Name: Related checkboxes or radio buttons must be grouped within a fieldset.
  Warning Type: warning
  Description: Related checkboxes or radio buttons must be grouped within a fieldset.
  Fix Suggestion: Check if radio buttons and checkboxes are part of a group of related controls. If there is a group of related controls then use a fieldset to group them.

  Warning Name: Empty heading
  Warning Type: error
  Description: This heading has no calculated text content.
  Fix Suggestion: Remove the headings tags if the heading is not needed, or add some content into the heading.

  Warning Name: Multiple h1
  Warning Type: error
  Description: Multiple h1 elements found; the document must have exactly one h1 element.
  Fix Suggestion: Change the heading structure. There must be only one h1 heading. It should be the first heading and should be at the start of the main content.

  Warning Name: Heading inside table header
  Warning Type: error
  Description: Headings must not be present inside table headers.
  Fix Suggestion: Remove heading tags from inside table headers.

  Warning Name: No visible h1
  Warning Type: warning
  Description: This h1 heading is hidden. Ensure the document has got exactly one visible h1 heading.
  Fix Suggestion: Ensure there is exactly one visible h1 heading. If there is no visible h1 then add one, or if there is an existing h1 heading that is visually hidden make it visible.

  Warning Name: Empty link
  Warning Type: error
  Description: This link contains no text content.
  Fix Suggestion: Either remove the link or add link text. If the link contains an image add a text alternative for the image.

  Warning Name: Link exceeds maximum length (400 characters)
  Warning Type: error
  Description: The calculated link text for this link exceeds the maximum permissible length (400 characters) and must be reduced.
  Fix Suggestion: Reduce the text inside the link. Consider having only some of the text as link, e.g. only the call to action.

  Warning Name: Link exceeds recommended length (200 characters)
  Warning Type: warning
  Description: The calculated link text for this link exceeds the maximum recommended length (200 characters) and should be reduced if possible.
  Fix Suggestion: Consider reducing the text inside the link. It might be possible to have only some of the text as link, e.g. only the call to action.

  Warning Name: Duplicated link text
  Warning Type: error
  Description: This link has the same link text as another link with a different href value. Links pointing to different destinations should have unambiguous link text.
  Fix Suggestion: Change the link text so each link uniquely describes the link target.

  Warning Name: duplicated navigation label
  Warning Type: error
  Description: The \aria-label\ attribute on this element was also set on another element with a \navigation\ role. The \aria-label\ attribute must be unique.
  Fix Suggestion: Change the aria-label to make the label of each navigation landmark unique.

  Warning Name: Missing main
  Warning Type: error
  Description: The page does not have a \main\ role.
  Fix Suggestion: Add <main> or role=\main\ around the main page content.

  Warning Name: Multiple main
  Warning Type: error
  Description: The page has more than one \main\ role.
  Fix Suggestion: Remove the additional <main> or role=\main\ and leave only a single one around the main content of the page.

  Warning Name: Missing navigation label
  Warning Type: error
  Description: If there are multiple elements with a \navigation\ role, each must have a unique \aria-label\ attribute.
  Fix Suggestion: Add aria-label to each <nav> and each role=\navigation\. Ensure the label uniquely describes each navigation landmark.

  Warning Name: Empty tabindex
  Warning Type: error
  Description: Elements should not have an empty tabindex.
  Fix Suggestion: Remove the tabindex attribute if it is not needed, or add valid values. You can use tabindex=\0\ or tabindex=\-1\

  Warning Name: <dl> without <dt> and <dd>
  Warning Type: error
  Description: This <dl> must contain at least one <dt> and one <dd>, and list items should be direct children of the list.
  Fix Suggestion: Add <dt> and <dl> as direct chidren of the <dd>.

  Warning Name: aria-labelledby doesn't match any id
  Warning Type: error
  Description: The \aria-labelledby\ attribute must have a value matching the id of an element within the DOM.
  Fix Suggestion: Correct the value of aria-labelledby, ensuring it matches the id of the element you want to use as label.

  Warning Name: Hidden heading
  Warning Type: warning
  Description: This heading is hidden. Ensure that if the heading is made visible, the document outline is still correct.
  Fix Suggestion: Check that the headings structure is still correct when the heading is made visible.

  Warning Name: tabindex values
  Warning Type: error
  Description: Elements should not have an explicit tabindex greater than 0.
  Fix Suggestion: Use tabindex=\0\ and change the DOM order to correct the navigation order. If you don't want the element included in the tab order then use tabindex=\-1\

  Warning Name: Layout table coded as data table.
  Warning Type: error
  Description: Please check this: a table is being used for tabular data.
  Fix Suggestion: This table doesn't appear to be a valid data table. Do not use tables for layout purposes.

  Warning Name: Incorrect heading structure
  Warning Type: error
  Description: This heading was preceded by a heading at the wrong level; the heading hierarchy must be sequential without skipping heading levels.
  Fix Suggestion: Change the heading levels to correct this error. Ensure you don't skip heading levels.