Minneapolis WCAG Requirements for Contractors

Minneapolis, Minnesota contractors who deliver digital products or services to the city must meet applicable web accessibility standards and procurement requirements. This guide explains how WCAG applies when contracting with Minneapolis, which city offices enforce accessibility obligations, typical enforcement outcomes, practical compliance steps, and where to find official forms and contacts. It summarizes common violations and concrete actions contractors should take before, during, and after contracting to reduce risk and speed approval of deliverables. Where specific penalties or fees are not published on the city pages referenced in the Resources section, this article notes that fact and is current as of February 2026.

Overview of WCAG and City Expectations

Many public-sector contracts require conformance to the Web Content Accessibility Guidelines (WCAG) at a specified level (commonly WCAG 2.1 AA). Contractors should expect accessibility clauses in solicitations, statements of work, and technical requirements. Compliance typically means design, development, testing, remediation, and documentation demonstrating conformance.

Penalties & Enforcement

Minneapolis enforces accessibility obligations through multiple city offices depending on the contract and service: procurement/purchasing, IT/technology services, civil rights or equity offices, and, for built environment work, planning and building inspections. Exact monetary fines or statutory penalty amounts for noncompliance with WCAG-specific clauses are not uniformly published on city procurement or IT accessibility pages; where amounts are not shown, they are noted below as "not specified on the cited page." This guidance is current as of February 2026.

• Enforcers: City procurement/purchasing, IT accessibility officers, Civil Rights/Equity departments, and contracting program managers.
• Monetary fines: not specified on the cited page.
• Escalation: first notice, formal correction period, and potential contract remedies or withholding of payments; specific ranges and schedules are not specified on the cited page.
• Non-monetary sanctions: stop-work orders, requirements to remediate at contractor expense, contract termination, corrective action plans, and referral to legal or administrative hearings.
• Complaint and inspection pathways: complaints routed to the city office named in the contract (procurement or IT) or to Civil Rights/Equity; contractors will be notified of inspections or accessibility reviews.
• Appeals and review: appeal routes typically follow contract dispute procedures or administrative review; exact time limits for appeals are not specified on the cited page.
• Common violations: inadequate keyboard access, missing alternative text, poor color contrast, inaccessible forms and PDFs, and lack of accessibility documentation; typical penalties depend on contract remedies and are not specified on the cited page.

Applications & Forms

Procurement and contract award processes generally use the city purchasing or vendor portal forms for bids and certifications. Specific accessibility certification forms or submission templates are not published on a single city page and are therefore noted as not specified on the cited page; contractors should follow solicitation instructions and request clarifications from the contracting officer listed in each solicitation.

Compliance Steps for Contractors

• Review contract terms: identify required WCAG level and deliverables, and include accessibility milestones in your project plan.
• Design and build to WCAG: adopt accessible design patterns, semantic HTML, ARIA only where needed, and accessible components.
• Test thoroughly: use automated tools, manual keyboard and screen reader testing, and include user testing with people with disabilities.
• Document conformance: provide an accessibility conformance report, test results, and remediation plans as deliverables.
• Remediate within deadlines: respond to city notices promptly and follow correction timelines provided by the contracting authority.

How-To

1. Identify the WCAG level required in the solicitation and include it in your internal project scope.
2. Integrate accessibility into design sprints and acceptance criteria.
3. Run automated scans and manual audits during development.
4. Prepare an accessibility conformance report and remediation schedule for submission with deliverables.
5. Respond to city accessibility reviews or complaints within the timeline provided by the contracting officer.
6. If enforcement action occurs, follow contract dispute and appeal procedures; seek clarification of appeal deadlines from the contracting office.

FAQ

Do contractors need to certify WCAG compliance to contract with Minneapolis?

Contract documents typically require evidence of conformance such as test reports and an accessibility conformance statement; check each solicitation for specific certification requirements.

What WCAG level does the city require?

WCAG level varies by solicitation; many public contracts request WCAG 2.1 AA, but contractors must verify the required level in the specific contract.

Who do I contact to report an accessibility issue with a city contract deliverable?

Contact the contracting officer listed in the solicitation and the city department responsible for the contract; for equity or civil-rights concerns, contact the city Civil Rights or Equity office as directed in the contract terms.

Key Takeaways

• Confirm WCAG requirements in each solicitation before bidding.
• Document testing and remediation and include them as deliverables.
• Use the contracting officer and city accessibility contacts for clarifications and appeals.

Help and Support / Resources

• City of Minneapolis main site - procurement and departmental contacts.
• Minneapolis Finance - Purchasing - purchasing and vendor instructions.
• City programs and initiatives - includes IT and accessibility program pages.
• City departments directory - contact Civil Rights/Equity or IT for enforcement questions.