Organizational Governance and Management Flashcards
True or false: Accessibility is a process management challenge, not just a technical challenge.
True.
It can be tempting to think of accessibility just as a technical challenge—because certainly there are technical aspects to accessibility—but it is more than a technical challenge. It is also a process management challenge. Organizations need to permanently embed accessibility into the process of design, development, and testing.
True or false: organizations can get by with a little bit of accessibility knowledge but no actual expertise.
False.
Somebody has to know accessibility very well, particularly in very technical domains of accessibility, such as web accessibility.
True or false: accessibility is possible without the support or buy-in of leadership.
False.
It is critical that the team has support and commitment from the executive level. An executive leader in accessibility not only empowers the team to make accessibility decisions and enforce policies, but an executive leader can make a public statement about the organization’s commitment to accessibility.
In the web development process, how can you incorporate accessibility in the Planning and Design phase?
Set requirements that include accessibility standards and best practices.
Design desktop interaction experience for sighted keyboard users (ensure visual focus indicator, full keyboard functionality, keyboard focus management on dynamic widgets, etc.) and blind users (correct semantic markup, alt text for images, landmarks, headings, ARIA markup on custom widgets, etc.).
Design mobile interaction experience for blind users (compatible with mobile screen readers), and low vision users (ability to zoom).
Design for low vision (ability to zoom, ability to customize colors of text/background, high contrast, etc.) and colorblindness (don’t use color alone to convey information).
Consider the auditory experience for deaf users (video captions) and deafblind users (transcripts).
In the web development process, how can you incorporate accessibility in the Creating/Testing the Content and Component phases?
For front end markup, run preliminary testing using automated tools and screen reader testing (especially of dynamic/interactive components), and manual testing.
Create text content by adding basic accessibility features, such as adding alt text to embedded images, ensuring proper table markup, logical reading order, and proper heading hierarchy for sections of content.
Test the multimedia, including deaf (captions), blind (audio descriptions), and deafblind (transcripts).
What are the four main ways to classify your accessibility efforts related to scope?
Innovation: Inventing new accessibility technologies or techniques
New Design: Incorporating known accessibility best practices into a new product or project
Retrofitting: Fixing the accessibility flaws in an existing product or project
Maintenance: Ensuring that new product features don’t break existing accessibility features
True or false: incorporating accessibility into the design process doesn’t take a lot of extra time.
Trick question: it depends.
But for organizations that are just starting to take accessibility seriously, we have to be honest and say that it does take some time, and therefore money, to do accessibility right. So how much extra time does it take? The correct answer is “it depends,” but let’s take a closer look at what it depends on.
In a best-case scenario, with all the best processes in place, an expert team, and uncomplicated content, accessibility tasks might add only 1% to 5% to the overall development time.
With an inexperienced team, an immature process, and highly complicated content, the estimate can balloon to much more than that, especially if the task is to fix existing content that is so badly inaccessible that it needs to be re-factored at a fundamental level. The accessibility tasks might double or triple the original development time in those scenarios.
What factors determine how long it will take to add accessibility into the design process?
Level of accessibility experience on the team, how mature your accessibility process is, already existing libraries of accessible widgets, patterns, and/or methods, the flexibility of your development environment, whether or not you’re retrofitting or starting from a new design, whether or not you’re using automated tools, how many technical configurations you’ll test, how much interactivity, multimedia, and data there is in the project.
How do you manage quality of accessibility in production?
Writing user stories for accessibility, writing QA tests during the planning phase, providing clear acceptance criteria for tests, high quality bug reports, and testing by users with disabilities.
What are three ways to incorporate accessibility into human resources?
Recruiting and Integrating Employees with Disabilities, Recruiting Accessibility Talent, Workforce Development and Training.
How do you mitigate risk associated with accessibility?
Internal Accountability for Compliance, The Public Relations Implications of Non-Compliance, Assessing Legal Liability.
How do you incorporate accessibility into the procurement process?
Buy Accessible Products, Verifying Product Accessibility Claims, Requiring Accessible Outcomes in Contractual Agreements, Verifying Contractor Accessibility Expertise and Capacity, Leveraging Procurement Policies to Influence Third-Party Providers
