One of the universal truths in the world of software and web development is that the less bugs in a system the more money is saved and more human resources can be applied to new development that adds value. The best way to reach the goal is to avoid the bugs in the first place – which typically requires testing the system regularly during the software development lifecycle. When it comes to accessibility testing it is often the case that testing is not performed on systems until after the system has been released to users. In such a scenario, an organization’s level of risk is at its highest, as people are using the system. Therefore the organization and its developers require sufficiently informative data output from the accessibility testing which is detailed, clear, and actionable. It doesn’t do the system’s owner any good to deliver a report filled with a bunch of accessibility violations unless that report also includes information to help them fix their problems. They need to know what their problems are, where their problems are, and how to fix them. There’s also an additional item they need to know: When to fix them. Experience Level:
Beginner - Assumes no prior knowledge of topic. Prerequisite Knowledge: Basic knowledge of web accessibility would be beneficial but not required. Skills/Knowledge Gained:
Attendees will come to understand the various concerns when determining how to manage the remediation of accessibility problems in websites and web-based applications to avoid unnecessary strain on budgets and resources while providing high positive impact for users with disabilities.