Is a Partially Supported VPAT Acceptable for Section 508 Compliance?

If you have ever seen a sample VPAT, you have probably seen the phrase Partially Supported in the table appear more often than expected. It may raise anxiety for enthusiastic vendors. It even raises questions about enough VPAT Compliance by government and enterprise procurement teams.

So let’s address the core issue directly:

Is a Partially Supported VPAT form acceptable for Section 508 compliance?

The short answer is, sometimes it is acceptable but for the long answer you need to read this blog.

VPAT Accessibility depends on how, where, and why that status appears in the report. So keep reading to find out when partial support can still pass procurement scrutiny.

What is Partially Supported in a VPAT?

The remarks section of the Voluntary Product Accessibility Template sometimes support Partially Supported. It means that a product meets some but not all requirements of a specific accessibility criterion.

This is not a failure state. It is an honest declaration that certain features meet the requirement

Others may need remediation or have known limitations

Full “Supports” across every criterion is rare in software environment. You need to understand that accessibility exists on a spectrum.

Why partially supported is common in Real VPATs

Do you also have this assumption that a VPAT filled entirely with Supports remarks means the product has the highest chances of approval? Well, that is not how accessibility works.

Partially Supported means the product is real. It appears because:

• Some user flows are accessible while edge cases are not

• Third-party components have limitations

• Legacy features need remediation

• Accessibility needs assistive technology

Note: VPATs that mark everything as Supports with no explanation are more doubtful than those that use Partially Supported honestly.

Section 508 Compliance vs Perfection

One of the biggest misunderstandings to assure that Section 508 requires perfect accessibility.

Section 508 requires that accessibility is evaluated against WCAG success criteria. Compliance means that you document all the barriers transparently in the VPAT Form. It means there are reasonable accommodations or remediation plans.

A VPAT with Partially Supported entries can still be fully acceptable for Section 508 procurement, as long as the limitations are clearly explained.

If there are no critical blockers for the intended use. It is acceptable if the blockers are accompanied by context or mitigation.

Do procurement teams accept Partially Supported VPATs

No government buyer or accessibility reviewer will automatically reject your VPAT because it includes Partially Supported. Instead, they look deeper at the remarks section.

They need answers about the impacted users and how frequently the barriers occur. Your product will pass the review if there is a workaround or a remediation plan is in progress.

Q: When does a VPAT form with Partially Supported remark accepted?

A: Your VPAT can be accepted by the procurement team even if it has the partially supported remarks at some places. The reviews need to know if the issue affect core functionality or not. If it does not then you have a competitive edge that other vendors who lack transparency in their VPAT assessment.

A well-written Partially Supported entry with detailed remarks is often more acceptable than a vague Supports claim with no evidence. If you need expert guidance on partial conformance due to third party components, then consult ADACP. These VPAT providers offer detailed and honest remarks to help you win contracts.

When a Partially Supported VPAT Is Acceptable

A “Partially Supported” VPAT is generally acceptable when:

• The limitation affects non-core features

• The issue is low-impact or infrequent

• Assistive technology users can still complete primary tasks

• Clear remediation plans are documented

• The vendor demonstrates accessibility awareness and accountability

In many cases, agencies approve such products with the understanding that accessibility is an ongoing process.

When It Becomes a Problem

However, Partially Supported can raise red flags when critical workflows are inaccessible. You need thorough VPAT testing and remediation if multiple core criteria lack support.

Do not submit a VPAT that has vague or missing remarks section in front of the Partially Supported entry. You may face back and forth audits if the same issues appear across many criteria.

Why Honest VPATs Matter More Than “Perfect” Ones

Accessibility professionals and procurement teams increasingly value honesty over perfection. A realistic VPAT builds trust. Whereas, a flawless-looking VPAT invites doubt.

A VPAT filled with Partially Supported followed by clear, technical explanations signals responsibility and trustworthiness.

On the other hand, VPATs that mark everything as Supports without evidence often trigger follow-up audits and rejection.

What vendors should do about Partially Supported sections

If you’re a vendor preparing a VPAT, “Partially Supported” should never be used casually. Also, it should not be avoided. You can follow the below best practices:

• Explain what is supported and what is not

• Name affected components or user flows

• Reference testing tools and environments

• State if remediation is planned

• Avoid generic phrases like “not fully supported” without detail

With this approach, you can position your product as accessibility-aware rather than defensive.

Conclusion

Yes a “Partially Supported” VPAT can absolutely be acceptable for Section 508 compliance. Remember, the label does not matter, reviewers look at the quality of the explanation behind it.

Transparency always wins in accessibility compliance. If used correctly, even “Partially Supported,” becomes the most truthful answer of all. If your product has accessibility gaps and you need VPAT Assessment for all those Partially Supported sections then connect with ADACP.  They can guide you about user impact, workarounds and efficient remediation.