Fort Wayne City Contracts: WCAG Compliance Guide

Technology and Data Indiana 3 Minutes Read ยท published February 09, 2026 Flag of Indiana

Fort Wayne, Indiana requires city vendors and departments to address digital accessibility when awarding and performing public contracts. This guide explains how to include Web Content Accessibility Guidelines (WCAG) requirements in solicitations, review vendor submissions, and manage ongoing compliance for websites, web apps, and digital documents used in municipal services. It covers roles, procurement language, testing expectations, reasonable accommodations, and next steps for contracting officers and bidders to reduce legal and operational risk. Current as of February 2026.

Start accessibility requirements early in the procurement process to avoid costly rework.

What WCAG means for city contracts

WCAG (currently WCAG 2.1 or later as adopted by a contracting authority) sets technical success criteria for perceivable, operable, understandable, and robust digital content. For Fort Wayne contracts this typically affects:

  • Procurement documents and solicitations (RFPs, RFQs) requiring accessible deliverables.
  • Development or maintenance services for city websites, public portals, and internal web apps.
  • Vendor deliverables such as PDFs, interactive forms, and documents provided to the public.

Contract language & practical clauses

Standard contract language should define the WCAG version, conformance level (e.g., 2.1 AA), testing expectations, remediation timelines, acceptance criteria, and reporting obligations. Include clear acceptance testing steps, remediation credits, and ongoing monitoring obligations for hosted services. Require vendors to provide test reports from recognized accessibility testing tools and a statement of compatibility with assistive technologies.

Define acceptance criteria in measurable terms, for example, "WCAG 2.1 AA, as tested by an independent auditor."

Suggested procurement clauses

  • Requirement: Deliverables must meet WCAG 2.1 AA or higher, with exceptions limited to documented third-party content.
  • Testing: Vendor must provide a remediation plan and test report from a recognized auditor before final acceptance.
  • Remediation timeline: Contractor must correct verified failures within a specified number of business days as set by the contract.

Penalties & Enforcement

Fort Wayne enforcers typically rely on contract remedies rather than separate bylaw fines for accessibility noncompliance. Specific monetary fines for WCAG violations are not routinely specified on the standard procurement pages; remedies are usually contractual (withhold payment, require remediation, or terminate) and civil enforcement may follow under federal or state accessibility laws. Departments responsible for enforcement are normally the Purchasing Division and the contracting department; see official contacts in Help and Support / Resources below. Current as of February 2026.

  • Fine amounts: not specified on the cited page.
  • Escalation: first remedy is typically remediation; repeat or continuing failures may lead to contract termination or withholding of payments.
  • Non-monetary sanctions: remediation orders, corrective action plans, suspension or termination of contract, and referral to legal counsel for further action.
  • Enforcer: City Purchasing Division and the contracting department manage compliance and inspections. Contact details appear in Help and Support / Resources below. [1]
  • Appeals/review: contract dispute procedures and administrative appeal timelines follow the contract terms; specific time limits are not specified on the cited page.
  • Defences/discretion: good-faith remediation efforts, documented third-party content, and approved variances can be relevant defenses.
If a contract lacks accessibility language, amend it before awarding or require a binding remediation schedule.

Applications & Forms

The procurement process typically uses vendor registration and solicitation response forms managed by the Purchasing Division; there is no single universal accessibility form published on the procurement overview page. For specific solicitations, include required accessibility deliverables and forms in the RFP package. Current as of February 2026.

Compliance testing and acceptance

Acceptance testing should combine automated scans, manual testing, and evaluation by assistive-technology users when feasible. Establish a staged acceptance: initial automated scan, manual remediation, and final auditor verification. Document testing tools and versions in the contract.

  • Automated testing: include required tools or test standards.
  • Manual testing: keyboard-only navigation, screen reader checks, and form labeling.
  • Ongoing monitoring: schedule periodic re-tests and require reporting to the contracting officer.

How-To

  1. Assess current digital assets for WCAG 2.1 AA gaps and document findings.
  2. Include measurable WCAG clauses, acceptance tests, and remediation timelines in the RFP or contract.
  3. Require vendor test reports and perform independent verification before final payment.
  4. Monitor post-deployment and enforce remediation obligations under contract terms.

FAQ

Do Fort Wayne contracts require WCAG compliance?
Many city solicitations require accessibility measures; include WCAG requirements expressly in the solicitation to make them enforceable.
Who to contact for accessibility questions in procurement?
Contact the City Purchasing Division or the contracting department listed in the solicitation for guidance and to report compliance issues.

Key Takeaways

  • Make WCAG requirements explicit in contracts to create enforceable remedies.
  • Combine automated and manual testing plus vendor remediation plans for acceptance.

Help and Support / Resources

Categories

General Governance and Administration Public Safety Public Health and Welfare Land Use and Zoning Housing and Building Standards Transportation Environmental Protection Parks and Public Spaces Business and Consumer Protection Taxation and Finance Labor and Employment Education Civil Rights and Equity Elections and Campaign Finance Events and Special Uses Signs and Advertising Utilities and Infrastructure Technology and Data