A prospective client asked us, can you include multiple products in a single VPAT?
Yes, this is definitely possible depending on the relationship between the products – the more connected the products (or services) are, the more a single VPAT makes sense. However, if the products are distinct from one another, then we’ll need to fill in a separate VPAT.
As a general rule, each distinct product should have its own VPAT and resulting Accessibility Conformance Report (ACR). However, there are situations where it makes sense to group products together.
Note: The terms VPAT and ACR are used interchangeably, but VPAT is simply the template and the ACR is the resulting report once the VPAT is filled out and completed.
Table of Contents
Official Guidance
The VPAT template itself acknowledges this situation. According to the WCAG edition of the VPAT:
Multiple Reports: When using the VPAT to create an Accessibility Conformance Report for complex products it may be helpful to separate answers into multiple reports. For example, when a product is an Authoring Tool that also has web content and documentation. When multiple reports are used for a complex product, it is required to explain this and how to reach the other reports in the Notes section of each report.
This official guidance confirms that while multiple reports are often preferred for complex products, there are legitimate scenarios where related products can be documented together, provided proper cross-referencing exists.
the Notes Section
The VPAT “Best Practices for Authors” guide also emphasizes the importance of the Notes section when documenting multiple products:
Notes: Add any notes applicable to product or the report
- Additional information about the product version that the document references
- Any revisions to the document
- Links to any related documents
- Additional information describing the product
- Additional information about what the document does or does not cover
- Information suggested by the WCAG 2.0 Conformance Claim
- Information needed to satisfy ISO/IEC 17050-1:2004, Supplier’s Declaration of Conformity
When combining multiple products or creating separate reports for complex products, the Notes section becomes crucial for explaining scope, limitations, and relationships between reports.
When to Use Separate VPATs
Most of the time, separate VPATs provide the clearest picture of accessibility:
- Different functional products: Products with fundamentally different purposes and functions should have separate VPATs
- Standalone user experiences: If users interact with the products independently, separate VPATs are recommended
- Products with different accessibility profiles: Products with significantly different levels of accessibility should not be combined
- Products on different release cycles: Products updated at different intervals are challenging to document together
When Combining Works
There are multiple scenarios where combining products/services into one VPAT can sense:
- Integrated suite: When the individual products work in concert with one another and are a part of a complete suite. For example, think of a mobile app with individual product add-ons that simply enhance the experience of the mobile app.
- Components of a complex product: Such as an authoring tool that includes web content and documentation
- Same codebase: Products built on the same technical framework with shared accessibility features
Practical Considerations
Keep in mind the various practical considerations involved with a VPAT/ACR:
- Buyers may need to evaluate specific components separately
- The procurement agent consideration is a big one. These are the people considering your product for purchase so you want to make sure they’re okay with combining multiple products.
- The VPAT edition needs to be for one technical standard for all products
- For example, you wouldn’t combine products where one needs to meet the Revised Section 508 Standard and the other WCAG 2.2 AA under the WCAG edition
- Combined VPATs may obscure important differences between products
- Combined VPATs tend to be longer and more complex which can make them difficult to read
Cost Implications
From a cost perspective, keep in mind:
- An audit will be necessary for each product or service
- The cost of VPAT services will rise
For example, we charge $550 to fill and complete the WCAG edition of the VPAT (and issue an ACR). But, if filling in the VPAT now requires extra work, we will need to charge extra.
Summary
The key takeaway is that sometimes it makes sense to combine products and/or services into one VPAT. This will usually be when the products are connected to one another. The more connected, the more one VPAT makes sense.
If you need help with VPAT services and/or would like to consult with us on what makes sense for your product or services, we’d love to help. Just send us a message and we’ll reply very shortly.
