A RACI chart is a project-management tool used to clarify responsibilities and roles when multiple team members are working on a complex project. Project participants are listed by role in Row 1. The tasks or stages comprised by a project are listed in Column 1. Within the chart, the nature of each participant/role’s responsibility for a given task is noted with an R, A, C, or I. RACI stands for Responsible, Accountable, Consulted, and Informed.
Responsible (R): directly in charge of executing a project or one of its parts.
Accountable (A): accountable for a project’s completion and its outcomes. This may not be the person directly executing the work, and often is filled by a project manager overseeing progress, or an administrator shaping or overseeing a project.
Consulted (C): reviews a project or a task undertaken as a part of a project.
Informed (I): informed of a project’s progress and completion, but not directly involved in the work.
Setting Policy for Larger Institutions
Head of Institution
Library Department Head
Product/ Project Manager
Functional Managers
Project Implementers
Accessibility Specialist
Sets institution-wide goals and priorities to include digital accessibility
R/A
C
C
C
I
C
Communicates importance of digital accessibility
R
R
R
R
R
R
Creates staffing structures that accommodate accessibility work across all of the institution’s portfolio of work
A
R
R
R
C/I
C/I
Creates budget with the necessary funding to provide accessibility services
R
C/I
C/I
C/I
C/I
Creating institution-wide accessibility policies that provide guidance, standards, and governance
C
C/A
C/I
C/I
C/I
R/A
Putting accessibility policies into practice
I
I
A/C/I
A
R
R
Resourcing projects to accomplish accessibility work
I
C/
R
C/I
C/I
New Website Project for Larger Institutions
Senior Administrator
Project Manager/ Product Manager
Functional Manager
Developer
UX Designer
Visual Designer
Content Author
Accessibility Specialist
Metadata Analyst
Creates project plans (may include budget, resourcing, and timeline)
C/I
R/A
C
I
I
I
I
I
I
Designs technical architecture
I
A
R
C
C
I
I
C
I
Designs user experience (UX) (including interactions, page layout structure, and information architecture)
C
C/A
C
C
R/A
C
C/I
C
I
Does visual design (color palette, font styling, page layout g)
C
C/I
I
C/I
C
R/A
C/I
C
I
Designs metadata for digital objects that will move through the website
I
C
C/I
C/I
C
I
C
C
R/A
Creates content for website
C/I
C
I
C/I
C
C
R/A
C
C
Develops front end
I
C
A
R
C
C
C/I
C
I
Develops back end
I
C
A
R
C
I
I
C
C
Tests and evaluates for usability
I
I
I
I
R/A
I
I
C
I
Tests front-end code
I
I
C/I
R
C
I
I
R/A
I
Tests accessibility test UI
I
I
I
C
C
C
C
R/A
I
Fixes any accessibility bugs
I
I
C
R
C
I
I
A/C
I
Maintenance Phase for Larger Institutions
Project Manager/ Product Manager
Technical Lead
Developer
UX Designer
Visual Designer
Content Author
Accessibility Specialist
Metadata Analyst
Monitors long-term success of accessibility work undertaken during implementation. Schedule periodic accessibility evaluations, noting accessibility issues throughout life cycle of website or service.
A
C
I
C
I
I
R/A
I
Assesses new features, content, or infrastructure maintenance work
A
C
C
C
C
C
R
C
Receives requests for remediation
A
C
C
C
I
C/I
R
C/I
Decides course of action based on remediation request