Accessibility procurement is the practice of evaluating software, services, and digital products for conformance with accessibility requirements before purchase, renewal, or implementation, while vendor management is the ongoing process of verifying that those commitments survive contract signature and show up in the delivered product. In my work with procurement teams, legal counsel, accessibility leads, and product owners, this is where many organizations stumble: they either ask nothing and buy avoidable barriers, or they write such rigid requirements that nearly every vendor fails on paper. The goal is not to create a perfect gate that blocks the market. The goal is to score accessibility in procurement in a way that is fair, evidence based, commercially realistic, and strong enough to reduce risk.
That balance matters because accessibility is now tied to legal exposure, customer experience, public-sector eligibility, and implementation cost. In the United States, agencies and many contractors align with Section 508 and WCAG. In Europe, the European Accessibility Act is raising expectations across private markets. Large enterprises increasingly require a current VPAT based on the Information Technology Industry Council template, accessibility roadmaps, and testing evidence before signing. Yet experienced buyers know a hard truth: a VPAT alone does not prove usability for disabled people, and a single defect should not always eliminate a vendor if the product is strategically important, the remediation path is credible, and contractual controls are in place. A workable procurement model distinguishes between nonnegotiable barriers, remediable gaps, and unsupported claims.
This hub page explains how to score accessibility in procurement without excluding every vendor. It defines the documents and signals that matter, shows how to weight criteria, and outlines a vendor management process that continues after selection. It also serves as the central guide for procurement and vendor management within compliance and implementation work. If your team needs a consistent way to compare platforms, respond to audit findings, and negotiate stronger accessibility terms, start here and use the linked subtopics to build a repeatable program.
Set the procurement objective before you set the scoring model
The first question is not “What percentage accessibility score should a vendor get?” The first question is “What are we buying, who will use it, and what harms occur if it is inaccessible?” A public-facing ecommerce platform, an employee HR portal, a video platform used for mandatory training, and a niche back-office tool do not carry identical risk. Procurement scoring must reflect the product’s user population, transaction criticality, and availability of alternatives. When I build scorecards, I start with four factors: legal obligation, audience size, task criticality, and replaceability. A customer login flow with identity verification is high criticality. A rarely used internal reporting add-on may be lower criticality, though still important.
Defining the objective also prevents teams from overcorrecting. If the organization states that only vendors with zero known issues can be considered, the process becomes detached from market reality. Even mature platforms often have some documented defects, especially in complex interfaces such as drag-and-drop dashboards, PDF exports, and custom data visualizations. Better procurement asks whether the vendor understands its gaps, tests systematically, prioritizes severe barriers, and can commit to remediation dates. That approach improves outcomes more than a pass-fail checkbox.
Use plain categories. Critical barriers are issues that block completion of core tasks for keyboard users, screen reader users, low-vision users, deaf users, or people relying on voice input. Major issues significantly degrade efficiency or independence. Minor issues create friction but do not prevent task completion. Scoring should reflect those distinctions. A vendor with three critical blockers in account creation should rank below a vendor with ten minor color contrast defects in low-use settings pages. Severity matters more than issue count.
Know what evidence to request from vendors
Strong accessibility procurement depends on evidence, not marketing claims. The standard document buyers request is the VPAT, usually mapped to WCAG and, where relevant, Section 508 or EN 301 549. A useful VPAT is current, product specific, version specific, and candid about partial support. A weak VPAT is generic, old, or filled with “supports” statements that do not match actual behavior. Ask for the publication date, tested version, testing methodology, assistive technologies used, and known limitations. If a vendor cannot answer those basics, confidence should drop immediately.
Do not stop at the VPAT. Request recent manual audit reports, sample defect tickets, accessibility roadmap milestones, and documentation of the vendor’s development process. Mature vendors can usually describe how they test components before release, who signs off on accessibility, and how they triage issues. Named tools help, but tools alone are not enough. Axe, WAVE, Accessibility Insights, Siteimprove, and Lighthouse catch only a subset of failures. Ask whether manual testing includes keyboard-only operation, screen readers such as JAWS, NVDA, or VoiceOver, zoom and reflow checks, focus visibility, caption verification, and error recovery flows. If mobile use is important, ask about TalkBack and VoiceOver on native or hybrid apps.
Also request evidence tied to your use case. If the product generates PDFs, ask whether tagged PDF output is supported. If it includes video, ask about captions, transcripts, and audio description workflows. If it relies on biometric verification, ask what accessible alternatives exist. Procurement teams often miss these feature-specific questions and end up with a technically conformant platform that still fails real tasks.
Build a weighted scoring framework that reflects risk
The most practical way to score accessibility without excluding every vendor is to use weighted criteria rather than a single absolute threshold. In complex procurements, I typically separate scoring into documentation quality, current conformance, usability risk, remediation capacity, and contractual readiness. That structure rewards vendors who are transparent and operationally mature, not just vendors who know the right terminology.
| Criterion | What to evaluate | Suggested weight | What strong evidence looks like |
|---|---|---|---|
| Documentation quality | Current VPAT, scope, test methods, version accuracy | 20% | Recent product-specific VPAT with detailed remarks and dates |
| Current conformance | Severity and breadth of known WCAG issues | 30% | Few or no critical blockers in core workflows |
| Usability risk | Impact on key user journeys and assistive technology support | 20% | Core tasks verified with keyboard and screen readers |
| Remediation capacity | Roadmap, staffing, SLA, defect handling, release cadence | 20% | Named owners, dated fixes, evidence of prior remediation |
| Contractual readiness | Willingness to accept accessibility terms, reporting, and cure periods | 10% | Acceptance of measurable obligations and escalation paths |
This model avoids the common mistake of treating all nonconformance equally. A vendor with moderate current gaps but excellent remediation capacity may be a better choice than a vendor with cleaner paperwork and weak contractual commitments. Weightings should change by procurement type. For a public-facing platform or regulated environment, increase current conformance and usability risk. For a lower-risk internal tool with few alternatives, remediation capacity may deserve more weight. The important point is consistency. Once the framework is set, use it across competing vendors so accessibility becomes a comparable procurement factor rather than a subjective afterthought.
Define red lines carefully so the process stays fair
A procurement program needs red lines, but too many red lines turn into a de facto market ban. Set only a small number of nonnegotiable conditions tied to mission-critical use. Examples include inability to complete authentication without a mouse, unreadable form labels for screen readers on required workflows, absence of captions for mandatory training content, or a vendor refusal to provide any accessibility documentation. Those are legitimate reasons to pause or disqualify because they either block access outright or indicate a lack of basic governance.
Everything else should move into a managed exception process. A managed exception does not mean “ignore the problem.” It means document the issue, assess affected users, identify workaround feasibility, assign a remediation deadline, and require executive approval for acceptance. This is especially important when the market has limited alternatives, as with specialized healthcare, finance, or industrial software. In those sectors, accessibility procurement often requires staged improvement rather than immediate perfection.
Fairness also means distinguishing between unsupported claims and transparent partial support. A vendor who says “supports” despite known failures is less trustworthy than a vendor who marks “partially supports,” explains limitations, and provides a fix roadmap. Procurement teams should reward honesty because honest vendors are easier to govern after contract award.
Validate claims with demos, testing, and scenario-based review
The fastest way to separate polished sales language from real accessibility maturity is to validate claims during evaluation. Ask vendors to demonstrate core workflows using only a keyboard. Require them to show focus order, visible focus, modal handling, form error identification, and screen reader announcements for status messages. If the product includes data tables, filters, or dashboards, ask for those specifically. Many products pass superficial navigation checks but break down in advanced interactions.
Scenario-based review works better than abstract discussion. Give each vendor the same tasks: create an account, recover a password, complete a transaction, upload a document, export a report, join a live meeting, or submit a support request. Then ask how a screen reader user, a low-vision zoom user, and a deaf user would complete the same tasks. This approach exposes implementation details that VPAT summaries can hide.
If your organization has accessibility specialists, include them in demos and score independently from procurement. If not, use an external auditor for finalist review. Even a limited targeted assessment on high-risk flows can prevent expensive surprises. I have seen organizations save months of remediation effort simply by testing the top five workflows before signature rather than after rollout.
Write contracts that turn accessibility promises into obligations
Procurement scoring matters, but contracts are what convert evaluation into leverage. Accessibility language should specify the applicable standard, usually WCAG 2.1 AA or WCAG 2.2 AA when feasible, define the in-scope product components, require maintenance of conformance in updates, and obligate the vendor to provide current documentation on request. Include timelines for remediation of critical and major defects, notice requirements when accessibility regressions are introduced, and escalation rights if issues remain unresolved.
Good contracts also define verification. Reserve the right to perform or commission accessibility testing, require cooperation in reproducing issues, and state that remediation cannot be deferred indefinitely to future roadmaps. For software-as-a-service products, tie accessibility commitments to release management and support terms. For content or service providers, require accessible deliverables, such as captioned media, tagged documents, and accessible templates.
Be realistic about remedies. Immediate termination for any accessibility defect is rarely enforceable or commercially wise. Better remedies include cure periods, service credits in some contexts, mandatory remediation plans, holdbacks tied to implementation milestones, or renewal conditions. The objective is to create incentives that improve accessibility over time while preserving business continuity.
Make vendor management continuous after award
Accessibility procurement does not end when a vendor is selected. The most effective organizations treat accessibility as a vendor management discipline with recurring checkpoints. During onboarding, confirm the version assessed, log known exceptions, assign internal owners, and define reporting frequency. During implementation, test configured workflows because accessible base products can become inaccessible through poor setup, custom code, or inaccessible uploaded content. During operations, review release notes, monitor user complaints, and retest high-risk journeys after major updates.
This hub approach is essential because procurement and vendor management overlap with implementation, legal review, security review, and user support. Your related subtopic pages should cover VPAT evaluation, contract clauses, exception management, implementation testing, and post-purchase monitoring in more depth, but the governing principle remains simple: score vendors based on evidence, severity, and remediation capability, then manage them against clear obligations.
Organizations that do this well do not exclude every vendor. They create a market signal. Vendors learn that vague assurances will not pass, severe barriers will be challenged, and credible improvement will be rewarded. Buyers gain defensible records, better user outcomes, and fewer late-stage accessibility crises. If you are building or refining your compliance and implementation program, use this page as the procurement and vendor management hub, standardize your scorecard, and make accessibility a measurable part of every purchasing decision.
Frequently Asked Questions
1. How can you score accessibility in procurement without automatically disqualifying most vendors?
The most practical approach is to treat accessibility as a weighted evaluation category instead of a simple pass/fail gate in every situation. Many organizations get into trouble by doing one of two things: they either ask vendors almost nothing about accessibility, or they impose rigid requirements so early that nearly every otherwise viable vendor is excluded. A better model is to define accessibility expectations clearly, score vendor maturity and product conformance separately, and then factor the results into the overall procurement decision according to risk, product impact, and business criticality.
In practice, this means creating a scoring framework that looks at more than a single checkbox. For example, you can assess whether the vendor has a current VPAT or accessibility conformance report, whether that documentation is credible and specific, whether the product has known barriers in key workflows, whether the vendor has an internal accessibility program, whether issues are tracked and remediated, and whether contractual commitments can be secured. This lets you distinguish between a vendor with minor, manageable gaps and a vendor with no accessibility process at all.
You should also tie the scoring model to risk tiers. A public-facing digital platform used by a large and diverse audience should be held to a higher standard than a low-impact internal tool with limited user exposure. That does not mean lower-risk tools get a free pass; it means the remediation expectations, approval path, and timeline can be calibrated realistically. The goal is not to declare every imperfect product unacceptable. The goal is to make informed decisions, document risk, require improvement, and avoid buying products that create preventable accessibility debt.
When done well, this method allows procurement teams to preserve competition, remain commercially practical, and still drive meaningful accessibility outcomes. Vendors are not excluded simply because they are not perfect today, but they are expected to show evidence, transparency, and a credible path to improvement.
2. What accessibility criteria should be included in a procurement scorecard?
A strong accessibility procurement scorecard should evaluate both the product itself and the vendor’s ability to sustain accessibility over time. That distinction matters because a polished VPAT alone does not guarantee accessible implementation, and a vendor with a good accessibility culture may still have real product gaps that need to be understood before purchase. Your scorecard should therefore include criteria that measure current conformance, organizational maturity, responsiveness, and contractual accountability.
Core product-level criteria often include alignment with WCAG requirements, completeness and quality of the VPAT or accessibility conformance report, test coverage across critical user journeys, compatibility with assistive technologies, keyboard accessibility, support for captions and transcripts where relevant, color contrast, form usability, error handling, and accessibility of documentation and support materials. If the solution includes mobile apps, PDFs, kiosks, or custom workflows, those should be explicitly included rather than assumed.
Vendor-level criteria should include whether the company has an accessibility policy, dedicated personnel or subject matter experts, formal testing processes, defect tracking for accessibility issues, training for design and engineering teams, customer escalation procedures, and a documented remediation process. You may also want to score how recently the product was evaluated, whether third-party testing was involved, and how transparent the vendor is about limitations. A vendor that openly identifies known issues and provides a remediation roadmap is usually a safer partner than one that offers vague assurances and little evidence.
Finally, the scorecard should include implementation and post-award criteria. Can the vendor commit to fixing issues within defined timeframes? Will they notify you of regressions or major changes? Can they provide updated conformance documentation after releases? Accessibility procurement is not just about pre-purchase validation. It is about ensuring that the commitments made during selection continue after the contract is signed and the product is deployed.
3. Is a VPAT enough to evaluate accessibility during software procurement?
No, a VPAT is useful, but it is not enough on its own. A VPAT can be a valuable starting point because it gives procurement teams a structured way to review a vendor’s claims about accessibility conformance. It can reveal whether the vendor understands accessibility standards, whether they have documented product limitations, and whether they are willing to put their claims in writing. However, a VPAT is still a vendor-supplied representation, and its quality can vary significantly. Some are detailed and credible. Others are generic, outdated, or written so vaguely that they offer little practical value.
That is why a VPAT should be treated as one piece of evidence, not the whole evaluation. You should review when it was created, which version of the product it covers, which standards it maps to, and whether the remarks are specific enough to identify actual support and limitations. If a VPAT says a criterion is “supports” without explanation across the board, that may warrant deeper scrutiny. If it identifies partial support with concrete notes, that often signals a more mature and trustworthy assessment process.
To make the evaluation meaningful, pair the VPAT with other validation methods. Ask targeted follow-up questions about critical workflows. Request a demo of accessibility features. Conduct your own testing on key tasks if feasible, especially for high-risk systems. Involve internal accessibility specialists, disabled users, or third-party experts where appropriate. Review support content, onboarding materials, templates, and admin interfaces too, because accessibility problems often extend beyond the core user interface.
The key point is that procurement teams should not confuse documentation with due diligence. A VPAT helps you ask better questions, but it does not replace verification, risk assessment, or contractual protections. If you rely on it alone, you may still end up purchasing a product with serious usability barriers that were never properly examined.
4. How should procurement teams handle vendors that have accessibility gaps but are willing to improve?
This is where thoughtful scoring and vendor management matter most. If a vendor has accessibility gaps, that does not always mean they must be excluded immediately. The right question is whether the gaps are acceptable in light of the product’s intended use, the impact on users, the availability of alternatives, and the vendor’s demonstrated willingness and ability to remediate. Procurement should be able to distinguish between manageable issues with a credible remediation path and systemic problems that create unacceptable risk.
Start by identifying the severity and location of the barriers. Are they concentrated in low-frequency administrative screens, or do they affect essential workflows such as login, navigation, checkout, data entry, or reporting? Are disabled users blocked entirely, or are there workarounds? Are the issues documented and acknowledged by the vendor, or are they being minimized? This analysis helps teams move beyond generic statements like “the product is not fully accessible” and toward a more defensible procurement decision.
If the vendor is otherwise the best fit, the next step is to formalize remediation expectations. Require a written accessibility roadmap with prioritized fixes, target dates, and named accountability. Include contract language covering remediation obligations, response times, updated conformance reporting, and consequences if commitments are not met. Depending on risk, you may also require periodic status reviews, retesting milestones, or executive approval before rollout. In some cases, a phased deployment may be appropriate, especially if accessibility defects must be resolved before broad implementation.
This approach protects the organization from two common failures: buying inaccessible products with no enforcement mechanism, and rejecting every vendor that is imperfect even when improvement is achievable. Accessibility procurement should create leverage, not deadlock. By documenting risk, securing commitments, and monitoring follow-through, teams can make realistic purchasing decisions that improve accessibility over time instead of merely documenting concern.
5. What role does vendor management play after an accessible procurement decision is made?
Vendor management is what turns accessibility procurement from a one-time exercise into an ongoing control. Many organizations do reasonable work during sourcing and then lose momentum after contract signature. That is a mistake because accessibility can degrade over time as products evolve, new features launch, integrations change, and implementation decisions introduce new barriers. If there is no post-award oversight, even strong procurement requirements may never show up in the delivered experience.
Effective vendor management begins by carrying procurement commitments into the contract and governance process. Accessibility obligations should not live only in evaluation notes or email threads. They should be reflected in statements of work, service terms, remediation commitments, documentation requirements, and review checkpoints. Vendors should know what they are expected to deliver, how progress will be measured, and when evidence must be updated. That may include revised VPATs, release notes that identify accessibility changes, periodic testing results, or meetings focused on unresolved issues.
It is also important to verify the real-world implementation of the product in your environment. Configuration choices, custom branding, templates, uploaded documents, and third-party plug-ins can all affect accessibility. In other words, a product that is reasonably accessible out of the box can still become inaccessible during deployment. Vendor management should therefore involve the internal teams responsible for implementation, content, design, security, and support, not just procurement alone.
Most importantly, vendor management creates accountability over time. If a supplier promised remediation during the selection process, someone needs to track whether those fixes were actually delivered. If regressions appear, there should be a clear escalation path. If renewals are being considered, the accessibility performance of the vendor should influence the decision. This is how organizations avoid the common pattern of buying on promises and living with barriers for years afterward. Procurement starts the accessibility conversation, but vendor management is what ensures the
