AEM Sites Playbook, Chapter 16: Accessibility for authors and visitors
Can authors and visitors complete the required tasks accessibly?
November 10, 2026
Include everyone who uses the system
Use this chapter when defining experience quality, testing components or responding to an accessibility finding. Assess both the delivered site and the Author tasks required to maintain it. A customer-facing check does not cover an editor who cannot operate a dialog with a keyboard or assistive technology.
The business/platform owner identifies the required standard, scope, supported tasks and responsible specialists. Designers, developers and authors divide the work explicitly: component structure and interaction, usable field/validation design, and meaningful content. Adobe's accessible-content guidance covers content practices; it does not certify a particular customization or complete implementation.
The Author UI accessibility question received documentation links and an acknowledgement, not evidence that all screens met the customer's requirements. Ask for the actual affected task, environment and observable barrier. Test the remedy against that task.
Review structure and content together
Check meaningful headings and reading order, descriptive links, labels/instructions, errors, text alternatives, decorative images, media alternatives, contrast and responsive behavior. Evaluate the final component with real content rather than an empty design-system example. A valid field may still produce confusing or inaccessible output.
Choose text alternatives for the image's purpose in the page. The Sites-versus-Assets alt-text discussion compares centralized metadata and local overrides. Define who owns each and inspect the rendered alternative. A central description can be inappropriate in a different context; decorative use needs different handling from an informative product image.
For a hypothetical campaign page, review the hero image, heading hierarchy, form/CTA labels and any media. Then review the author's task of supplying those values. If the implementation makes the correct value difficult to enter or preserve, fix the authoring design as well as the page.
Test complete interactions
Run representative visitor and author tasks using the input methods and assistive technologies required by the project. Include entering a component, reaching its controls, changing values, handling validation, saving and returning to the surrounding task. Record focus movement, visible indication, reading/interaction order and the ability to recover from errors.
In the 6.5 RTE keyboard discussion, the author reported success reaching the fullscreen toolbar but still could not complete inline formatting navigation. That is partial success. Keep the unresolved task visible rather than close it because one mode works. The nested-dialog upgrade case adds focus behavior to the regression set; its private-method workaround is not a universal supported remedy.
Use automated checks for the issues they can detect, then investigate findings and complete the necessary manual tests. Record the tested browser/technology combinations, content and component versions. A screenshot or a clean automated report cannot by itself demonstrate a usable interaction.
Convert a finding into a task the team can reproduce
Community discussions describe different accessibility evidence: requests for Author UI guidance, partial keyboard interaction, and responsibility for contextual image alternatives. None establishes that every screen or custom component is accessible. Judge the complete task against the organization's requirements and retain unresolved barriers.
Describe the user task, input/assistive technology, expected action, observed barrier and affected environment. Separate an inability to complete a task from an inconvenience, using the organization's criteria. Do not invent an affected user's needs or treat a generic standards link as a completed assessment.
Scroll horizontally if needed.
| Finding | Likely contributors | Evidence for closure |
|---|---|---|
| A control cannot be reached or operated | Component/editor engineering and accessibility specialist | Complete task with the required input method |
| An image alternative is unsuitable | Author, asset and component owners | Correct contextual output, including decorative behavior where relevant |
| An error is not understandable | Content/design/engineering owners | User can identify the problem and recover |
| Focus disappears after a dialog change | Component/editor engineering | Predictable completion and return to the surrounding task |
| Layout blocks use at a required size | Design/component owners | Representative content remains operable under the required conditions |
| Custom markup changes behavior | Engineering and accessibility owners | Applicable semantic/interaction checks on the rendered result |
Worked scenario of an inclusive campaign task
This hypothetical project must support a regional author completing a campaign page using a keyboard, and visitors navigating its content and action. The organization has defined its required accessibility scope with the responsible specialists. The team uses a real-sized content fixture, not an empty component.
The author must open a text component, edit formatting, add a meaningful link, recover from validation and return to the page. Visitors must understand the heading structure, image meaning and action, then complete the intended next step. The team records input/technology combinations and actual supported versions.
Scroll horizontally if needed.
| Task segment | Required observation | Owner |
|---|---|---|
| Enter and operate the text editor | Controls can be found and used through the required input method | Editor/component engineering |
| Handle invalid content | Error/instruction is available and recovery is possible | Design/content/engineering |
| Save and return | Focus/task context remains usable | Component engineering |
| Understand the page image | Appropriate alternative or decorative treatment is rendered | Author/media/component owners |
| Follow the primary action | Clear purpose and operable control | Design/content/engineering |
Suppose the initial test passes fullscreen editing but fails the inline path authors ordinarily use. The team keeps that task open, just as partial success remains visible in the RTE discussion. It does not label the complete authoring experience passed because an alternate mode can perform one step.
The component owner then implements a supported correction on the target configuration. The accessibility reviewer repeats the complete path, including validation and return to the page. Hypothetically, all defined segments now pass on the recorded combinations, and the visitor checks pass for the fixture. The owner can accept that tested scope while retaining other content/component combinations as separate review work.
Distinguish temporary assistance from a repaired experience
Scroll horizontally if needed.
| Situation | Record it as | Next decision |
|---|---|---|
| Another person completes an inaccessible step | Operational assistance | Owner decides urgency and supported remediation |
| An alternative path completes only part of the task | Partial workaround | Complete-task testing remains open |
| A supported correction passes the required task | Remediated within tested scope | Add regression evidence and review affected variants |
| Automated findings are absent | One check result | Complete the required manual/assistive-technology assessment |
| One content fixture passes | Evidence for that fixture | Select representative variations before expanding acceptance |
Use Adobe's accessible-content guidance with the required standard and scope selected for the organization. Keep legal/conformance decisions with the responsible specialists. A Core Component choice, customization or tool report alone does not certify the whole site.
Make content and interaction quality durable
Give authors practical guidance for headings, link meaning, alternatives, labels and media. Demonstrate those choices using the actual component, including its fallback rules. Give engineers fixtures that include long localized content, missing optional values and errors.
Retest affected tasks after editor/component/runtime changes and keep the remediation owner visible. The acceptance record should state the task, content, technology, versions, findings and results, so the next release can verify the same capability instead of restarting an unstructured audit.
Close findings with a retest
Complete W16 with task, population, required criterion, barrier, owner, remedy and retest evidence. Assign severity according to the task's impact and the organization's criteria. Content owners can correct wording or alternatives; engineers/designers must own structural and interaction changes. Track temporary assistance separately from a repaired product task. Before accepting an upgrade, repeat the affected author and visitor journeys so the remedy survives the next release.
W16 Accessibility task matrix
Use with chapter 16. Record full task completion, including any remaining barrier.
Scroll horizontally if needed.
| Record | Entry |
|---|---|
| Author/visitor task, population and required standard/criterion | [enter] |
| Content/component/environment and technology/input combination | [enter] |
| Expected interaction, observed barrier and task impact | [enter] |
| Automated finding and relevant manual/assistive-technology evidence | [enter] |
| Content/design/engineering remedy, owner and priority | [enter] |
| Retest, remaining condition and regression check | [enter] |
