Content Author Responsibilities in Accessibility Roles and Responsibilities Mapping (ARRM)

Role summary

Content Creation is often used in marketing, but can also be a task assigned to a role within a product team. Content creation involves defining a content strategy, the writing or creation of the content or media for a product. The person who authors the content is responsible for making sure that content is accessible to people with disabilities.

Key deliverable examples:
Body copy, managed content, scripts, taxonomies, written guidelines, media files, including PDF, audio, and video
Tasks include:
Content authoring, Media and documentation creation, and Content strategies definition
Example job titles for this role:
Content Strategist, Content Creator, Content Designer, Content Author, Digital Copywriter, UX Writer, Content Producer, Technical Writer, Information Developer, and Content Developer

Tasks to get started

Below is a list of tasks for Content Authors to get started making your work more accessible to disabled people. If these tasks aren’t met, your content can create barriers to users with disabilities.

Important notes:

You can also get the full list of Tasks Involved in Accessibility as a web page with other roles, or download the CSV file.

ID WCAG SC Task
IMG-001 1.1.1 Non-text Content (A) Informative alternate text is provided for images (i.e. not "spacer" or image file name).
IMG-002 1.1.1 Non-text Content (A) Informative images are described with a clear and meaningful text equivalent (alt attribute or other equivalent means).
IMG-006 1.1.1 Non-text Content (A) Alt text used for images of text include all relevant text found in the image.
IMG-008 1.1.1 Non-text Content (A) The purpose or function of complex images is accurately described in text.
IMG-010 1.1.1 Non-text Content (A) The full explanation of complex images is accurately described in text.
IMG-013 1.1.1 Non-text Content (A) Images primarily conveying function use alternative text to describe their purpose, rather than what they look like.
IMG-014 1.1.1 Non-text Content (A) Text alternatives of static and linked images do not replicate any information that is already being conveyed by screen reader technology.
IMG-017 1.1.1 Non-text Content (A) Images which do not convey information are defined as decorative.
SEM-012 1.3.1 Info and Relationships (A) Headings follow a hierarchical sequence without skipping any levels.
SEM-019 2.4.2 Page Titled (A) Page title text matches the level 1 heading text.
SEM-020 2.4.2 Page Titled (A) Pages are described using unique and descriptive page title values.
SEM-022 2.4.6 Headings and Labels (AA) Heading text meaningfully describes the content's topic or purpose.
SEM-023 2.4.6 Headings and Labels (AA) The main heading of the page describes the content of the page.
INP-021 2.5.3 Label in Name (A) Text or images of text that is usually included in a user interface control is part of its accessible name.
FRM-006 1.3.1 Info and Relationships (A) Common group label text is informative, meaningful and provides context for the grouping.
FRM-016 2.4.6 Headings and Labels (AA) The purpose of the form control is clearly described in text.
FRM-030 3.3.2 Labels or Instructions (A) Clear text-based instructions are provided on how to use the form controls.
FRM-033 3.3.3 Error Suggestion (AA) Error messages returned provide clear instructions on how to fix them.
NAV-002 1.3.3 Sensory Characteristics (A) Instructions are conveyed through more than shape, size, position, or sound alone.
NAV-018 2.4.4 Link Purpose (In Context) (A) Link text and alternate text for images, when used as links, describe the destination or purpose of the link.
NAV-022 2.4.9 Link Purpose (Link Only) (AAA) The purpose of each link can be identified in its immediate context, or from the link text alone.
NAV-023 2.4.10 Section Headings (AAA) Content is logically organized using section headings.
NAV-028 3.2.4 Consistent Identification (AA) The accessible name of user interface components used across the site or application are defined consistently.
TAB-015 1.3.1 Info and Relationships (A) A meaningful description of the structure of data tables is provided.
ANM-001 1.2.1 Audio-only and Video-only (Prerecorded) (A) Text transcripts are provided for prerecorded audio-only files.
ANM-002 1.2.1 Audio-only and Video-only (Prerecorded) (A) Text transcripts are provided for prerecorded video-only files.
ANM-007 1.2.2 Captions (Prerecorded) (A) Synchronized captions are provided for all prerecorded video content.
ANM-008 1.2.2 Captions (Prerecorded) (A) Captions do not skip dialogues or important sounds.
ANM-010 1.2.3 Audio Description or Media Alternative (Prerecorded) (A) Text transcripts report all significant information from the audio track.
ANM-011 1.2.3 Audio Description or Media Alternative (Prerecorded) (A) Text transcripts or audio descriptions report all significant information from the visual track.
ANM-012 1.2.4 Captions (Live) (AA) Synchronized captions are provided for all live video content.
ANM-013 1.2.4 Captions (Live) (AA) Captions for live audio content are generated using real-time text transcription services.
ANM-014 1.2.5 Audio Description (Prerecorded) (AA) Prerecorded videos have audio descriptions that captures all significant information from the visual track.
ANM-017 1.2.6 Sign Language (Prerecorded) (AAA) Sign language interpretation is provided for all prerecorded audio content in synchronized media.
ANM-018 1.2.7 Extended Audio Description (Prerecorded) (AAA) Extended audio description is provided for all prerecorded synchronized video content when pauses in foreground audio are insufficient to allow audio descriptions to convey the sense of the video.
ANM-019 1.2.8 Media Alternative (Prerecorded) (AAA) Text alternatives are provided for all prerecorded audio and video files.
ANM-021 1.2.9 Audio-only (Live) (AAA) Live transcripts are provided for all audio content happening in real-time.
ANM-028 1.4.7 Low or No Background Audio (AAA) Prerecorded audio-only speeches contain no background sound, or if they do, must be at least 20 decibels lower than the foreground speech content.
SCT-007 1.3.1 Info and Relationships (A) The headings used in a page provide a logical outline for the document.
SCT-019 3.1.1 Language of Page (A) The language definition of the document uses the correct value for language and locale.
SCT-020 3.1.2 Language of Parts (AA) Content passages that differ from the default are identified with the correct value for language and locale.
SCT-024 3.1.5 Reading Level (AAA) Content is written in plain language using everyday words, to help users with different literacy levels and access needs.

Case study: How to use the tasks

A good way to get familiar with the tasks is to do a short case study. Think about how you might tackle the task in your role.

Then, think of how meeting this task impacts an end user.

Task:

IMG-002: Informative images are described with a clear and meaningful text equivalent (alt attribute or other equivalent means).

Primary Role: Content Author

“As the primary owner of this task, I will ensure that any images that contain information or represent an action or a symbol for the user, and are not just decorative - have a descriptive and meaningful text alternative that will be announced by screen reader software.”

Secondary Role: None

There is no secondary owner of this task.

Contributor Role: None

There is no additional contributor for this task.

End user persona: Lakshmi, a senior accountant who is blind

Lakshmi is blind and uses a screen reader (speech-to-text software) and keyboard to navigate web pages. She uses websites daily for research and financial transactions. This design task ensures she isn’t confused by an unexpected behaviour, i.e., when her keyboard focus lands on a button for the first time and content is announced automatically or the button automatically opens another page.

The intent of the task is to ensure that functionality is predictable as visitors navigate their way through a document.

This task helps people with visual disabilities, cognitive limitations, and motor impairments by reducing the chance that a change of context will occur unexpectedly.

Read Lakshmi’s full story and learn about other design tasks that benefit users like her.

Additional resources

Back to Top