accessibility

Wagtail Accessibility Conformance Report

Based on VPAT® 2.4 WCAG 2.1 and Revised Section 508 Edition

Name of Product/Version

Wagtail 5.2

Report Dates and Version

Product Description

A Django content management system focused on flexibility and user experience

Contact Information

Author Information

Notes

Testing based on https://static-wagtail-v5-2.netlify.app/admin/. This report was created based on results of an ATAG 2.0 audit (https://wagtail.org/accessibility/atag-audit/) and WCAG 2.2 audit (https://github.com/wagtail/wagtail/discussions/11180), as well as the public record of accessibility issues identified as of December 2023.

Evaluation Methods

Auditing conducted with the WCAG-EM methodology. Specific testing tools employed are Accessibility Insights (Axe) and Pa11y (Axe).

Manual tests included:

Applicable Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guidelines:

Standard/Guideline Included In Report
Web Content Accessibility Guidelines 2.1 <ul><li>Table 1: Success Criteria, Level A</li><li>Table 2: Success Criteria, Level AA</li><li>Table 3: Success Criteria, Level AAA</li></ul>
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018 <ul><li>Chapter 3: Functional Performance Criteria (FPC)</li></ul>

Terms

The terms used in the Conformance Level information are defined as follows:

WCAG 2.1 Report

Table 1: Success Criteria, Level A

Conformance to the 30 criteria listed below is distributed as follows:

Criteria Conformance Level Remarks and Explanations
1.1.1 Non-text Content <ul><li>Web: Partially Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Partially Supports</li> </ul> <ul><li>Web: Though Wagtail has alt text options for all images by default, and ways for site implementers to adjust to their needs, some of the default options lack a clear way to mark images as decorative.

See ATAG 2.0 audit: https://wagtail.org/accessibility/atag-audit/#b23-assist-authors-with-managing-alternative-content-for-non-text-content</li><li>Electronic Documents: All of the Wagtail editor guide (https://guide.wagtail.org/) and developer documentation (https://docs.wagtail.org/) has been reviewed so none of the images are decorative and all images have appropriate alt text.</li><li>Authoring Tool: In the authoring tool, there are a few scenarios in which images’ alt text is present but not programmatically associated with the image.

See ATAG 2.0 audit: https://wagtail.org/accessibility/atag-audit/#a2-editing-views-are-perceivable</li> </ul>      
  1.2.1 Audio-only and Video-only (Prerecorded) <ul><li>Web: Not Applicable</li><li>Electronic Documents: Not Applicable</li><li>Software: Not Applicable</li><li>Authoring Tool: Not Applicable</li> </ul> <ul><li>Web: There is no built-in audio or video support in Wagtail.</li><li>Electronic Documents: There is no audio or video content in Wagtail’s documentation.</li><li>Authoring Tool: There is no audio or video content in Wagtail’s user interface.</li> </ul>
  1.2.2 Captions (Prerecorded) <ul><li>Web: Not Applicable</li><li>Electronic Documents: Not Applicable</li><li>Software: Not Applicable</li><li>Authoring Tool: Not Applicable</li> </ul> <ul><li>Web: There is no built-in audio or video support in Wagtail.</li><li>Electronic Documents: There is no audio or video content in Wagtail’s documentation.</li><li>Authoring Tool: There is no built-in audio or video support in Wagtail.</li> </ul>
  1.2.3 Audio Description or Media Alternative (Prerecorded) <ul><li>Web: Not Applicable</li><li>Electronic Documents: Not Applicable</li><li>Software: Not Applicable</li><li>Authoring Tool: Not Applicable</li> </ul> <ul><li>Web: There is no built-in audio or video support in Wagtail.</li><li>Electronic Documents: There is no audio or video content in Wagtail’s documentation.</li><li>Authoring Tool: There is no built-in audio or video support in Wagtail.</li> </ul>
  1.3.1 Info and Relationships <ul><li>Web: Partially Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Partially Supports</li> </ul> <ul><li>Web: All content created with Wagtail rich text supports 1.3.1 Info and Relationships, except for the built-in blockquote formatting, which lacks a way to programmatically define the cite attribute or element within.
See ATAG 2.0 audit: https://wagtail.org/accessibility/atag-audit/#a34-for-the-authoring-tool-user-interface-enhance-navigation-and-editing-via-content-structure and https://wagtail.org/accessibility/atag-audit/#b24-assist-authors-with-accessible-templates</li><li>Electronic Documents: All of the Wagtail editor guide (https://guide.wagtail.org/) and developer documentation (https://docs.wagtail.org/) has been reviewed so all content is correctly structured with semantic elements.</li><li>Authoring Tool: There are a few known 1.3.1 issues. See for example https://github.com/wagtail/wagtail/issues/10576, and https://docs.google.com/spreadsheets/d/1l7tnpEyJiC5BWE_JX0XCkknyrjxYA5T2aee5JgPnmi4/edit.</li> </ul>      
  1.3.2 Meaningful Sequence <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Partially Supports</li> </ul> <ul><li>Web: All content authored with Wagtail has a matching visual and DOM order, in all languages.</li><li>Electronic Documents: All of the Wagtail editor guide (https://guide.wagtail.org/) and developer documentation (https://docs.wagtail.org/) has been reviewed so visual order and semantic order always match.</li><li>Authoring Tool: Wagtail has been extensively tested so all content has a visual order matching the semantic order. We are aware of a few issues with layout of admin views for right-to-left languages (https://github.com/wagtail/wagtail/discussions/7793), those issues have ben addressed and the fixes will be released in February 2024 in Wagtail 6.0.</li> </ul>
  1.3.3 Sensory Characteristics <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Partially Supports</li> </ul> <ul><li>Authoring Tool: We are aware of one view in the CMS which relies on sensory characteristics too much: revision comparisons (https://github.com/wagtail/wagtail/issues/10576).</li> </ul>
  1.4.1 Use of Color <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Partially Supports</li> </ul> <ul><li>Authoring Tool: We are aware of one view in the CMS which relies on color too much: revision comparisons (https://github.com/wagtail/wagtail/issues/10576).</li> </ul>
  1.4.2 Audio Control <ul><li>Web: Not Applicable</li><li>Electronic Documents: Not Applicable</li><li>Software: Not Applicable</li><li>Authoring Tool: Not Applicable</li> </ul> <ul><li>Web: There is no built-in audio or video support in Wagtail.</li><li>Electronic Documents: There is no audio or video content in Wagtail documentation.</li><li>Authoring Tool: There is no audio or video content in the Wagtail user interface.</li> </ul>
  2.1.1 Keyboard <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Partially Supports</li> </ul> <ul><li>Web: All content created with built-in Wagtail features is keyboard-accessible.</li><li>Electronic Documents: All of the Wagtail editor guide (https://guide.wagtail.org/) and developer documentation (https://docs.wagtail.org/) has been reviewed for keyboard support.</li><li>Authoring Tool: We are currently aware of a issues with keyboard support:
See ATAG 2.0 audit: https://wagtail.org/accessibility/atag-audit/#a33-for-the-authoring-tool-user-interface-help-authors-avoid-flashing-that-could-cause-seizures</li> </ul>      
  2.2.2 Pause, Stop, Hide <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Supports</li> </ul> <ul><li>Authoring Tool: The only timing is the session time limit / session cookie expiry, configured to 2 weeks by default.
See ATAG 2.0 audit: https://wagtail.org/accessibility/atag-audit/#a322-timing-adjustable</li> </ul>      
  2.3.1 Three Flashes or Below Threshold <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Supports</li> </ul> <ul><li>Electronic Documents: There are no flashing elements in Wagtail documentation.</li><li>Authoring Tool: There are no flashing elements in the Wagtail admin interface.</li> </ul>
  2.4.1 Bypass Blocks <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Supports</li> </ul> <ul><li>Web: Skip links can be created for all Wagtail content.</li><li>Electronic Documents: All pages of the Wagtail editor guide (https://guide.wagtail.org/) and developer documentation (https://docs.wagtail.org/) provide skip links and navigation "table of content" menus.</li><li>Authoring Tool: The Wagtail admin interface provides skip links, direct anchor links to page sections, and a "minimap" component to jump directly to a specific form section.</li> </ul>
  2.4.2 Page Titled <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Supports</li> </ul> <ul><li>Web: By default, Wagtail-managed pages have a title as set in the CMS.</li><li>Electronic Documents: All of the Wagtail editor guide (https://guide.wagtail.org/) and developer documentation (https://docs.wagtail.org/) has been reviewed so every page has a unique title.</li><li>Authoring Tool: All of the CMS interface has been reviewed so every view has a descriptive title.</li> </ul>
  2.4.3 Focus Order <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Supports</li> </ul> <ul><li>Web: All Wagtail-created content uses a matching semantic, visual, and focus order.</li><li>Electronic Documents: All of the Wagtail editor guide (https://guide.wagtail.org/) and developer documentation (https://docs.wagtail.org/) has been reviewed so all content has a matching semantic, visual, and focus order.</li><li>Authoring Tool: The Wagtail admin interface has been extensively reviewed so semantic, visual, and focus order always match.</li> </ul>
  2.4.4 Link Purpose (In Context) <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Supports</li> </ul> <ul><li>Web: Wagtail link content is always user-generated so can be created with enough description. By default, Wagtail link text for pages defaults to the page’s title.</li><li>Electronic Documents: All of the Wagtail editor guide (https://guide.wagtail.org/) and developer documentation (https://docs.wagtail.org/) has been reviewed for content considerations like link text.</li><li>Authoring Tool: All of the admin interface has been reviewed for content considerations like link text.</li> </ul>
  2.5.1 Pointer Gestures <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Supports</li> </ul> <ul> </ul>
  2.5.2 Pointer Cancellation <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Supports</li> </ul> <ul><li>Authoring Tool: The only CMS operation on the down-event is application of rich text formatting options via the toolbar. This is always undo-able.</li> </ul>
  2.5.3 Label in Name <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Partially Supports</li> </ul> <ul><li>Web: All forms created with Wagtail support setting the text of the label element.</li><li>Authoring Tool: All interactive elements within the CMS have programmatically-associated text matching the visible label. There is one exception currently identified: https://github.com/wagtail/wagtail/issues/11372.</li> </ul>
  2.5.4 Motion Actuation <ul><li>Web: Not Applicable</li><li>Electronic Documents: Not Applicable</li><li>Software: Not Applicable</li><li>Authoring Tool: Not Applicable</li> </ul> <ul> </ul>
  3.1.1 Language of Page <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Supports</li> </ul> <ul><li>Web: Page language is managed in the CMS and then reflects on page templates as configured by site implementers.</li><li>Electronic Documents: All of the Wagtail editor guide (https://guide.wagtail.org/) reflects the page’s language across the different versions. Developer documentation is currently english-only.</li><li>Authoring Tool: Page language is semantically defined based on what language the CMS user has configured.</li> </ul>
  3.2.1 On Focus <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Supports</li> </ul> <ul> </ul>
  3.2.2 On Input <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Supports</li> </ul> <ul> </ul>
  3.3.1 Error Identification <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Partially Supports</li> </ul> <ul><li>Web: Forms created with Wagtail use the aria-describedby and aria-invalid attributes to programmatically identify fields with errors, as per how Django 5.0+ operates.</li><li>Electronic Documents: There are no form fields that can have input errors in the editor guide or developer documentation.</li><li>Authoring Tool: Within the CMS, all form fields use visible error messages, aria-describedby, and aria-invalid – except a specific type of field, which does not currently use aria-invalid. This is tracked here: https://github.com/wagtail/wagtail/issues/10300.</li> </ul>
  3.3.2 Labels or Instructions <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Supports</li> </ul> <ul><li>Web: All forms created with Wagtail have mandatory labels for all fields, and optional help text.</li><li>Electronic Documents: There is no content that requires user input in our Editor Guide or developer documentation.</li><li>Authoring Tool: All form fields requiring input in the CMS have labels. Some also have help text for instructions.</li> </ul>
  4.1.1 Parsing <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Supports</li> </ul> <ul><li>Web: To the extent of our knowledge, there are no parsing issues affecting CMS users or website visitors.</li><li>Electronic Documents: To the extent of our knowledge, there are no parsing issues affecting documentation users.</li><li>Authoring Tool: To the extent of our knowledge, there are no parsing issues affecting CMS users or website visitors.</li> </ul>
  4.1.2 Name, Role, Value <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Partially Supports</li> </ul> <ul><li>Authoring Tool: There are a few components in the CMS where we are aware of needed improvements: https://github.com/wagtail/wagtail/issues/5411, https://github.com/wagtail/wagtail/issues/10228, https://github.com/wagtail/wagtail/issues/10576, https://github.com/wagtail/wagtail/issues/5408, https://github.com/wagtail/wagtail/issues/5411</li> </ul>

Table 2: Success Criteria, Level AA

Conformance to the 20 criteria listed below is distributed as follows:

Criteria Conformance Level Remarks and Explanations
1.2.4 Captions (Live) <ul><li>Web: Not Applicable</li><li>Electronic Documents: Not Applicable</li><li>Software: Not Applicable</li><li>Authoring Tool: Not Applicable</li> </ul> <ul> </ul>
1.2.5 Audio Description (Prerecorded) <ul><li>Web: Not Applicable</li><li>Electronic Documents: Not Applicable</li><li>Software: Not Applicable</li><li>Authoring Tool: Not Applicable</li> </ul> <ul> </ul>
1.3.4 Orientation <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Supports</li> </ul> <ul> </ul>
1.3.5 Identify Input Purpose <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Supports</li> </ul> <ul><li>Web: All input fields of Wagtail-generated forms have programmatically-associated labels, and programmatically-associated help text if set.</li><li>Electronic Documents: All input fields in documentation have programmatically-associated labels.</li><li>Authoring Tool: All input fields of admin interface forms have programmatically-associated labels, and occasionally also have help text.</li> </ul>
1.4.3 Contrast (Minimum) <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Partially Supports</li> </ul> <ul><li>Web: Wagtail doesn’t enforce any specific styles in its output that would affect this SC.</li><li>Electronic Documents: All of the Wagtail editor guide (https://guide.wagtail.org/) and developer documentation (https://docs.wagtail.org/) has been reviewed so there are no known contrast issues.</li><li>Authoring Tool: The admin interface’s color theme has been extensively reviewed for color contrast considerations. We’re currently aware of two text contrast issues:

See:

  1. All content entry in the CMS is automatically validated for correctness
  2. For page content and opt-in for other content types, all editing actions are reversible
  3. For page content and opt-in for other content types, all editing actions can go through a multi-step publication workflow with reviews (https://guide.wagtail.org/en-latest/how-to-guides/configure-workflows-for-moderation/).
For legal and financial requirements specifically, Wagtail supports turning on different publication workflows for different pages or sections of a site.</li> </ul>      
  4.1.3 Status Messages <ul><li>Web: Supports</li><li>Electronic Documents: Does Not Support</li><li>Software: Not Applicable</li><li>Authoring Tool: Supports</li> </ul> <ul><li>Web: Wagtail does not mandate the use of status messages in Wagtail-created content, but supports creating them as needed.</li><li>Electronic Documents: The live search in the Wagtail editor guide documentation lacks programmatically-identifiable status messages.</li><li>Authoring Tool: Wagtail’s status messages use the role attribute</li> </ul>

Table 3: Success Criteria, Level AAA

Conformance to the 28 criteria listed below is distributed as follows:

Criteria Conformance Level Remarks and Explanations
1.2.6 Sign Language (Prerecorded) <ul><li>Web: Not Applicable</li><li>Electronic Documents: Not Applicable</li><li>Software: Not Applicable</li><li>Authoring Tool: Not Applicable</li> </ul> <ul> </ul>
1.2.7 Extended Audio Description (Prerecorded) <ul><li>Web: Not Applicable</li><li>Electronic Documents: Not Applicable</li><li>Software: Not Applicable</li><li>Authoring Tool: Not Applicable</li> </ul> <ul> </ul>
1.2.8 Media Alternative (Prerecorded) <ul><li>Web: Not Applicable</li><li>Electronic Documents: Not Applicable</li><li>Software: Not Applicable</li><li>Authoring Tool: Not Applicable</li> </ul> <ul> </ul>
1.2.9 Audio-only (Live) <ul><li>Web: Not Applicable</li><li>Electronic Documents: Not Applicable</li><li>Software: Not Applicable</li><li>Authoring Tool: Not Applicable</li> </ul> <ul> </ul>
1.3.6 Identify Purpose <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Supports</li> </ul> <ul><li>Web: Wagtail only uses semantic HTML elements as part of its web page output.</li> </ul>
1.4.6 Contrast (Enhanced) <ul><li>Web: Supports</li><li>Electronic Documents: Does Not Support</li><li>Software: Does Not Support</li><li>Authoring Tool: Does Not Support</li> </ul> <ul><li>Web: Wagtail doesn’t enforce any specific styles in its output that would affect this SC.</li><li>Electronic Documents: We target lower contrast levels than this SC requires.</li><li>Authoring Tool: We target lower contrast levels than this SC requires. There are simple ways to create custom color themes for the admin interface should this be a must have.</li> </ul>
1.4.7 Low or No Background Audio <ul><li>Web: Not Applicable</li><li>Electronic Documents: Not Applicable</li><li>Software: Not Applicable</li><li>Authoring Tool: Not Applicable</li> </ul> <ul> </ul>
1.4.8 Visual Presentation <ul><li>Web: Supports</li><li>Electronic Documents: Does Not Support</li><li>Software: Not Applicable</li><li>Authoring Tool: Does Not Support</li> </ul> <ul><li>Web: Wagtail doesn’t enforce any specific styles in its output that would affect this SC.</li> </ul>
1.4.9 Images of Text (No Exception) <ul><li>Web: Supports</li><li>Electronic Documents: Partially Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Partially Supports</li> </ul> <ul><li>Electronic Documents: The Wagtail logotype present in the documentation would fail this.</li><li>Authoring Tool: The Wagtail logotype present in the login screen would fail this.</li> </ul>
2.1.3 Keyboard (No Exception) <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Partially Supports</li> </ul> <ul><li>Web: See 2.1.1 Keyboard</li><li>Electronic Documents: See 2.1.1 Keyboard</li><li>Authoring Tool: See 2.1.1 Keyboard</li> </ul>
2.2.3 No Timing <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Supports</li> </ul> <ul> </ul>
2.2.4 Interruptions <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Supports</li> </ul> <ul><li>Web: Wagtail doesn’t enforce any specific styles in its output that would affect this SC.</li><li>Electronic Documents: There are no interruptions in the editor guide or developer documentation.</li><li>Authoring Tool: Though the admin interface occasionally contains server updates or other kinds of system-driven notifications, none of them will interrupt the user’s activities.</li> </ul>
2.2.5 Re-authenticating <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Does Not Support</li> </ul> <ul><li>Web: Wagtail does not enforce any specific authentication behavior on website pages.</li><li>Electronic Documents: There is no authentication in the documentation.</li> </ul>
2.2.6 Timeouts <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Partially Supports</li> </ul> <ul><li>Authoring Tool: The default is 2 weeks of inactivity to lose data. If the timeout is lower, Wagtail is missing a warning on data loss. See https://github.com/wagtail/wagtail/issues/2199.</li> </ul>
2.3.2 Three Flashes <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Supports</li> </ul> <ul> </ul>
2.3.3 Animation from Interactions <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Partially Supports</li> </ul> <ul><li>Web: Wagtail doesn’t enforce any specific styles in its output that would affect this SC.</li><li>Authoring Tool: All of the animation can be disabled with the prefers-reduced-motion media query, but there is no CMS setting.</li> </ul>
2.4.8 Location <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Partially Supports</li> </ul> <ul><li>Authoring Tool: Wagtail uses breadcrumb components across the admin interface but not all of it: https://github.com/wagtail/wagtail/issues/11366</li> </ul>
2.4.9 Link Purpose (Link Only) <ul><li>Web: Supports</li><li>Electronic Documents: Does Not Support</li><li>Software: Not Applicable</li><li>Authoring Tool: Does Not Support</li> </ul> <ul><li>Web: Wagtail doesn’t enforce any specific HTML in its output that would affect this SC.</li><li>Electronic Documents: A number of links don’t have an understandable purpose without context.</li><li>Authoring Tool: A number of links don’t have an understandable purpose without context.</li> </ul>
2.4.10 Section Headings <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Supports</li> </ul> <ul><li>Web: Wagtail doesn’t enforce any specific HTM in its output that would affect this SC.</li><li>Electronic Documents: All pages contain headings.</li><li>Authoring Tool: All pages contain headings where sub-sections are present.</li> </ul>
2.5.5 Target Size <ul><li>Web: Supports</li><li>Electronic Documents: Does Not Support</li><li>Software: Not Applicable</li><li>Authoring Tool: Does Not Support</li> </ul> <ul><li>Web: Wagtail doesn’t enforce any specific CSS in its output that would affect this SC.</li><li>Electronic Documents: There are a number of interactive elements that are smaller than the target.</li><li>Authoring Tool: There are a number of interactive elements that are smaller than the target.</li> </ul>
2.5.6 Concurrent Input Mechanisms <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Supports</li> </ul> <ul> </ul>
3.1.3 Unusual Words <ul><li>Web: Supports</li><li>Electronic Documents: Does Not Support</li><li>Software: Not Applicable</li><li>Authoring Tool: Does Not Support</li> </ul> <ul><li>Web: Wagtail doesn’t enforce any specific HTML in its output that would affect this SC.</li><li>Electronic Documents: A high number of unusual words aren’t defined currently.</li><li>Authoring Tool: Mechanisms to annotate text can be built, but this isn’t built-in functionality.</li> </ul>
3.1.4 Abbreviations <ul><li>Web: Supports</li><li>Electronic Documents: Does Not Support</li><li>Software: Not Applicable</li><li>Authoring Tool: Does Not Support</li> </ul> <ul><li>Web: Wagtail doesn’t enforce any specific HTML in its output that would affect this SC.</li><li>Electronic Documents: A high number of abbreviations aren’t defined currently.</li><li>Authoring Tool: Mechanisms to annotate text can be built, but this isn’t built-in functionality.</li> </ul>
3.1.5 Reading Level <ul><li>Web: Supports</li><li>Electronic Documents: Does Not Support</li><li>Software: Not Applicable</li><li>Authoring Tool: Does Not Support</li> </ul> <ul><li>Web: Wagtail doesn’t enforce any specific HTML in its output that would affect this SC.</li><li>Electronic Documents: A high number of content hasn’t been assessed for reading level.</li><li>Authoring Tool: Mechanisms to assess text can be built, but this isn’t built-in functionality.</li> </ul>
3.1.6 Pronunciation <ul><li>Web: Supports</li><li>Electronic Documents: Does Not Support</li><li>Software: Not Applicable</li><li>Authoring Tool: Does Not Support</li> </ul> <ul><li>Web: Wagtail doesn’t enforce any specific HTML in its output that would affect this SC.</li><li>Electronic Documents: A high number of content hasn’t been assessed for reading level.</li><li>Authoring Tool: Mechanisms to annotate text can be built, but this isn’t built-in functionality.</li> </ul>
3.2.5 Change on Request <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Supports</li> </ul> <ul><li>Web: Wagtail doesn’t enforce any specific HTML in its output that would affect this SC.</li> </ul>
3.3.5 Help <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Supports</li> </ul> <ul><li>Web: Wagtail’s form builder supports providing HTML for all form fields.</li><li>Authoring Tool: All forms in Wagtail provide help text.</li> </ul>
3.3.6 Error Prevention (All) <ul><li>Web: Supports</li><li>Electronic Documents: Supports</li><li>Software: Not Applicable</li><li>Authoring Tool: Does Not Support</li> </ul> <ul><li>Authoring Tool: Though a large number of authoring actions are reversible, not all are. See https://wagtail.org/accessibility/atag-audit/#a411-content-changes-reversible-minimum</li> </ul>

Revised Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Conformance to the 9 criteria listed below is distributed as follows:

Criteria Conformance Level Remarks and Explanations
302.1 Without Vision <ul><li>Partially Supports</li> </ul> <ul><li>Wagtail actively supports all popular screen readers, though there are a small number of known issues.</li> </ul>
302.2 With Limited Vision <ul><li>Partially Supports</li> </ul> <ul><li>Wagtail supports Windows High Contrast Mode / Contrast themes, though there are a few known issues.</li> </ul>
302.3 Without Perception of Color <ul><li>Partially Supports</li> </ul> <ul><li>None of the Wagtail admin interface relies on perception of color except for revision comparisons. See https://github.com/wagtail/wagtail/issues/10576.</li> </ul>
302.4 Without Hearing <ul><li>Not Applicable</li> </ul> <ul><li>With only built-in functionality, there is no audio element to the CMS admin interface, documentation, or website content.</li> </ul>
302.5 With Limited Hearing <ul><li>Not Applicable</li> </ul> <ul><li>With only built-in functionality, there is no audio element to the CMS admin interface, documentation, or website content.</li> </ul>
302.6 Without Speech <ul><li>Not Applicable</li> </ul> <ul><li>With only built-in functionality, there is no audio element to the CMS admin interface, documentation, or website content.</li> </ul>
302.7 With Limited Manipulation <ul><li>Not Evaluated</li> </ul> <ul> </ul>
302.8 With Limited Reach and Strength <ul><li>Not Evaluated</li> </ul> <ul> </ul>
302.9 With Limited Language, Cognitive, and Learning Abilities <ul><li>Not Evaluated</li> </ul> <ul> </ul>

Repository

https://github.com/wagtail/accessibility

Feedback

https://github.com/wagtail/accessibility

OpenACR is a format maintained by the GSA. The content is the responsibility of the author.

This content is licensed under a Creative Commons Zero v1.0 Universal.