Provide role based evaluations
Creation of modern digital content involves a great many distinct roles. There have been multiple efforts to organize the different roles that occur with each digital team.
We've taken these lists, added other roles that we didn't see included and included them here. With each role we are including tools that we think would be most useful for that role. Where appropriate we have also included links to the W3C's Accessibility Responsibility Breakdown for WCAG 2.0 requirements.
Back-end Engineer / Developer Anchor link
- See: UK DWP: Business Analyst, BBC: Accessibility, News and Business Analysts and UK Service Manual
- "As a Business Analyst in an agile team, you're involved in the critical parts where accessibility is often overlooked. Your role is often a facilitating role, to make sure user stories and conversations always include accessibility."
- "Business Analyst maps to IAAP's Analysis, Architecture, Content Strategy, and Interaction Design and Usability." - A11ycle.com
- Write the accessibility acceptance criteria (design review, documentation, high risk factors, scenarios, and awareness).
- W3C Accessibility Responsibility: Analysis.
- Tools: WebAim's WAVE Toolbar.
Content Author / Writer Anchor link
- See: USA: Accessibility for content designers
- W3C WAI - ARRM Project: Accessibility Roles and Responsibilities Mapping.
- Tools: Sa11y, Editoria11y, retextjs and HemingwayApp
- Does the content meet your readability target?
- Are there any unusual words to watch for?
- Do images have meaningful alternative text that is related to the other content?
- Are there large blocks of text, or is it broken up by appropriate headers?
- Can links be understood without any surrounding content?
- Have you stated major point(s) first before going into details?
- Limit each paragraph to one idea and keep it short.
- Use everyday words. If you must use technical terms and acronyms, do you explain them on the first reference?
- Can you omit unneeded words?
- Do you use headings, lists, and simple tables to make reading easier?
- Did you have someone review your work?
- Is it easy to scan and pick out the main points? Are headings clear and descriptive?
- Are you using inclusive language?
- Resources: CivicAction's Plain Language Guide, W3C - Writing for Web Accessibility, Blog post for content authors, Content Design London - Readability Guidelines, Singapore Government Design System - Accessibility for Content, USA OPM Information Management, Canada: Writing principles for web content, The Book on Accessibility and plainlanguage.gov.
Content Designer / Information Architecture Anchor link
Customer Experience / Service Design / Content Strategy Anchor link
- See: UK DWP: Delivery Manager and UK Service Manual
- "As a Delivery Manager you need to make sure that accessibility is considered when sizing up stories and that very feature is fully accessible before it is released."
- "Making sure accessibility is factored into each feature or activity the team's working on"
- Tools: WebAim's WAVE Toolbar.
Digital Performance Analyst / Data Analysts / Business Intelligence Anchor link
Front End Engineer / Software Engineer Anchor link
HTML & CSS Prototyping Anchor link
Product Manager / Project Manager Anchor link
- See: USA: Accessibility for product managers, UK DWP: Product Manager, BBC: Product Owner, BBC: Project Manager and NZ Government
- "Make sure the team know their responsibilities"
- W3C Accessibility Responsibility: Project Manager.
- Tools: Site-wide scanners and WebAim's WAVE Toolbar.
- Verify that personas include permanent, temporary or situational examples for vision, mobility, hearing, and cognitive disabilities.
- Ensure that accessibility is being considered with every sprint (or alternative process).
- Find ways to prioritize common, weird and critical barriers that are discovered in QA.
- Prioritise user stories for each work sprint and look for ways to include permanent, temporary & situational disabilities.
- Identify where to include people with disabilities in the process.
- Ensure you are tracking Actionable Metrics
- Resources: BBC's Product Owner Checklists & BBC's Project Managers Checklist, Planning and Managing Web Accessibility, Managing for Accessibility, Section508.gov's Accessibility Playbook, Disability Fundamentals Training for Managers, The Book on Accessibility and Accessibility for Product Managers.
Quality Assurance / Quality Control Tester Anchor link
Search Engine Optimization Anchor link
- See: UK DWP: User Researcher, UK Service Manual and NZ Government
- "As a user researcher, you will help the team to understand the needs of the people who use the service, including those users who might have impairments and use assistive technologies."
- Tools: WebAim's WAVE Toolbar
- Resources: UK GDS Blogs, How inclusive user research makes your products better, Working with Others: Accessibility and User Research, A Comprehensive Guide to Accessible User Research, What user researchers need to know about accessibility, How to Conduct Usability Studies for Accessibility, Conducting Accessibility User Research: What's Really Needed?, The Book on Accessibility and Tips For Conducting Usability Studies With Participants With Disabilities — Smashing Magazine.
Visual Design / Graphic Design Anchor link
We plan to continue to add to this as other role specific advice becomes relevant. The W3C's ARRM Project - Accessibility Roles and Responsibilities Mapping will be mapping this out in more detail in the years to come.
- Identify list of digital roles in your organizations.
- List what each role can do to enhance accessibility.
- Provide checklists personalized for each role.
- Look for educational materials that are focused on each role.
- What digital content creation roles does your organization have?
- Where are there opportunities for barriers to be introduced in your digital content?