More and more, companies are turning to web technology and online video for a variety of corporate and enterprise communications. Be it for training, branding, tutorials, or events, this brings up new challenges for companies that need to make their video and web content accessible to individuals with disabilities.
In this webinar, Deque's John Foliot will outline an A to Z approach to sustainable corporate accessibility, providing a roadmap for companies of all sizes. He'll demonstrate how to make accessibility a part of your organization's program, examining the role that everyone in your organization plays in achieving and maintaining accessible digital materials.
This presentation will cover:
Legal requirements and applicable lawsuits
How to make corporate web, video, and training content accessible
Strategies for building accessibility into your workflow
The Roadmap to Sustainable Corporate Accessibility
1. The Road to Sustainable Corporate
Accessibility
Lily Bond (Moderator)
Director of Marketing,
3Play Media
lily@3playmedia.com
www.3playmedia.com
twitter: @3playmedia
live tweet: #a11y
Type questions in the control panel during the presentation
This presentation is being recorded and will be available for replay
To view live captions, please follow the link in the chat window
John Foliot
Principal Accessibility Strategist
Deque
5. •Promotes the Vision through
clear requirements and tangible
support
•Fosters a team spirit
•Integrates Accessibility
requirements in other corporate
guides
•Be specific in what you ask for,
generous in what you accept
Executive Management
7. Web Accessibility Champion
Director level or above
• Has signing authority and the authority
to make things happen
Web Accessibility Champion understands
• The types of issues that people with
disabilities face on the Internet
• The many benefits of accessibility
compliance
• The legal ramifications of failing to
comply.
8. Web Accessibility Specialists by Roles
• Providing their respective fields of expertise with related
accessibility requirements, guidelines and best practices.
• Offering support and training to their team members so
everyone understands their roles and responsibilities
when it comes to creating accessible products.
• Supporting their team with accessibility related
knowledge.
• Assisting stakeholders in reviewing production
to intercept issues before they become part of
the lifecycle.
10. Develop Digital Accessibility Policies
Internal Accessibility Policy and Guidelines
• Conformance Level: conform to the W3C Web Content
Accessibility Guidelines 2.0 Level AA (WCAG 2.0 AA).
• Scope: applies to:
• All areas of both internal and external Web Sites
• All new, updated, and existing Web pages including:
• All content and functionality produced or updated
internally.
• All content and functionality provided by third-party
developers.
11. Develop Digital Accessibility Policies
Internal Accessibility Policy and Guidelines also
address:
• Milestones & Compliance Timeline
• Known Limitations
• Responsibilities
• Accountability and Monitoring
• Accessibility Policy Violations
• Policy Review
12. Develop Digital Accessibility Policies
Other Polices:
• Web Accessibility Exception Procedure for accessibility
violations
• 3rd Party Vendor Accessibility Policy
• Social Media Accessibility Policy
14. Establish a Communication Plan
The Accessibility Communication Plan creates a bridge that connects
Accessibility Policies to the people, processes, and tools:
• Decision makers
• Implementers
• Information Technology
• Procurement
• Technology Users
• Vendors
15. Establish a Communication Plan
Key Messages:
1. Effective use of technology solves problems that without
technology were much more difficult or impossible to solve
2. Accessibility is not the same thing as accommodation
3. Web Accessibility is not necessarily more expensive, if it is planned
from the beginning
4. Web Accessibility is an important component of delivering services
electronically
5. The need for accessible technology is growing rapidly
6. Web Accessibility is a journey not a destination
16. Develop Digital Accessibility Policies
Adding Web Accessibility to a Customer
Service Plan
It is important to understand that most
accessibility lawsuits do not start with an
inaccessible website. Lawsuits usually start
with a poor user experience either in a
physical location, or over the phone or
email, and through poor customer service
that is either insensitive to the request of
the disabled person or in some way agonizes
or frustrates the person with disabilities.
18. Establish a Learning Plan
Provide sustainable role-based
accessibility training to web developers,
designers, quality assurance testers,
content contributors and other
stakeholders across your organization.
Options include:
• In person training
• Live training via online meeting software
• Pre-recorded/eLearning training
20. Immediate Strategy: Repair, Replace, or Retire
While the requirement for
accessibility applies to all of
your digital presence, it is
important to take a phased
approach.
It is at this point that decisions
around repairing existing
content, replacing it as part of
a new design deployment, or
in some instances retiring
legacy content of questionable
value should be undertaken.
22. Long-Term Process Plan:
Plan, Design, Build, & Test
• Design » Plan for Accessibility at the
Requirements Stage of Projects
• Code » Equip & Empower for Accessible
Development
• Test » Test & Remediate for Accessibility
• Launch » Sustain Accessibility
26. 226
John Foliot
Principal Accessibility
Strategist
Deque
Lily Bond
Director of Marketing
3Play Media
lily@3playmedia.com
617-764-5189 x119
Upcoming Webinars
Advanced Workflows for Closed Captioning
Quick Start to Captioning
The Future of Closed Captioning in Higher Ed
Register for our webinars at:
http://www.3playmedia.com/webinars/
Q&A
Please type your questions into the window in your control panel. A recording of this webinar will be available for replay.
Editor's Notes
Vision
Your Accessibility Roadmap is designed to support your organization as it makes its way through the different phases required to successfully integrate web accessibility in the DNA of your organization. The most critical step is one of corporate vision. Without full support and a clear vision from your senior management, you can quickly lose your way.
Creating a Web Accessibility Leadership Team
Reviewing and Recommend External and Internal Accessibility Policies
Finalizing and Approve Accessibility Policy
Establishing an Accessibility Communication Plan
Assessing Current State of Web Accessibility
Establishing a Prioritization and Remediation Process
Establishing an Accessible Web Development and QA Process
Establishing an Accessibility Training and Documentation
Planning a Monthly Web Accessibility Monitoring and Reporting Process
Web accessibility is not a project with a starting date and an end date. It’s a program.
What this means is that in order to obtain lasting success, web accessibility needs to be integrated into the entire web production process much like the security field.
The easiest way of achieving this is through the establishment of a leadership team
Communication/Promotion
Communicate accessibility policies within the entire organization.
Promote accessibility awareness in all spheres of activities and core groups.
Training Resources
Identify the various accessibility training needs for key audiences.
Provide training needed for staff to successfully implement accessibility policies.
Provide internal documentation on Web Accessibility Style Guides and Guidelines, including, but not limited to:
Accessibility Development Guide including code samples
Accessibility use cases
Accessibility testing plans
Accessibility Governance
Standards Interpretation and Development:
Provide technical guidance on best practices and conformance criteria for meeting WCAG 2.0.
Keep up to date on the evolving accessibility standards and best practices (508 Refresh, CVAA, HTML5, ARIA).
Monitoring Compliance:
Monitor compliance (monthly) to accessibility policy.
Report on accessibility implementation plan, policy and progress (monthly, every other month, quarterly, bi-annually, annually).
Exception Reviews:
Review any requests for exceptions to [client]’s digital accessibility polic(ies).
Provide guidance on how to resolve accessibility issues when an exception is not appropriate.
Provide risk analysis and recommendations on exceptions to Leadership.
Maintain documentation on all exceptions. Review regularly for increased risk.
Production Life Cycle
Backlog: Be available for questions from designers and the UX team as they start rough mockups of items in the backlog stack.
Planning Phase: Be present in the meetings, identifying design choices that will present accessibility challenges, and helping the team balance the amount of effort required to make that choice accessible versus small design adjustments. During those sessions the Web Accessibility Coordinator could also highlight sections of the mockup where common errors are made, and offer suggestions for the development team on how to avoid them. Comments should be provided during the review of graphic and interactive design models.
Development: Be available for questions and sometimes coach code fixes or offer resources.
Functional Testing: Be available for questions to the QA team and check issues not grasped by the QA.
Regression Testing: Be available to help interpret the severity of new issues that show up in the output of WorldSpace Suite when it’s being compared to that week’s regular reporting output from the Production site.
Generally this person would be at the director level or above, who has signing authority, and has the authority to make things happen. This is not a paid position, nor does it require a lot of expertise or time, except for a basic understanding of the types of issues that people with disabilities face on the Internet, the many benefits of accessibility compliance, and the legal ramifications of failing to comply.
This type of commitment from senior management is critical for success. The Accessibility Champion role will provide support and resources to the Web Accessibility Coordinator(s), and should be consulted when important budget decisions are being made, and will reiterate the organization’s commitment to inclusion. They will take interest in the Web Accessibility Coordinator and ask this person what they need to get the job done, and ensure they get it. The Web Accessibility Coordinator would be within this person’s authority.
Finalizing and approving the Web Accessibility Policies is the first real milestone that will be shared with internal stakeholders and production teams. It’s the organization’s statement or commitment towards digital inclusion and diversity support.
Review the proposed internal accessibility policies with the Accessibility Leadership Team, as well as upper management and the legal department.
Review feedback from different stakeholders and make required adjustments to the policy.
Submit the policy for final Leadership/Legal approval.
Once the final approval has been received, go through the proper channels to communicate the policy across the organization and follow up with a strategy to communicate about the commitment.
Milestones & Compliance Timeline – varies by organization and readiness
Known Limitations - providing alternative methods of ensuring accessibility of material or other accommodation.
Responsibilities – Business Unit or equivalent, Web Developers, Content Providers and Document Authors,
Accountability and Monitoring - Web Accessibility Coordinator and Leadership.
Accessibility Policy Violations – escalation process for Web Accessibility Coordinator
Policy Review – scheduled reviews
The purpose of creating an Accessibility Communication Plan is to implement the Accessibility Policies adopted by putting in place processes, tools, and support (e.g., guidelines and training) that make accessibility simply the way your organization wants do business from a certain point, moving forward.
There are usually up to four main categories of audiences for the Accessibility Communication Plan: decision makers, Web accessibility implementers (information technology and procurement personnel), technology users, and vendors.
When new technology is implemented, how can we improve accessibility for users who have previously been unable to access this service?” The new mantra becomes: Technology is the solution, not the barrier.
Accommodation is used when an accessibility solution is determined to not be feasible.
Planning for accessibility is significantly cheaper than dealing with accessibility issues at the end of a project.
When implemented properly, an accessible web site or service says “We’re open for business” to everyone.
Accessibility impacts more than just people with disabilities: it may also be your Mother, my Father, or maybe some day you!
100% accessibility is a goal that is never fully realized. The purpose of creating and implementing an Accessibility Communication Plan is to identify and put in place the processes, tools, and training that enables your organization to procure or develop content that best meet accessibility standards.
Training and documentation is a fundamental part of integrating web accessibility into the DNA of any organization and into the development lifecycle of all digital projects.
While training helps resources develop the skills required to do the work, documentation ensures that new resources pulled into the projects can quickly integrate the existing process and also make it their own.
Breaking your digital presence down into major web sites and major projects is a great place to start. What matters is considering the litigation risks and user impacts for each site and application and place them on the prioritization grid from critical user impact and high litigation risks to minor use impact and low litigation risks.
It is at this point that decisions around repairing existing content, replacing it as part of a new design deployment, or in some instances retiring legacy content of questionable value should be undertaken.
Design » Plan for Accessibility at the Requirements Stage of Projects
Set WCAG 2.0 AA as the standard for Accessibility
QA Team provides standard use cases
Code » Equip & Empower for Accessible Development
Provide web development and accessibility testing tools
Integrate accessibility process with existing IDE and testing tools
Provide role-specific accessibility training as needed
Test » Test & Remediate for Accessibility
Testing for Accessibility
Centralized automated tests for accessibility
Expert accessibility/usability evaluation with assistive technology
Users testing with people with disabilities.
Remediating for Accessibility
Prioritize accessibility errors
Resolve accessibility errors
Retest to ensure compliance with policy
Launch » Sustain Accessibility
Continuous monitoring of accessibility compliance including WorldSpace Suite weekly crawl of production site
Accessibility verification of third-party content/functionality before purchase
New employee training on accessibility
A formal accessibility validation process needs to be put in place throughout the development lifecycle, so developers can proactively intercept bugs and issues as they are created.
While this process also needs to involve the QA teams, making sure developers have access to a tool that can flag the most basic issues is critical to ensuring efficiency.