International Edition
(Based on VPAT® Version 2.5)
Name of Product/Version:
Accessibility Checker, version 1.52
Report Date:
November 8, 2026
Product Description:
Equalize Digital Accessibility Checker helps you find and fix accessibility issues in WordPress. Scan posts and pages as you edit, review WCAG-based issues inside WordPress, apply automated fixes for common barriers, and generate an accessibility statement to support your compliance efforts.
This report covers the free version of Accessibility Checker.
Contact Information:
Anyone may submit accessibility questions via email to accessibilityhelp@equalizedigital.com. You can also submit an accessibility report directly on our GitHub repo for Accessibility Checker.
Support for Accessibility Checker free is provided via the WordPress.org support forum.
Notes:
The information contained in this report applies to the product itself and some documentation/support services. Product help and support documentation is located in documentation pages on our website. For information about the accessibility of our website or documentation, view our website accessibility statement.
The scope of this report is limited to the accessibility of the listed product only and does not cover accessibility in the WordPress content management system as a whole or any additional add-on products. Visit our accessibility statement page for links to Accessibility Conformance Reports for other products.
Evaluation Methods Used:
Equalize Digital, Inc. completed the accessibility assessment using industry-standard automated testing tools and manual testing techniques. Certified accessibility professionals completed manual testing using leading assistive technology, such as screen readers (NVDA, VoiceOver, and JAWS), screen magnifiers, and keyboard navigation. Blind screen reader users tested some components.
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.0 | Level A: Yes Level AA: Yes Level AAA: Yes |
| Web Content Accessibility Guidelines 2.1 | Level A: Yes Level AA: Yes Level AAA: Yes |
| Web Content Accessibility Guidelines 2.2 | Level A: Yes Level AA: Yes Level AAA: Yes |
| Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018 | Yes |
| EN 301 549 Accessibility requirements for ICT products and services – V3.1.1 (2019-11) AND EN 301 549 Accessibility requirements for ICT products and services – V3.2.1 (2021-03) | Yes |
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
- Not Evaluated: The product has not been evaluated against the criterion. This can only be used in WCAG Level AAA criteria.
WCAG 2.x Report
Tables 1 and 2 also document conformance with:
- EN 301 549: Chapter 9 – Web, Sections 10.1-10.4 of Chapter 10 – Non-Web documents, and Sections 11.1-11.4 and 11.8.2 of Chapter 11 – Non-Web Software (open and closed functionality), and Sections 12.1.2 and 12.2.4 of Chapter 12 – Documentation
- Revised Section 508: Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 – 602.3 Electronic Support Documentation .
Note: When reporting on conformance with the WCAG 2.x Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.
Table 1: Success Criteria, Level A
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
1.1.1 Non-text Content (Level A) Also applies to:
|
Supports |
The product provides sufficient text alternatives for all instances of non-text content that are functional or provide meaning. |
1.2.1 Audio-only and Video-only (Prerecorded) (Level A) Also applies to:
|
Not Applicable |
There is no prerecorded audio or video in the product. |
1.2.2 Captions (Prerecorded) (Level A) Also applies to:
|
Not Applicable |
There is no prerecorded video in the product. |
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) Also applies to:
|
Not Applicable |
There is no prerecorded video in the product. |
1.3.1 Info and Relationships (Level A) Also applies to:
|
Partially Supports |
The product generally conveys information, structure, and relationships programmatically. However, the following issues were identified: In the block editor, the Accessibility Checker sidebar uses the wordpress/components <Panel> components. This WordPress core component is hard coded to use only H2 elements without a configuration, which causes the incorrect heading nesting. The panel title and accordion headers have the same heading level, resulting in a heading structure that does not accurately reflect the organization of the content (accordions should be H3s). In a future version of the product, we may be able to use a different WordPress component that allows for correct heading nesting. This issue can be tracked on GitHub Issue #1764. |
1.3.2 Meaningful Sequence (Level A) Also applies to:
|
Supports |
The product presents content in a reading order that correctly communicates its meaning, and the correct reading sequence can be programmatically determined. |
1.3.3 Sensory Characteristics (Level A) Also applies to:
|
Supports |
There are no instructions provided for understanding and operating the product that rely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound. |
1.4.1 Use of Color (Level A) Also applies to:
|
Supports |
Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. Where color is used as an indicator, a distinguishable icon, or visible number and text is also present. |
1.4.2 Audio Control (Level A) Also applies to:
|
Not Applicable |
There is no audio that plays automatically. |
2.1.1 Keyboard (Level A) Also applies to:
|
Supports |
All functionality of the product is operable through a keyboard interface without requiring specific timings for individual keystrokes. |
2.1.2 No Keyboard Trap (Level A) Also applies to:
|
Supports |
There are no keyboard traps present in the product. |
2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply |
Not Applicable |
There are no keyboard shortcuts in the product. |
2.2.1 Timing Adjustable (Level A) Also applies to:
|
Not Applicable |
No time limits are present in the product. |
2.2.2 Pause, Stop, Hide (Level A) Also applies to:
|
Not Applicable |
There is no moving, blinking, scrolling, or auto-updating content in the product. |
2.3.1 Three Flashes or Below Threshold (Level A) Also applies to:
|
Supports |
The product does not contain flashing content or anything that rapidly blinks. |
2.4.1 Bypass Blocks (Level A) Also applies to:
|
Supports |
Admin pages created by the product are coded in a way such that the WordPress core skip link will function. The product does not create front-end pages for website visitors. |
2.4.2 Page Titled (Level A) Also applies to:
|
Supports |
Admin pages created by the product are titled. The product does not create front-end pages for website visitors. |
2.4.3 Focus Order (Level A) Also applies to:
|
Supports |
The product maintains a logical and meaningful focus order that preserves the meaning and operability of the content when users navigate using a keyboard. |
2.4.4 Link Purpose (In Context) (Level A) Also applies to:
|
Supports |
The product provides links with descriptive accessible names that clearly communicate their purpose, either through the link text itself or through its programmatically determined context, allowing users of assistive technologies to understand the destination or function of each link. |
2.5.1 Pointer Gestures (Level A 2.1 and 2.2) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply |
Not Applicable |
There is no functionality that uses multipoint or path-based gestures for operation in the product. |
2.5.2 Pointer Cancellation (Level A 2.1 and 2.2) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply |
Supports |
All pointer-triggered events in the product happen on the up-event, and it is possible for users to cancel interactions mid-click. |
2.5.3 Label in Name (Level A 2.1 and 2.2) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply |
Supports |
The product ensures that the accessible names of user interface components containing visible text labels include the corresponding visible text, allowing speech input users to activate controls by their displayed labels and ensuring consistency for assistive technology users. |
2.5.4 Motion Actuation (Level A 2.1 and 2.2) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply |
Not Applicable |
There is no functionality in the product that is operated by device motion or user motion. |
3.1.1 Language of Page (Level A) Also applies to:
|
Supports |
Admin pages created by the product declare the human language of the page. The product does not create front-end pages for website visitors. |
3.2.1 On Focus (Level A) Also applies to:
|
Supports |
There are no components in the product that initiate a change of context when focused with a keyboard. |
3.2.2 On Input (Level A) Also applies to:
|
Supports |
The product does not initiate unexpected changes of context when users change the settings of user interface components. Any changes of context are communicated to users in advance, allowing them to interact with form controls predictably. |
3.2.6 Consistent Help (Level A 2.2 only) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Not Applicable |
The product’s content does not include help mechanisms or support features for front-end user navigation or understanding. |
3.3.1 Error Identification (Level A) Also applies to:
|
Supports |
If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. |
3.3.2 Labels or Instructions (Level A) Also applies to:
|
Supports |
The product provides clear labels and instructions for user input fields, allowing users to understand the purpose of each field and the information required to complete forms successfully. |
3.3.7 Redundant Entry (Level A 2.2 only) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Supports |
No instances were identified where users were required to re-enter information previously provided during the same process. Where applicable, information was retained or available, meeting the requirements of this success criterion. |
4.1.1 Parsing (Level A) Applies to: WCAG 2.0 and 2.1 – Always answer ‘Supports’ WCAG 2.2 (obsolete and removed) – Does not apply
|
Not Evaluated |
For WCAG 2.0, 2.1, EN 301 549, and Revised 508 Standards, the September 2023 errata update indicates this criterion is always supported. See the WCAG 2.0 Editorial Errata and the WCAG 2.1 Editorial Errata. |
4.1.2 Name, Role, Value (Level A) Also applies to:
|
Supports |
The product provides programmatically determinable names, roles, values, and states for user interface components. |
Table 2: Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
1.2.4 Captions (Live) (Level AA) Also applies to:
|
Not Applicable |
There are no live videos in the product. |
1.2.5 Audio Description (Prerecorded) (Level AA) Also applies to:
|
Not Applicable |
There is no prerecorded video in the product. |
1.3.4 Orientation (Level AA 2.1 and 2.2) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply |
Supports |
The product supports the use of both portrait and landscape orientations without restricting functionality or content display, except where a specific display orientation is essential. |
1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply |
Supports |
Input fields that collect information about the user use appropriate autocomplete attributes to programmatically identify their purpose, allowing browsers and assistive technologies to provide personalized input assistance. |
1.4.3 Contrast (Minimum) (Level AA) Also applies to:
|
Supports |
Text and interactive elements maintain sufficient color contrast against adjacent backgrounds. |
1.4.4 Resize text (Level AA) Also applies to:
|
Supports |
Content supports text resizing and browser zoom up to 200% without loss of functionality. |
1.4.5 Images of Text (Level AA) Also applies to:
|
Supports |
There are no images of text in the product. |
1.4.10 Reflow (Level AA 2.1 and 2.2) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply |
Partially Supports |
Most content fully reflows at 400% browser zoom or on small viewports. There is one exception: The "Want to do more with Accessibility Checker? Unlock Pro Features" section in the WordPress admin footer are not visible or reachable at 400% browser zoom because the footer has been intentionally hidden on mobile by WordPress core. This issue has been reported to WordPress core and will be fixed in WordPress 7.2. |
1.4.11 Non-text Contrast (Level AA 2.1 and 2.2) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply |
Supports |
The product provides sufficient non-text contrast for interactive components and visual indicators. In some themes, the default focus highlight color may not provide sufficient contrast against the background. When this occurs, site administrators can customize the focus indicator color using CSS to meet the required contrast ratio. See documentation on how to change the highlighter focus color. |
1.4.12 Text Spacing (Level AA 2.1 and 2.2) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply |
Supports |
Text content and functionality remain available when text spacing styles are adjusted in accordance with WCAG requirements, without loss of content or functionality. |
1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply |
Not Applicable |
There is no content displayed on hover or focus in the product. |
2.4.5 Multiple Ways (Level AA) Also applies to:
|
Not Applicable |
This criterion does not apply to the product. |
2.4.6 Headings and Labels (Level AA) Also applies to:
|
Supports |
Pages created by the product provide clear and descriptive headings and labels that accurately identify the purpose of sections, controls, and form fields. These headings and labels help users, including those using assistive technologies, understand and navigate the content effectively. |
2.4.7 Focus Visible (Level AA) Also applies to:
|
Supports |
There is a visible focus indicator on all focusable elements. |
2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Supports |
When a user interface component receives keyboard focus, it remains fully visible and is not obstructed by author-created content. |
2.5.7 Dragging Movements (Level AA 2.2 only) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Supports |
The product does not include content that rely on dragging movements for functionality. |
2.5.8 Target Size (Minimum) (Level AA 2.2 only) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Supports |
Interactive controls provide sufficient target size and spacing to support accurate selection and interaction across input methods. |
3.1.2 Language of Parts (Level AA) Also applies to:
|
Not Applicable |
The product's content only includes the default language, with no additional languages. |
3.2.3 Consistent Navigation (Level AA) Also applies to:
|
Supports |
The product provides consistent navigation mechanisms across pages and views, helping users predictably locate and access functionality throughout the experience. |
3.2.4 Consistent Identification (Level AA) Also applies to:
|
Supports |
Components that have the same functionality are identified consistently. |
3.3.3 Error Suggestion (Level AA) Also applies to:
|
Supports |
The product provides clear error identification and, where user input errors are detected, appropriate suggestions are provided to help users understand and correct the issue. |
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) Also applies to:
|
Not Applicable |
The product does not include legal commitments, financial transactions, or user-submitted data workflows requiring reversible, reviewable, or confirmable submissions under this criterion. |
3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Supports |
The product does not rely on cognitive function tests for authentication and supports authentication methods that can be completed without requiring users to memorize, transcribe, or solve complex cognitive tasks. |
4.1.3 Status Messages (Level AA 2.1 and 2.2) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply |
Partially Supports |
The product generally provides status messages to communicate the results of user actions and updates. However, a few status messages are not automatically announced by assistive technologies. The following issues were identified:
|
Table 3: Success Criteria, Level AAA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
1.2.6 Sign Language (Prerecorded) (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Not Applicable |
There is no prerecorded video in the product. |
1.2.7 Extended Audio Description (Prerecorded) (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Not Applicable |
There is no prerecorded video in the product. |
1.2.8 Media Alternative (Prerecorded) (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Not Applicable |
There is no prerecorded video in the product. |
1.2.9 Audio-only (Live) (Level AAA) EN 301 549 Criteria– Does not apply Revised Section 508 – Does not apply |
Not Applicable |
There is no live audio in the product. |
1.3.6 Identify Purpose (Level AAA 2.1 and 2.2) EN 301 549 Criteria– Does not apply Revised Section 508 – Does not apply |
Supports |
The product uses appropriate semantic structure and programmatic identification to help assistive technologies determine the purpose of common user interface components and input fields, where supported by current technologies. |
1.4.6 Contrast (Enhanced) (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Supports |
All text in the product has a contrast ratio of at least 7:1 with the background. |
1.4.7 Low or No Background Audio (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Not Applicable |
There is no prerecorded video or audio in the product. |
1.4.8 Visual Presentation (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Supports |
The product supports user customization of visual presentation through standard browser and operating system settings, including text spacing, resizing, and reflow behaviors, without loss of content or functionality. |
1.4.9 Images of Text (No Exception) (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Supports |
There are no images of text in the product. |
2.1.3 Keyboard (No Exception) (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Supports |
All functionality of the product is operable through a keyboard interface without requiring specific timings for individual keystrokes. |
2.2.3 No Timing (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Supports |
Timing is not an essential part of the event or activity presented by the product. |
2.2.4 Interruptions (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Supports |
There are no auto-updating content or other interruptions in the product. |
2.2.5 Re-authenticating (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Not Applicable |
The product does not require users to re-authenticate during a session. Therefore, this criterion is not applicable. |
2.2.6 Timeouts (Level AAA 2.1 and 2.2) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Not Applicable |
The product does not contain or trigger timeouts which could result in a loss of data. |
2.3.2 Three Flashes (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Not Applicable |
The product does not contain flashing content or anything that flashes more than three times per second. |
2.3.3 Animation from Interactions (Level AAA 2.1 and 2.2) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Not Applicable |
The product does not contain animations from interactions. |
2.4.8 Location (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Supports |
Admin pages created by the product identify the user’s location within the WordPress admin area through descriptive page headings and current-page indicators in the navigation menu. |
2.4.9 Link Purpose (Link Only) (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Supports |
All links in the product have meaningful names that describe where the links go. |
2.4.10 Section Headings (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Partially Supports |
The product uses headings to organize content into sections. However, in the block editor, the Accessibility Checker sidebar’s title and accordion headings all use H2 elements, rather than nesting the accordion headings as H3s beneath the sidebar title. This limits how accurately the heading structure communicates the organization of the content. The heading levels are defined by the WordPress core wordpress/components Panel components and cannot currently be configured. A future update may use an alternative component that supports appropriate heading nesting. This issue is tracked in GitHub Issue #1764. |
2.4.12 Focus Not Obscured (Enhanced) (Level AAA 2.2 only) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Supports |
When a user interface component receives keyboard focus, it remains fully visible and is not obstructed by author-created content. |
2.4.13 Focus Appearance (Level AAA 2.2 only) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Supports |
Visible focus indicators are consistently presented and provide sufficient size and contrast to help users identify the currently focused interface component during keyboard navigation. |
2.5.5 Target Size (Level AAA 2.1 and 2.2) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Partially Supports |
Some targets in the product and created by the product are AAA conformant and have a minimum height and width of 44px. Some targets in the block editor, which have sizing controlled by WordPress core, and some targets in the frontend highlighter are not AAA conformant. Examples include:
Site administrators can add custom CSS to enlarge these items if they would like them to be AAA conformant. |
2.5.6 Concurrent Input Mechanisms (Level AAA 2.1 and 2.2) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Not Applicable |
The product content does not restrict the use of available input modalities on a platform, unless these restrictions are needed to ensure content security or to adhere to user preferences or settings. |
3.1.3 Unusual Words (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Partially Supports |
The product explains each issue with a description and a link to more detailed documentation. However, the product uses technical terms, such as landmark, heading level, ARIA, and WCAG success criterion names, without a mechanism to identify their definitions. |
3.1.4 Abbreviations (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Does Not Support |
The product uses abbreviations, such as WCAG, CSS, and HTML, in the Issues Explorer and the issue modal. The expanded forms of these abbreviations are not provided, and the abbr element is not used. |
3.1.5 Reading Level (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Partially Supports |
The summary of each issue is generally written at a lower-secondary reading level. However, the “Why It Matters” and “How to Fix” explanations for most issues require a higher reading level because they include technical terms. Each issue links to more detailed documentation. |
3.1.6 Pronunciation (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Not Applicable |
The product does not include words whose meaning is ambiguous in context without knowing the pronunciation. |
3.2.5 Change on Request (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Supports |
Changes of context in the product are initiated only by user request. |
3.3.5 Help (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Not Applicable |
The content does not require context-sensitive help, and the labels provided are sufficient to describe all functionality, making additional assistance unnecessary. |
3.3.6 Error Prevention (All) (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Supports |
User-entered data is checked for input errors, and the user is given the opportunity to correct them. |
3.3.9 Accessible Authentication (Enhanced) (Level AAA 2.2 only) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Not Applicable |
The product does not create login forms or manage authentication. |
Revised Section 508 Report
Chapter 3: Functional Performance Criteria (FPC)
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
302.1 Without Vision |
Partially Supports |
The product supports operation without vision through screen reader compatibility, keyboard access, text alternatives, and logical reading and focus order. However, the block editor sidebar’s heading hierarchy does not accurately convey the organization of its sections. Certain validation messages and updates are not automatically announced to screen reader users, including the email opt-in validation error and refreshed accessibility analysis results. In the classic editor metabox, dismissing an issue does not provide confirmation of the completed action. See WCAG 1.3.1 Info and Relationships and 4.1.3 Status Messages for details. |
302.2 With Limited Vision |
Partially Supports |
The product supports text resizing and browser zoom to 200%, provides sufficient text contrast, and generally reflows at 400% zoom. However, the “Want to do more with Accessibility Checker? Unlock Pro Features” section in the WordPress admin footer is unavailable at 400% zoom because WordPress core hides the footer at smaller viewport widths. See WCAG 1.4.10 Reflow for details. |
302.3 Without Perception of Color |
Supports |
The product does not rely on color alone to communicate information, status, or actions. Where color is used as an indicator, text, icons, or numbers also communicate the information. See WCAG 1.4.1 Use of Color. |
302.4 Without Hearing |
Not Applicable |
The product does not provide an audible mode of operation. Hearing is not required to use the product. |
302.5 With Limited Hearing |
Not Applicable |
The product does not provide an audible mode of operation. Hearing is not required to use the product. |
302.6 Without Speech |
Not Applicable |
The product does not require speech for input, control, or operation. |
302.7 With Limited Manipulation |
Supports |
All product functionality is operable through a keyboard interface without requiring specific timings for individual keystrokes. The product does not require multipoint or path-based gestures, dragging movements, or device motion to operate. See WCAG 2.1.1 Keyboard, 2.1.2 No Keyboard Trap, 2.5.1 Pointer Gestures, and 2.5.7 Dragging Movements. |
302.8 With Limited Reach and Strength |
Supports |
The product is software-based and can be operated through standard keyboard and pointer interfaces and compatible assistive technologies. It does not introduce product-specific requirements for extended reach or physical force. |
302.9 With Limited Language, Cognitive, and Learning Abilities |
Partially Supports |
The product provides consistent navigation and identification, descriptive headings and labels, predictable interactions, and error identification and suggestions. However, the block editor sidebar’s heading hierarchy does not accurately communicate the organization of its sections. In the classic editor metabox, dismissing an issue does not provide visual or auditory confirmation that the action was completed. These limitations may make the content structure and results of actions harder to understand. See WCAG 1.3.1 Info and Relationships, 2.4.10 Section Headings, and 4.1.3 Status Messages for details. |
Chapter 4: Hardware
Notes: Not Applicable.
Chapter 5: Software
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
501.1 Scope – Incorporation of WCAG 2.0 AA |
See WCAG 2.x section |
See information in WCAG 2.x section |
502.2.1 User Control of Accessibility Features |
Not Applicable |
The product is a WordPress plugin operating within a web browser and does not provide platform-level accessibility settings. User control of those settings is provided by the browser and operating system. |
502.2.2 No Disruption of Accessibility Features |
Supports |
The product does not disrupt browser or operating system accessibility features. Users can continue to use screen readers, browser zoom, text resizing, and compatible assistive technologies while operating the product. |
502.3.1 Object Information |
Supports |
User interface components expose their roles, states, properties, boundaries, names, and descriptions through semantic HTML and appropriate WAI-ARIA attributes, making this information available to assistive technologies through the browser’s accessibility services. |
502.3.2 Modification of Object Information |
Supports |
User-settable states and properties of interactive components can be changed programmatically, including through compatible assistive technologies. The resulting states are reflected in the browser’s accessibility tree. |
502.3.3 Row, Column, and Headers |
Supports |
Data tables use semantic HTML to expose row and column structure and associated headers, allowing assistive technologies to determine the relationships between headers and data cells. |
502.3.4 Values |
Supports |
The current values and any applicable allowable values or ranges of interactive controls are programmatically determinable through standard HTML and appropriate accessibility attributes. |
502.3.5 Modification of Values |
Supports |
The product allows users to set and change editable control values through standard HTML controls and compatible assistive technologies. These controls are operable through a keyboard interface without requiring pointer gestures. |
502.3.6 Label Relationships |
Supports |
The product programmatically associates labels with form fields and interactive controls throughout its interface. These labeling relationships are available to assistive technologies. |
502.3.7 Hierarchical Relationships |
Partially Supports |
The product generally exposes the organization of content through semantic markup. However, the block editor’s Accessibility Checker sidebar title and accordion headings all use H2 elements, rather than nesting the accordion headings beneath the sidebar title. This does not accurately convey the intended heading hierarchy. The heading levels are defined by the WordPress core Panel components and cannot currently be configured. See WCAG 1.3.1 Info and Relationships and GitHub Issue #1764. |
502.3.8 Text |
Supports |
The product renders text using standard HTML so that text content, attributes, and boundaries are programmatically determinable by assistive technologies through the browser’s accessibility services. |
502.3.9 Modification of Text |
Supports |
The product provides a Simplified Summary text field that allows authors to enter, edit, and save summary text for display on the website’s front end. The field supports keyboard editing and programmatic text modification through compatible assistive technologies. |
502.3.10 List of Actions |
Supports |
Available actions on interactive components are programmatically determinable through standard HTML semantics and appropriate WAI-ARIA roles and states. Assistive technologies can identify actions such as activating a control, selecting an option, or expanding and collapsing a section. |
502.3.11 Actions on Objects |
Supports |
The product allows compatible assistive technologies to execute available actions on interactive components through standard browser accessibility services. Buttons, links, and form controls are operable through a keyboard interface. |
502.3.12 Focus Cursor |
Supports |
The product exposes keyboard focus, text insertion point, and selection information through standard HTML controls and browser accessibility services, allowing compatible assistive technologies to track and report this information. |
502.3.13 Modification of Focus Cursor |
Supports |
User-settable focus, text insertion point, and selection attributes can be changed programmatically through compatible assistive technologies using standard browser and HTML control behavior. |
502.3.14 Event Notification |
Partially Supports |
The product generally exposes changes to interactive component states and values to assistive technologies. However, some updates are not automatically announced to screen reader users. These include validation errors in the email opt-in form and refreshed accessibility analysis results in the block editor sidebar. In the classic editor metabox, dismissing an issue does not provide visual or auditory confirmation that the action was completed. See WCAG 4.1.3 Status Messages for details. |
502.4 Platform Accessibility Features |
Not Applicable |
The product does not provide a platform or platform software. Features such as sequential key entry, keyboard acceptance timing, and platform speech output are provided by the browser and operating system. |
503.2 User Preferences |
Not Applicable |
The product is a web application and falls within the exception under 503.2. Browser zoom and supported browser or operating system accessibility settings remain available to users. |
503.3 Alternative User Interfaces |
Not Applicable |
The product does not provide an alternative user interface that functions as assistive technology. |
503.4.1 Caption Controls |
Not Applicable |
The product does not display video with synchronized audio or provide media playback controls. |
503.4.2 Audio Description Controls |
Not Applicable |
The product does not display video with synchronized audio or provide media playback controls. |
504.2 Content Creation or Editing |
Supports |
The product allows authors to create and edit a simplified text summary for display on the website’s front end. This feature provides a way to supplement complex content with an easier-to-read explanation. The accessibility of the authoring interface is addressed in the WCAG tables. |
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion |
Not Applicable |
The product’s simplified-summary authoring feature saves text for display on the website’s front end. It does not convert content between formats or save content in multiple formats. |
504.2.2 PDF Export |
Not Applicable |
The product does not export PDFs. |
504.3 Prompts |
Supports |
The product evaluates content readability and prompts authors to provide a simplified summary when the detected reading level exceeds ninth grade. It provides a summary-entry field, summary reading-level feedback, and links to guidance on improving readability. The product also provides accessibility findings and remediation guidance to help authors address detected issues in WordPress content. |
504.4 Templates |
Not Applicable |
The product does not provide templates. |
Chapter 6: Support Documentation and Services
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
602.2 Accessibility and Compatibility Features |
Supports |
Product documentation lists and explains built-in accessibility and assistive technology compatibility features. The product accessibility guide provides keyboard instructions for the frontend highlighter, block editor sidebar, and Classic Editor report. These instructions were verified in the evaluated plugin version. |
602.3 Electronic Support Documentation |
Supports |
Electronic product documentation and web-based support have been evaluated and verified to meet WCAG 2.2 Level A and AA requirements. Documentation is provided as HTML pages with semantic structure, descriptive headings and links, and accessible instructions. See the product documentation and Equalize Digital Accessibility Statement. |
602.4 Alternate Formats for Non-Electronic Support Documentation |
Not Applicable |
Support documentation is provided electronically as HTML pages on the product website. No non-electronic support documentation is provided. |
603.2 Information on Accessibility and Compatibility Features |
Supports |
Support staff provide information about built-in accessibility features, assistive technology compatibility, known limitations, and available workarounds. Staff references include the verified product accessibility guide and applicable ACRs. The internal accessible-support procedure defines request ownership and escalation for accessibility questions and accommodation arrangements. |
603.3 Accommodation of Communication Needs |
Supports |
Users may request accessible communication or information directly through accessibilityhelp@equalizedigital.com or existing support channels. No paid license, account, diagnosis, or proof of disability is required. Available accommodations include written instructions, text descriptions of visual information, smaller instruction steps, accessible electronic formats, email alternatives, and Zoom calls when appropriate. Support staff own follow-up and escalate accessibility questions or accommodation logistics to the designated contacts. These options are described in the public support article and Accessibility Statement. |
EN 301 549 Report
Chapter 4: Functional Performance Statements (FPS)
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
4.2.1 Usage without vision |
Partially Supports |
The product supports operation without vision through screen reader compatibility, keyboard access, text alternatives, and logical reading and focus order. However, the block editor sidebar’s heading hierarchy does not accurately convey its structure. Email opt-in validation errors and refreshed sidebar results are not automatically announced. Dismissing an issue in the Classic Editor report does not provide confirmation. See WCAG 1.3.1 Info and Relationships and 4.1.3 Status Messages. |
4.2.2 Usage with limited vision |
Partially Supports |
The product supports text resizing and browser zoom to 200%, provides sufficient text contrast, and generally reflows at 400% zoom. However, the “Want to do more with Accessibility Checker? Unlock Pro Features” section in the WordPress admin footer is unavailable at 400% zoom because WordPress core hides the footer at smaller viewport widths. See WCAG 1.4.10 Reflow. |
4.2.3 Usage without perception of colour |
Supports |
The product does not rely on color alone to communicate information, status, or actions. Text, icons, or numbers also convey information where color is used. See WCAG 1.4.1 Use of Color. |
4.2.4 Usage without hearing |
Not Applicable |
The evaluated product does not provide an audible mode of operation. Hearing is not required to use the product. |
4.2.5 Usage with limited hearing |
Not Applicable |
The evaluated product does not provide an audible mode of operation. Hearing is not required to use the product. |
4.2.6 Usage with no or limited vocal capability |
Not Applicable |
The product does not require vocal input for control or operation. |
4.2.7 Usage with limited manipulation or strength |
Supports |
All product functionality is operable through a keyboard interface without requiring specific timings for individual keystrokes. The product does not require multipoint or path-based gestures, dragging movements, or device motion. See WCAG 2.1.1 Keyboard, 2.1.2 No Keyboard Trap, 2.5.1 Pointer Gestures, and 2.5.7 Dragging Movements. |
4.2.8 Usage with limited reach |
Not Applicable |
The evaluated product is software and does not provide free-standing or installed hardware, physical controls, or product-specific reach requirements. |
4.2.9 Minimize photosensitive seizure triggers |
Supports |
The product does not contain flashing content that could trigger photosensitive seizures. See WCAG 2.3.1 Three Flashes or Below Threshold. |
4.2.10 Usage with limited cognition, language or learning |
Partially Supports |
The product provides consistent navigation and identification, descriptive headings and labels, predictable interactions, and error identification and suggestions. However, the block editor sidebar’s heading hierarchy does not accurately communicate its organization. In the Classic Editor report, dismissing an issue does not provide visual or auditory confirmation. These limitations may make the structure and results of actions harder to understand. See WCAG 1.3.1 Info and Relationships, 2.4.10 Section Headings, and 4.1.3 Status Messages. |
4.2.11 Privacy |
Supports |
Using the product’s accessibility features, accessibility settings, or compatible assistive technologies does not introduce different privacy behavior or require additional disclosure. Users of these features receive the same level of privacy as other users. |
Chapter 5: Generic Requirements
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
5.1.2.1 Closed functionality |
Not Applicable |
The product is web-based software with no closed functionality. Users can use compatible assistive technologies through the browser and operating system. |
5.1.2.2 Assistive technology |
Not Applicable |
The product has no closed functionality that must operate without connected or installed assistive technology. |
5.1.3.1 Audio output of visual information |
Not Applicable |
The product has no closed functionality. The non-visual access requirements for closed functionality do not apply. |
5.1.3.2 Auditory output delivery including speech |
Not Applicable |
The product has no closed functionality. The non-visual access requirements for closed functionality do not apply. |
5.1.3.3 Auditory output correlation |
Not Applicable |
The product has no closed functionality. The non-visual access requirements for closed functionality do not apply. |
5.1.3.4 Speech output user control |
Not Applicable |
The product has no closed functionality. The non-visual access requirements for closed functionality do not apply. |
5.1.3.5 Speech output automatic interruption |
Not Applicable |
The product has no closed functionality. The non-visual access requirements for closed functionality do not apply. |
5.1.3.6 Speech output for non-text content |
Not Applicable |
The product has no closed functionality. The non-visual access requirements for closed functionality do not apply. |
5.1.3.7 Speech output for video information |
Not Applicable |
The product has no closed functionality. The non-visual access requirements for closed functionality do not apply. |
5.1.3.8 Masked entry |
Not Applicable |
The product has no closed functionality. The non-visual access requirements for closed functionality do not apply. |
5.1.3.9 Private access to personal data |
Not Applicable |
The product has no closed functionality. The non-visual access requirements for closed functionality do not apply. |
5.1.3.10 Non-interfering audio output |
Not Applicable |
The product has no closed functionality. The non-visual access requirements for closed functionality do not apply. |
5.1.3.11 Private listening volume |
Not Applicable |
The product has no closed functionality. The non-visual access requirements for closed functionality do not apply. |
5.1.3.12 Speaker volume |
Not Applicable |
The product has no closed functionality. The non-visual access requirements for closed functionality do not apply. |
5.1.3.13 Volume reset |
Not Applicable |
The product has no closed functionality. The non-visual access requirements for closed functionality do not apply. |
5.1.3.14 Spoken languages |
Not Applicable |
The product has no closed functionality or built-in speech synthesizer. Screen reader language behavior is provided through the browser and the user’s assistive technology. |
5.1.3.15 Non-visual error identification |
Not Applicable |
The product has no closed functionality or built-in speech output. Input error identification and announcement findings for the open web interface are documented under WCAG 3.3.1 and 4.1.3. |
5.1.3.16 Receipts, tickets, and transactional outputs |
Not Applicable |
The product has no closed functionality. The non-visual access requirements for closed functionality do not apply. |
5.1.4 Functionality closed to text enlargement |
Not Applicable |
The product is not closed to text enlargement through browser or assistive technology settings. Text resizing and reflow are addressed under WCAG 1.4.4 and 1.4.10. |
5.1.5 Visual output for auditory information |
Not Applicable |
The product has no closed functionality requiring auditory information and does not provide an audible mode of operation. |
5.1.6.1 Closed functionality |
Not Applicable |
The product has no functionality closed to keyboards or keyboard interfaces. Keyboard operation is addressed under WCAG 2.1.1. |
5.1.6.2 Input focus |
Not Applicable |
The product has no functionality closed to keyboards or keyboard interfaces. Focus movement and keyboard traps in the open web interface are addressed under WCAG 2.1.2 and 2.4.3. |
5.1.7 Access without speech |
Not Applicable |
The product has no closed functions requiring speech input. Speech is not required to use the product. |
5.2 Activation of accessibility features |
Supports |
Documented accessibility features can be accessed and activated using keyboard-operable controls and compatible assistive technologies. Users do not need a mouse, vision, hearing, or speech to enable a feature intended to meet the corresponding access need. |
5.3 Biometrics |
Not Applicable |
The product does not use biometric characteristics for identification or control. |
5.4 Preservation of accessibility information during conversion |
Not Applicable |
The product does not convert information or communication between formats. The Simplified Summary feature saves author-entered text for display on the website; it does not perform format conversion. |
5.5.1 Means of operation |
Not Applicable |
The product is software and provides no physical operable parts requiring grasping, pinching, or twisting of the wrist. |
5.5.2 Operable parts discernibility |
Not Applicable |
The product provides no physical operable parts. Programmatic identification of software controls is addressed in the WCAG and software sections. |
5.6.1 Tactile or auditory status |
Not Applicable |
The product provides no hardware locking or toggle controls. Software control states are exposed through HTML and accessibility attributes, as addressed in the WCAG and software sections. |
5.6.2 Visual status |
Not Applicable |
The product provides no hardware locking or toggle controls. Visual and programmatic software control states are addressed in the WCAG and software sections. |
5.7 Key repeat |
Not Applicable |
The product does not provide a key repeat function. Key repeat settings are controlled by the user’s operating system or input device. |
5.8 Double-strike key acceptance |
Not Applicable |
The product does not provide a keyboard or keypad or control double-strike key acceptance. These settings are provided by the user’s platform or input device. |
5.9 Simultaneous user actions |
Not Applicable |
The product does not require simultaneous user actions. Its functions are available through individual keyboard or pointer actions without product-specific key chords or multitouch gestures. |
Chapter 6: ICT with Two-Way Voice Communication
Notes: Not Applicable.
Chapter 7: ICT with Video Capabilities
Notes: Not Applicable.
Chapter 8: Hardware
Notes: Not Applicable.
Chapter 9: Web (see WCAG 2.x section)
Notes: Report for web in the WCAG 2.x section.
Chapter 10: Non-Web Documents
Notes: Not Applicable
Chapter 11: Software
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
11.1.1.1 through 11.4.1.3 |
Not Applicable |
These clauses address non-web software. The evaluated product is web-based; applicable web-content conformance and exceptions are documented in the WCAG 2.x section for EN 301 549 Chapter 9. |
11.5.2.1 Platform accessibility service support for software that provides a user interface |
Not Applicable |
The product is a WordPress plugin, not platform software providing accessibility services to other applications. These services are provided by the browser and operating system. |
11.5.2.2 Platform accessibility service support for assistive technologies |
Not Applicable |
The product is not platform software providing accessibility services to assistive technologies. It uses the services of the browser and operating system. |
11.5.2.3 Use of accessibility services |
Supports |
The product uses semantic HTML, standard browser controls, and appropriate WAI-ARIA attributes to interoperate with assistive technologies through browser accessibility services. Specific limitations are identified in the applicable rows below. |
11.5.2.4 Assistive technology |
Not Applicable |
The product is an accessibility checking and authoring-support tool, not assistive technology as defined by this criterion. |
11.5.2.5 Object information |
Supports |
User interface components expose their roles, states, boundaries, names, and descriptions through semantic HTML and appropriate WAI-ARIA attributes, making this information available through browser accessibility services. |
11.5.2.6 Row, column, and headers |
Supports |
Data tables expose cell, row, column, and header relationships through semantic HTML so assistive technologies can determine the table structure. |
11.5.2.7 Values |
Supports |
The current values and any applicable minimum and maximum values of controls are programmatically determinable through standard HTML and accessibility attributes. |
11.5.2.8 Label relationships |
Supports |
Labels are programmatically associated with form fields and interactive controls throughout the product. Assistive technologies can determine these labeling relationships. |
11.5.2.9 Parent-child relationships |
Partially Supports |
The product generally exposes content relationships through semantic markup. However, the block editor sidebar title and accordion headings all use H2 elements rather than nesting accordion headings beneath the title. WordPress core Panel components define these heading levels and do not currently allow configuration. See WCAG 1.3.1 Info and Relationships and GitHub Issue #1764. |
11.5.2.10 Text |
Supports |
Text content, attributes, and boundaries are programmatically determinable through standard HTML controls and browser accessibility services. |
11.5.2.11 List of available actions |
Supports |
Available actions are programmatically determinable from control roles, names, and states, including activating buttons and links, selecting options, and expanding or collapsing sections. |
11.5.2.12 Execution of available actions |
Supports |
Compatible assistive technologies can execute available actions through standard browser accessibility services. Buttons, links, and form controls support keyboard operation. |
11.5.2.13 Tracking of focus and selection attributes |
Supports |
Keyboard focus, text insertion points, and selection attributes are exposed through standard HTML controls and browser accessibility services. |
11.5.2.14 Modification of focus and selection attributes |
Supports |
Compatible assistive technologies can change focus, text insertion points, and selections wherever users can modify them, using standard browser and HTML control behavior. |
11.5.2.15 Change notification |
Partially Supports |
The product generally exposes changes to control states and values. However, email opt-in validation errors and refreshed block editor sidebar results are not automatically announced to screen reader users. Dismissing an issue in the Classic Editor report does not provide confirmation of the completed action. See WCAG 4.1.3 Status Messages. |
11.5.2.16 Modifications of states and properties |
Supports |
User-settable states and properties can be changed programmatically through compatible assistive technologies. Resulting states are reflected in the browser accessibility tree. |
11.5.2.17 Modifications of values and text |
Supports |
Users can enter and edit values and text in product fields, including settings and the Simplified Summary, through standard HTML controls and compatible assistive technologies. |
11.6.1 User control of accessibility features |
Not Applicable |
The product is not platform software and does not provide platform accessibility settings. User control of those settings is provided by the browser and operating system. |
11.6.2 No disruption of accessibility features |
Supports |
The product does not disrupt browser or operating system accessibility features. Users can continue to use screen readers, browser zoom, text resizing, and compatible assistive technologies. |
11.7 User preferences |
Partially Supports |
The product supports browser zoom and text resizing. Tested settings-page buttons, report tabs, and links respond to the selected WordPress admin color scheme. However, some text does not follow the browser’s default font size preference. Settings-page text inherits fixed font sizes from WordPress Core; see WordPress Core ticket #66628. The product also defines fixed pixel font sizes in parts of its reports and frontend highlighter. |
11.8.2 Accessible content creation |
Supports |
The product supports authoring a Simplified Summary for display on the website. It evaluates readability, prompts authors to provide a summary when the reading level exceeds ninth grade, and provides summary reading-level feedback. Accessibility checks, issue explanations, remediation guidance, and available automatic fixes help authors create accessible WordPress content. Automated checks do not replace manual review. |
11.8.3 Preservation of accessibility information in transformations |
Not Applicable |
The product does not provide restructuring or re-coding transformations between content formats. The Simplified Summary feature saves author-entered text for display on the website. |
11.8.4 Repair assistance |
Supports |
When accessibility checks detect an issue, the product provides issue-specific explanations, repair suggestions, and links to detailed documentation. For supported issue types it also offers configurable automatic fixes. Readability guidance prompts authors to provide a simplified summary where needed. |
11.8.5 Templates |
Not Applicable |
The product does not provide content templates. |
Chapter 12: Documentation and Support Services
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
12.1.1 Accessibility and compatibility features |
Supports |
Product documentation lists and explains built-in accessibility and assistive technology compatibility features. The product accessibility guide provides keyboard instructions for the frontend highlighter, block editor sidebar, and Classic Editor report. These instructions were verified in the evaluated plugin version. See the product accessibility guide. |
12.1.2 Accessible documentation |
Supports |
Electronic product documentation is provided as HTML pages on the product website. Its accessibility has been evaluated and verified to meet WCAG 2.2 Level A and AA requirements, including the WCAG 2.1 Level A and AA requirements referenced by EN 301 549 Chapter 9. See the product documentation and Equalize Digital Accessibility Statement. |
12.2.2 Information on accessibility and compatibility features |
Supports |
Support staff provide information about built-in accessibility features, assistive technology compatibility, known limitations, and available workarounds. Staff references include the verified product accessibility guide and applicable ACRs. The internal accessible-support procedure defines request ownership and escalation for accessibility questions and accommodation arrangements. |
12.2.3 Effective communication |
Supports |
Users may request accessible communication or information through accessibilityhelp@equalizedigital.com or existing support channels. No paid license, account, diagnosis, or proof of disability is required to request accessibility assistance. Accommodations include written instructions, text descriptions of visual information, smaller instruction steps, accessible electronic formats, email alternatives, and Zoom calls when appropriate. The support assignee owns follow-up; accessibility questions and accommodation logistics are escalated to designated staff. See the public support article and Accessibility Statement. |
12.2.4 Accessible documentation |
Supports |
Documentation provided by support services is available in accessible electronic formats, including HTML pages on the product website. Product documentation and the web-based support experience have been evaluated and verified to meet WCAG 2.2 Level A and AA requirements, including the WCAG 2.1 Level A and AA requirements referenced by EN 301 549 Chapter 9. Accessible communication and format requests are handled through the documented support procedure. |
Chapter 13: ICT Providing Relay or Emergency Service Access
Notes: Not Applicable
Legal Disclaimer (Equalize Digital, Inc.)
This Accessibility Conformance Report (ACR) is provided for informational purposes only and is not legal advice. The purpose of this ACR is to assist Equalize Digital, Inc. customers in making preliminary assessments regarding the features that support accessibility in version 1.52 of Accessibility Checker.
Equalize Digital, Inc. makes no warranties of any kind, expressed or implied, in or about this ACR. Equalize Digital, Inc. expressly disclaims any liability with respect to this ACR.
Equalize Digital, Inc. cannot guarantee the accuracy of this information, which may be changed without prior notice. Equalize Digital is not a law firm. Website owners are solely responsible for assessing and ensuring their website complies with applicable laws and regulations, including the Americans with Disabilities Act (ADA), European Accessibility Act (EAA), and Section 508, among others.