Report Information
↑ Volver al principioWCAG Edition
(Based on VPAT® Version 2.5Rev)
Name of Product/Version:
Product Vendors for WooCommerce 2.5.2
Report Date:
July 14, 2026
Product Description:
Product Vendors for WooCommerce is an extension that enables a WooCommerce installation to function as a multi-vendor marketplace. The extension allows multiple third-party vendors to list and sell products through a single storefront while the marketplace owner manages vendor participation, commission structures, and payout settings. Supported product types include physical goods, digital downloads, and time-based bookings when integrated with WooCommerce Bookings.
Configuration and administration are performed through the WordPress and WooCommerce administrative interfaces. Vendors can manage their own product listings, shipping rules, order notes, and view sales reports in the WordPress admin.
Contact Information:
If you encounter an accessibility issue, please contact support or email us at accessibility@woocommerce.com.
Notes:
The scope of this report is limited to the accessibility of user interfaces for the Product Vendors for WooCommerce, including both front-end interfaces for store customers and WordPress admin interfaces that vendor users use to manage products.
Testing of front-end components was completed on a website utilizing the Storefront theme (version 4.6.1) with default settings. As WordPress themes can significantly impact frontend design and accessibility, the reported conformance levels may not apply to websites built with other themes or customized themes.
Testing of admin vendor interfaces was completed on a website running WordPress version 7.0 and WooCommerce version 10.9.3. This report does not cover accessibility in the WordPress content management system or for WooCommerce as a whole. Some Product Vendor admin interfaces differ from WooCommerce core admin interfaces and the views other user roles see. Accessibility issues reported should not be assumed to apply to similar views in WooCommerce core. Find a front-end Accessibility Conformance Report for WooCommerce core here.
Information about product help and support documentation is located in our website Accessibility Statement.
Evaluation Methods Used:
Accessibility assessment was completed by Equalize Digital, Inc., using industry-standard automated testing tools and manual testing techniques. Manual testing was completed by certified accessibility professionals using leading assistive technology, such as screen readers (NVDA, VoiceOver, and JAWS), screen magnifiers, and keyboard navigation. Accessibility testing was conducted by certified accessibility professionals.
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 ) |
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
↑ Volver al principioNote: 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) |
Supports |
All meaningful non-text content is provided with appropriate text alternatives that convey equivalent information to assistive technologies. |
Not Applicable |
There is no prerecorded audio or video in the product. |
|
1.2.2 Captions (Prerecorded) (Level A) |
Not Applicable |
There is no prerecorded video in the product. |
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) |
Not Applicable |
There is no prerecorded video in the product. |
1.3.1 Info and Relationships (Level A |
Partially Supports |
In some cases, programmatic relationships are not consistently conveyed for Vendor users. These issues primarily exist in the WordPress admin for Vendor users, not in the front-end customer interfaces. Issues present may make it difficult for users of assistive technology to become a product vendor or view reports on their products. Examples of known issues include:
These issues are being tracked and will be remediated in the future. |
1.3.2 Meaningful Sequence (Level A) |
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) |
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) |
Partially Supports |
Most parts of the product support this success criterion. The parts of the product that do not support are related to the reports admin views for Vendors. In the reports views, color is used as the only means to distinguish links and chart data series. In the case of reports, no additional visual or programmatic indicators are provided. It may be difficult for vendors with color blindness to understand or interpret reports in the plugin. The Product Vendor Reports UI comes from WooCommerce core and uses a version of reports that were marked as deprecated in WooCommerce 4.0. Automattic is currently in the process of reworking analytics and reports in WooCommerce core; when that is complete, reports will be upgraded in Product Vendors, and these issues will be resolved. A timeline for these fixes is not currently available. |
1.4.2 Audio Control (Level A) |
Not Applicable |
There is no audio that plays automatically. |
2.1.1 Keyboard (Level A) |
Partially Supports |
Most parts of the product support this success criterion. The parts of the product that do not support are related to the reports admin views for Vendors. Examples of known issues include:
The Product Vendor Reports UI comes from WooCommerce core and uses a version of reports that were marked as deprecated in WooCommerce 4.0. Automattic is currently in the process of reworking analytics and reports in WooCommerce core; when that is complete, reports will be upgraded in Product Vendors, and these issues will be resolved. A timeline for these fixes is not currently available. |
2.1.2 No Keyboard Trap (Level A) |
Supports |
There are no keyboard traps present in the product. |
2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2) |
Not Applicable |
There are no single-key keyboard shortcuts in the product. |
2.2.1 Timing Adjustable (Level A) |
Partially Supports |
Most parts of the product support this success criterion. Error messages on the add/edit product screen, which come from WooCommerce core use browser-based validation and disappear automatically after a short period without providing a mechanism to extend, adjust, or disable the time limit. Vendor users may not have sufficient time to perceive and act on the information. |
2.2.2 Pause, Stop, Hide (Level A) |
Not Applicable |
There is no moving, blinking, scrolling, or auto-updating content in the products. |
2.3.1 Three Flashes or Below Threshold (Level A) |
Supports |
The product does not contain flashing content or anything that flashes more than three times per second. |
2.4.1 Bypass Blocks (Level A) |
Not Applicable |
This criterion does not apply to the product because it does not create full pages on the front end or in the admin. Admin views support WordPress core’s built-in skip links. |
2.4.2 Page Titled (Level A) |
Not Applicable |
This criterion does not apply to the product because it does not create full pages on the front end or in the admin. |
2.4.3 Focus Order (Level A) |
Partially Supports |
Most parts of the product support this success criterion. On the individual orders view for vendor users, keyboard focus does not follow a logical sequence. Focus moves to the right sidebar elements before the main content, disrupting the expected top-to-bottom, left-to-right navigation order. This is a minor issue that will be resolved in a future version of WooCommerce core. |
2.4.4 Link Purpose (In Context) (Level A) |
Supports |
The purpose of each link can be determined from the link text alone or from the link text together with its programmatically associated context. |
2.5.1 Pointer Gestures (Level A 2.1 and 2.2) |
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) |
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) |
Partially Supports |
Most parts of the product support this success criterion. There are some selects in the admin, such as the Bulk Actions selects and filters above the orders table, that don’t have persistent visible labels, so the accessible name doesn’t match or include the visible text, which may prevent activation via speech recognition. This is an issue coming from WordPress core, not the Product Vendors admin, but it may impact usability for some Vendor Users. A fix for this is currently milestoned for WordPress version 7.1. |
2.5.4 Motion Actuation (Level A 2.1 and 2.2) |
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) |
Not Applicable |
This criterion does not apply to the product because it does not create full pages on the front end or in the admin. |
3.2.1 On Focus (Level A) |
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) |
Supports |
Changing the value of input controls does not automatically trigger unexpected context changes such as navigation, submission, or focus shifts. |
3.2.6 Consistent Help (Level A 2.2 only) |
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) |
Supports |
Input errors are clearly identified and communicated to users. |
3.3.2 Labels or Instructions (Level A) |
Partially Supports |
Most parts of the product support this success criterion. However, several controls in the admin orders screen and individual orders view lack visible, persistent labels or rely only on placeholder text. In some cases, the accessible name does not match the visible label, or there is no accessible name. These issues are being tracked and will be remediated in the future. |
3.3.7 Redundant Entry (Level A 2.2 only) |
Supports |
Users are not required to re-enter previously provided information. |
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 |
Supports |
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) |
Does Not Support |
Multiple user interface components in the admin views for vendor users are not programmatically exposed with the correct name, role, or state. Interactive elements use incorrect roles, missing or invalid ARIA attributes, and do not properly communicate states such as expanded, selected, current, or disabled. As a result, assistive technology users may not understand the purpose, behavior, or status of these controls, and vendor users may have difficulty adding products or viewing reports. Examples of known issues include:
The Product Vendor Reports UI comes from WooCommerce core and uses a version of reports that were marked as deprecated in WooCommerce 4.0. Automattic is currently in the process of reworking analytics and reports in WooCommerce core; when that is complete, reports will be upgraded in Product Vendors, and these issues will be resolved. Other issues related to the WooCommerce core admin are being tracked and will be addressed in future updates. A timeline for these fixes is not currently available. |
Table 2: Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
1.2.4 Captions (Live) (Level AA) |
Not Applicable |
There are no live videos in the product. |
1.2.5 Audio Description (Prerecorded) (Level AA) |
Not Applicable |
There is no prerecorded video in the product. |
1.3.4 Orientation (Level AA 2.1 and 2.2) |
Supports |
The products do not restrict the view and operation to a single display orientation, such as portrait or landscape. |
1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2) |
Partially Supports |
Input fields that collect user information do not provide a programmatically identifiable purpose using appropriate autocomplete attributes. Examples of known issues include:
The Product Vendor Reports UI comes from WooCommerce core and uses a version of reports that were marked as deprecated in WooCommerce 4.0. Automattic is currently in the process of reworking analytics and reports in WooCommerce core; when that is complete, reports will be upgraded in Product Vendors, and these issues will be resolved. |
1.4.3 Contrast (Minimum) (Level AA) |
Does Not Support |
Multiple text elements, including links, status labels, buttons, and interface text, do not meet minimum contrast requirements against their backgrounds. Examples of known issues include:
The Product Vendor Reports UI comes from WooCommerce core and uses a version of reports that were marked as deprecated in WooCommerce 4.0. Automattic is currently in the process of reworking analytics and reports in WooCommerce core; when that is complete, reports will be upgraded in Product Vendors, and these issues will be resolved. |
1.4.4 Resize text (Level AA) |
Partially Supports |
At 200% zoom, the date picker component is cropped, resulting in loss of content and preventing full access without loss of functionality on the Vendor Reports screen. The Product Vendor Reports UI comes from WooCommerce core and uses a version of reports that were marked as deprecated in WooCommerce 4.0. Automattic is currently in the process of reworking analytics and reports in WooCommerce core; when that is complete, reports will be upgraded in Product Vendors, and these issues will be resolved. |
1.4.5 Images of Text (Level AA) |
Supports |
Text is presented using styled HTML text rather than images of text |
1.4.10 Reflow (Level AA 2.1 and 2.2) |
Partially Supports |
At 400% zoom, modals and form controls are cropped, and chart and modal content overlap, resulting in loss of content and readability on the Vendor Reports screen. The Product Vendor Reports UI comes from WooCommerce core and uses a version of reports that were marked as deprecated in WooCommerce 4.0. Automattic is currently in the process of reworking analytics and reports in WooCommerce core; when that is complete, reports will be upgraded in Product Vendors, and these issues will be resolved. |
1.4.11 Non-text Contrast (Level AA 2.1 and 2.2) |
Partially Supports |
The focus indicator and chart elements have insufficient contrast against adjacent colors and backgrounds on the Vendor Reports Orders screen. |
1.4.12 Text Spacing (Level AA 2.1 and 2.2) |
Supports |
No loss of content or functionality of the product occurs by adjusting line height, paragraph spacing, word spacing, or letter spacing. |
1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2) |
Partially Supports |
Additional content triggered on hover obscures other page content. It cannot be dismissed without moving the pointer and does not remain visible when hovered, failing the dismissible and hoverable requirements of this criterion on the Vendor Reports screens. |
2.4.5 Multiple Ways (Level AA) |
Not Applicable |
This criterion does not apply to the product. |
2.4.6 Headings and Labels (Level 0AA) |
Does Not Support |
Headings are not organized in a logical hierarchical order. Skipped heading levels do not accurately represent page structure, which may make navigation difficult for screen reader users on the Vendor Individual Order view. |
2.4.7 Focus Visible (Level AA) |
Supports |
The focus indicator is visible in both the editor and on the front-end parts of the site created by the product. |
2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only) |
Supports |
When a user interface component receives keyboard focus, it is not obscured by author-created content. |
2.5.7 Dragging Movements (Level AA 2.2 only) |
Does Not Support |
The product add/edit screen requires a dragging movement to change the order of attributes or variations. There is no alternative method (e.g., a single pointer or keyboard interaction) to change the order of attributes or variations. |
2.5.8 Target Size (Minimum) (Level AA 2.2 only) |
Supports |
Targets in the product have a minimum height of 24px. |
3.1.2 Language of Parts (Level AA) |
Not Applicable |
The product’s content only includes the default language, with no additional languages. |
3.2.3 Consistent Navigation (Level AA) |
Supports |
Admin pages generated by the product provide a consistent navigational experience. |
3.2.4 Consistent Identification (Level AA) |
Supports |
Components that have the same functionality are identified consistently. |
3.3.3 Error Suggestion (Level AA) |
Supports |
The product offers users suggestions for resolving errors. |
Supports |
User-entered data is checked for input errors, and the user is given the opportunity to correct them. |
|
3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only) |
Supports |
Authentication does not rely on cognitive function tests. |
4.1.3 Status Messages (Level AA 2.1 and 2.2) |
Partially Supports |
Several status messages (e.g., form submission confirmation, add note) are visually displayed but are not programmatically exposed as status messages. As a result, screen readers do not automatically announce them, and users may not be informed of action outcomes on the Product Vendors profile and individual order screens. |
Table 3: Success Criteria, Level AAA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
1.2.6 Sign Language (Prerecorded) (Level AAA) |
Not Applicable |
There is no prerecorded video in the product. |
1.2.7 Extended Audio Description (Prerecorded) (Level AAA) |
Not Applicable |
There is no prerecorded video in the product. |
1.2.8 Media Alternative (Prerecorded) (Level AAA) |
Not Applicable |
There is no prerecorded video in the product. |
1.2.9 Audio-only (Live) (Level AAA) |
Not Applicable |
There is no live audio in the product. |
1.3.6 Identify Purpose (Level AAA 2.1 and 2.2) |
Supports |
In content implemented within the product using markup languages, the purpose of user interface components, icons, and regions can be programmatically determined. |
1.4.6 Contrast (Enhanced) (Level AAA) |
Partially Supports |
Some text in the product has a contrast ratio of at least 7:1 with the background, but multiple text elements, including links, status labels, buttons, and interface text, do not meet minimum contrast requirements against their backgrounds, let alone enhanced contrast. |
1.4.7 Low or No Background Audio (Level AAA) |
Not Applicable |
There is no prerecorded video or audio in the product. |
1.4.8 Visual Presentation (Level AAA) |
Supports |
The styles within the products allow users to change colors, width, and line spacing within their browser. The text is not justified and can be resized without assistive technology up to 200% without requiring horizontal scroll. |
1.4.9 Images of Text (No Exception) (Level AAA) |
Supports |
The product does not rely on images of text to convey information. |
2.1.3 Keyboard (No Exception) (Level AAA) |
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) |
Supports |
Timing is not an essential part of the event or activity presented by the product. |
2.2.4 Interruptions (Level AAA) |
Supports |
There are no auto-updating content or other interruptions in the product. |
2.2.5 Re-authenticating (Level AAA) |
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) |
Not Applicable |
The products do not contain or trigger timeouts which could result in a loss of data. |
2.3.2 Three Flashes (Level AAA) |
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) |
Not Applicable |
The product does not contain animations from interactions. |
2.4.8 Location (Level AAA) |
Not Applicable |
This criterion does not apply to the product. |
2.4.9 Link Purpose (Link Only) (Level AAA) |
Supports |
Multiple links ("Edit" and "view" links) have identical accessible names but lead to different destinations. When links are presented without surrounding context, users of assistive technologies cannot determine their distinct purposes on the Vendor Reports stock screen. |
2.4.10 Section Headings (Level AAA) |
Supports |
Headings in the products effectively organize and label sections or related content. |
2.4.12 Focus Not Obscured (Enhanced) (Level AAA 2.2 only) |
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) |
Partially Supports |
The focus indicator of the Edit product graphic links is implemented as a 2px shadow and is not fully visible. It does not provide sufficient thickness and contrast against adjacent colors to meet enhanced focus appearance requirements, making it difficult to perceive for users with low vision. |
2.5.5 Target Size (Level AAA 2.1 and 2.2) |
Partially Supports |
Some targets in the product meet the AAA sizing of 44px x 44px, but other elements, such as tooltip targets and elements on reports are not AAA conformant. Site owners can introduce custom stylesheets if they want to increase sizing to meet AAA conformance. |
2.5.6 Concurrent Input Mechanisms (Level AAA 2.1 and 2.2) |
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) |
Not Applicable |
The products do not use definitions, words, or phrases in an unusual or restricted manner, including idioms and jargon. |
3.1.4 Abbreviations (Level AAA) |
Not Applicable |
The product does not contain abbreviations. |
3.1.5 Reading Level (Level AAA) |
Not Applicable |
The product does not generate content on the front-end sufficient for calculating a reading-level check. Shop owners are encouraged to check the reading level for their content as it is entered. |
3.1.6 Pronunciation (Level AAA) |
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) |
Not Applicable |
This criterion does not apply to the product. |
3.3.5 Help (Level AAA) |
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) |
Supports |
Users can review and correct all data before final submission. |
3.3.9 Accessible Authentication (Enhanced) (Level AAA 2.2 only) |
Supports |
Authentication is accessible and compatible with assistive technologies. |
Legal Disclaimer (WooCommerce)
↑ Volver al principioThis Accessibility Conformance Report (ACR) is provided for informational purposes only and does not constitute legal advice or a guarantee of full legal compliance. The purpose of this ACR is to assist WooCommerce customers in making preliminary assessments regarding the features that support accessibility in version 2.5.2 of the Product Vendors extension.
WooCommerce makes no warranties of any kind, expressed or implied, in or about this ACR. WooCommerce and Equalize Digital, Inc. expressly disclaim any liability with respect to this ACR, including reliance thereon.
WooCommerce cannot guarantee the accuracy or completeness of this information, which is current as of the date of publication but may be changed without prior notice as further updates are made.