The Accessibility Roles and Responsibility Mapping (ARRM) is a framework developed by the W3C’s EOWG to help teams break down Web accessibility requirements by roles.

1. AccessU 2020 – Introducing ARRM: A Framework to Fight Accessibility Apathy
Introducing ARRM
A framework to fight accessibility apathy
AccessU 2020 (Virtual)
May 19th, 2020

2. –AccessU 2020 Introducing ARRM: A Framework to Fight Accessibility Apathy
Who own accessibility on your teams?
If you’re that person, how’s that working out for
you so far? Do you wish things were different?

3. –
Getting us started
Using the chat feature
Locate the Chat feature at the bottom of your
screen. Turn on the Chat window and share who
owns accessibility on your team, or more globally,
in your organization.
If you’re that person, how’s that working out for
you so far? Do you wish things were different?
AccessU 2020 Introducing ARRM: A Framework to Fight Accessibility Apathy

4. AccessU 2020 – Introducing ARRM: A Framework to Fight Accessibility Apathy
Our team / your speakers
EAUDENIS BOUDR
Deque Systems
db@deque.com
BILL TYLER
Optum Technology
btyler@optum.com
JENNIFER CHADWICK
Siteimprove
jcha@siteimprove.com
LEWIS PHILLIPS
AT&T
lewis_phillips@labs.att.com
SEAN KELLY
Optum Technology
sean_kelly@optum.com
MICHAEL MISTAK
Diamond
michael.mistak@dws.la

5. –
Getting us started
Annotation toolbar
Throughout this training, you will be required
to make use of Zoom’s Annotation toolbar.
It can be found under the View Options menu.
NOTE:
This menu item will only be available when the instructor’s
screen is being shared.
AccessU 2020 Introducing ARRM: A Framework to Fight Accessibility Apathy

6. –
Getting us started
AccessU 2020 Introducing ARRM: A Framework to Fight Accessibility Apathy
Using the annotation toolbar
• X Close: Dismiss the annotation toolbar.
• Mouse: Returns your cursor to the
regular mouse.
• Text: Type text on the shared screen.
• Draw: Draw with a pen or another tool.
• Stamp: Insert predefined icons like a
check mark or star.
• Arrow: Add an arrow with your name on
the shared screen.
• Eraser: Erase any annotations you have
done.
• Format: Open formatting options for text
such as colors.
• Undo: Remove your last changes.
• Redo: Add the annotations you removed
by clicking Undo.
• Clear: Remove your own annotations.
• Save: Grab a capture of the screen.

7. –
Getting us started
Where are you from?
Using the annotations
stamps, use the to
indicate where you are
located on the map.
AccessU 2020 Introducing ARRM: A Framework to Fight Accessibility Apathy

8. –
ACCESSIBILITY TOP 10 LIST OF CHALLENGES
What are some of the challenges your team faces, when it comes to meeting accessibility standards?
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
AccessU 2020 Introducing ARRM: A Framework to Fight Accessibility Apathy

9. –AccessU 2020 Introducing ARRM: A Framework to Fight Accessibility Apathy
Genesis of this project
You can only witness so many projects crash and burn due
to lack of proper planning before you do something about it.

10. –
Genesis of this project
Breaking down accessibility by roles…
2010 - AccessibilitéWeb comes to
CSUN with a wild, novel idea…
2011 - The ARB resource is made
available as part of WAI-Engage
(see link below)
2013 - The Canadian govt. adopts
ARB as part of its Web Experience
Toolkit framework
Resource
https://www.w3.org/community/wai-engage/wiki/Accessibility_Responsibility_Breakdown
AccessU 2020 Introducing ARRM: A Framework to Fight Accessibility Apathy

11. –
Genesis of this project
And thus, ARRM picks up steam
2014 - Independent research
on role-based accessibility at
Optum Technology (Bill)
2018 - ARRM is launched at the
EOWG, with full team coming
together over the next year
2020 – And here we are today
virtually at AccessU 2020!
AccessU 2020 Introducing ARRM: A Framework to Fight Accessibility Apathy

12. –AccessU 2020 Introducing ARRM: A Framework to Fight Accessibility Apathy
Introducing the ARRM project
How can we truly help organizations distribute accessibility
responsibilities across an entire cross-functional team?

13. –
Introducing the ARRM project
ARRM’s framework introduction
Resource landing page, explaining
how to use the ARRM framework
and providing some context such
as whom should own accessibility
and how to refer to the different
parts of this resource.
Resource
http://bit.ly/wai-arm-resource
AccessU 2020 Introducing ARRM: A Framework to Fight Accessibility Apathy

14. –
Introducing the ARRM project
ARRM’s role definition document
A list of all the different roles that
can exist within a cross-functional
product team: business, design,
implementation and QA Testing
roles. Meant to support the decision
making process.
Resource
http://bit.ly/wai-arm-definition
AccessU 2020 Introducing ARRM: A Framework to Fight Accessibility Apathy

15. –
Introducing the ARRM project
ARRM’s role-based decision tree
Inspired by the concept of a RACI
matrix, and built as a framework to
define ownership for accessibility in
a cross-functional product team
with various levels of ownership
(primary, secondary, contributor).
Resource
http://bit.ly/wai-arm-decision
AccessU 2020 Introducing ARRM: A Framework to Fight Accessibility Apathy

16. –AccessU 2020 Introducing ARRM: A Framework to Fight Accessibility Apathy
Putting the ARRM framework to the test
Break down into groups of 4-5 people and test drive the framework.
Can you easily assign ownership levels to typical accessibility tasks?

17. –
Putting ARRM to the test
Decision tree flow
As a reminder of the framework logic…
1. Is this checkpoint driven by Business/Non-Functional requirements?
2. Is this checkpoint about Visual Design?
3. Is this checkpoint about Content Authoring?
4. Is this checkpoint about UX Design?
5. Is this checkpoint about Implementation?
6. Is this checkpoint about Testing?
7. IF NONE OF THE ABOVE, then it’s a Management concern.
AccessU 2020 Introducing ARRM: A Framework to Fight Accessibility Apathy

18. –
Putting ARRM to the test
Workshop activity
As a group, assign roles and responsibilities for the following tasks
Example checkpoints Ownership levels
Primary Secondary Contributor
Keyboard focus advances across the page in a meaningful way
Keyboard focus is not applied to non-active or static elements
Headings follow a hierarchical sequence without skipping levels
Elements that visually look like headings are marked up as such
The main heading of the page describes the content of the page
AccessU 2020 Introducing ARRM: A Framework to Fight Accessibility Apathy

19. –AccessU 2020 Introducing ARRM: A Framework to Fight Accessibility Apathy
What does your team’s matrix look like?
Let’s take a moment to compare our results from one team to
the next. How different are those results, on this small sample?

20. –
Putting ARRM to the test
Workshop activity(checkpoint no. 1)
AccessU 2020 Introducing ARRM: A Framework to Fight Accessibility Apathy
Keyboard focus advances across
the page in a meaningful way
Ownership levels
Primary Secondary Contributor
Team 1
Team 2
Team 3
Team 4
Team 5
Team 6

21. –
Putting ARRM to the test
Workshop activity(checkpoint no. 2)
AccessU 2020 Introducing ARRM: A Framework to Fight Accessibility Apathy
Keyboard focus is not applied to
non-active or static elements
Ownership levels
Primary Secondary Contributor
Team 1
Team 2
Team 3
Team 4
Team 5
Team 6

22. –
Putting ARRM to the test
Workshop activity(checkpoint no. 3)
AccessU 2020 Introducing ARRM: A Framework to Fight Accessibility Apathy
Headings follow a hierarchical
sequence without skipping levels
Ownership levels
Primary Secondary Contributor
Team 1
Team 2
Team 3
Team 4
Team 5
Team 6

23. –
Putting ARRM to the test
Workshop activity(checkpoint no. 4)
AccessU 2020 Introducing ARRM: A Framework to Fight Accessibility Apathy
Elements that visually look like
headings are marked up as such
Ownership levels
Primary Secondary Contributor
Team 1
Team 2
Team 3
Team 4
Team 5
Team 6

24. –
Putting ARRM to the test
Workshop activity(checkpoint no. 5)
AccessU 2020 Introducing ARRM: A Framework to Fight Accessibility Apathy
The main heading of the page
describes the content of the page
Ownership levels
Primary Secondary Contributor
Team 1
Team 2
Team 3
Team 4
Team 5
Team 6

25. –
Introducing the ARRM project
ARRM’s role-specific templates
Accessibility is a team effort, and
everyone has a role to play! The
first iteration of these templates
helps UX/UI designers, copywriters
and developers get started with
accessibility.
Resources
http://bit.ly/wai-arm-ux
http://bit.ly/wai-arm-visual
http://bit.ly/wai-arm-content
http://bit.ly/wai-arm-front-end
AccessU 2020 Introducing ARRM: A Framework to Fight Accessibility Apathy

26. –AccessU 2020 Introducing ARRM: A Framework to Fight Accessibility Apathy
What do you think?
Can you see how this framework could help your team get clarity
on how to break down accessibility through your own lifecycle?

27. –
Discover the EOWG
Want to get involved?
The EOWG (Education and Outreach
Working Group) has many projects
going on and are always looking for
more volunteers! Wanna help out?
We’d love to welcome you as part of
the team.
Resource
https://www.w3.org/WAI/about/groups/eowg/
AccessU 2020 Introducing ARRM: A Framework to Fight Accessibility Apathy

28. Thank you for your attention!
Want to know more about this project or get
a hold of us? Don’t hesitate to reach out!
AccessU 2020 – Introducing ARRM: A Framework to Fight Accessibility Apathy