DisneyNOW Design : Accessibility

<body>
    <a href="#maincontent">Skip to main content</a>
    ...
    <main id="maincontent>
        <h1>Heading</h1>
        <p>This is the first paragraph</p>
    </main>
</body>

Useful Links:

Designing for Accessibility and Inclusion - https://www.smashingmagazine.com/2018/04/designing-accessibility-inclusion/

Principles for Accessible Design - http://ncdae.org/resources/factsheets/principles.php

Universal vs. Accessible Design - https://www.washington.edu/doit/what-difference-between-accessible-usable-and-universal-design

What is Accessibility?

Accessibility involves two key issues: how users with disabilities access electronic information and how web content designers and developers enable web pages to function with assistive devices used by individuals with disabilities.

For instance, a website is accessible if all people, including disabled and elderly people, can use it.

Why is it important to us?

“The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect.”

The more inclusive the application is, the broader the reach. Why exclude a segment of the population? While it might not always be easy, you might discover that improving the accessibility of your site can improve the experience for all users.

• Accessibility is the right thing to do- It is essential that the Web be accessible in order to provide equal access and equal opportunity to people with diverse abilities. 

• Benefits all users- 

• Uses innovative technology

• Creates market opportunity

19.6% of the U.S. population as having some sort of disability. Within that group are individuals with visual, hearing, cognitive, and motor impairments.

Who else does accessibility benefit?

• people using mobile phones, smart watches, smart TVs, and other devices with small screens, different input modes, etc.

• older people with changing abilities due to ageing

• people with “temporary disabilities” such as a broken arm or lost glasses

• people with “situational limitations” such as in bright sunlight or in an environment where they cannot listen to audio

• people using a slow Internet connection, or who have limited or expensive bandwidth

Accessibility overlaps with other best practices such as mobile web design, device independence, multi-modal interaction, usability, design for older users, and search engine optimization (SEO). Accessible websites can have better search results, reduced maintenance costs, increased audience reach, and demonstrate corporate social responsibility (CSR).

1. Intro/Facts
   1. Why have an accessibility review?
      
      1. It's the law.
      2. We want our content and services to reach the widest possible audience.
      3. Accessible websites provide a better experience for all users regardless of ability.
   2. 15-20% of the population has some form of disability
   3. Standards
      1. Title III of The Americans with Disabilities Act (ADA)
         1. Requires businesses to provide public accommodations for the disabled.
         2. Language expanded to include digital accommodations and emerging technologies.
      2. Section 508 of the Rehabilitation Act of 1973 (508)
         1. Required for Government agency websites
            1. Also private companies with government contracts
         2. Specific to the U.S.
      3. WCAG 2.0 (Web Content Accessibility Guidelines)
         1. Specific to Web Content only, not User agents (UAAG) or Authoring Tools (ATAG)
         2. Used by ADA to measure compliance with Title III
         3. Accepted Internationally
         4. WCAG 2.1 (2018) will expand the types of disabilities and technologies
            1. low vision, learning disabilities, speech disabilities and multiple disabilities
            2. small screens, touch screens and other features common to mobile devices and tablets
      4. WAI-ARIA (Web Accessibility Initiative – Accessible Rich Internet Applications)
         1. A set of standards and best practices for making dynamic content, custom UI components, and Web apps accessible
2. Succes Criteria
   1. The Good News: 90% of accessibility comes with good development practices
      1. Web standards like HTML and User Agents (ie. browsers) have accessibility built in
      2. Platforms and libraries, like Wordpress and Bootstrap, have standards built in.
   2. The Bad News: A high accessibility score does not mean your site is fully accessible
      1. As of yet, no tool can perform a completely automated assessment on the WCAG 2.0 guidelines.
      2. Automated tests check for standards and best practices, but only a human can verify that a web page is accessible.
      3. Non-standard or unconventional design specifications can introduce accessibility issues
3. Testing Scope
   1. Web Standards and practices (automated test) 
   2. Unique Templates and components such as forms and navigation
   3. Use Cases
      1. Can the user get to your site?
      2. Can the user navigate within your site?
      3. Can the user complete a task or goal (ex, buy something or get information) and get notification upon success?
      4. In the event of failure or error, can the user fix the error/failure?
4. Typical timeframe
5. Requesting a review
   1. Intake Process
6. summary of steps taken by our team to review a site and the expected output. 

Open Qs

<body>
    <a href="#maincontent">Skip to main content</a>
    ...
    <main id="maincontent>
        <h1>Heading</h1>
        <p>This is the first paragraph</p>
    </main>
</body>