[Draft] Accessibility Roles and Responsibilities Mapping (ARRM) Overview
What is ARRM
Accessibility Roles and Responsibilities Mapping (ARRM) helps define which roles (designer, developer, writer, etc.) have which responsibilities for meeting which aspects of the Web Content Accessibility Guidelines (WCAG) requirements.
ARRM assigns primary, secondary, and contributor level responsibilities for tasks.
ARRM currently provides an example of typical roles and responsibilities for WCAG success criteria. It is also a tool for project managers to assign different responsibilities across roles within their team.
Typical Roles and Mapping
ARRM provides one approach for defining roles and responsibilities.
You can use these as they are, without doing any more work to customize them.
- Role Definitions
- Accessibility Roles and Responsibilities Mapping — Table of Success Criteria
which is also available as separate lists:
Customizing ARRM for Your Situation
ARRM also guides organizations that want to customize their own accessibility roles and responsibilities mapping, based on the roles and considerations in their organizations.
- Customizing ARRM for Your Situation explains how to use the Role Definitions and the Decision Tree to create your customized Accessibility Responsibilities Mapping.
- ARRM Decision Tree provides the steps for deciding which roles have which level responsibilities for success criteria or your organization’s accessibility checkpoints.
Future Work
Future work on ARRM includes breaking down success criteria into multiple sub-points, and assigning those sub-points to roles.
Back to Top