From the Citizen Engagement & Services edition of November 7, 2026
Minneapolis 311's new MARS portal went live with known screen-reader and contrast issues; full WCAG AA review not due until April 2027, disability committee tells city what to fix
City of Minneapolis 311 / Minneapolis Advisory Committee on People with Disabilities · Municipal 311 portal accessibility · Minneapolis, Minnesota, United States
- Publisher
- Muyni (automated coverage generated from public meeting minutes)
- Original publication
- 2026-11-03 (covers Oct. 21, 2026 meeting)
- Source retrieved
- 2026-11-08
- Event date
- 2026-10-21
What happened
At the Oct. 21, 2026 Minneapolis Advisory Committee on People with Disabilities (MACOPD) meeting, 311 staff and vendor Catalyst Consulting said the Minneapolis Agent Reporting System (MARS) CRM project, planned as a two-year transition, had to be completed in eight months and went live with known screen-reader glitches and at least one contrast issue; a Phase B walk-through for full AA compliance is expected by April 2027. MARS expands online request types from 18 to 126 and includes a chatbot labeled as a bot that works in English and Spanish (the minutes say it will expand as Salesforce expands language functionality), plus interpreter-preference settings. Committee members found the sandbox mostly keyboard-navigable and a major improvement, but asked for 911-versus-311 guidance, an accessibility menu, a chatbot-specific privacy statement, and an accessibility-bug contact that does not require filing a 311 ticket. A member also reported an invalid case link in a confirmation reply, since corrected.
Why it matters
Why now: Minneapolis publicly launched this portal and its mobile app on Nov. 5, 2026, so the Oct. 21 staff admission that accessibility conformance lags go-live is newly relevant. It shows an AI-assisted 311 front door shipping before WCAG AA review, with a disability committee defining fixes.
Evidence and measured results
Automated Muyni article generated from the official MACOPD meeting record; the minutes text is mirrored on Muyni's meeting page (inspected). The official city LIMS PDF returned HTTP 403 and was not bypassed.
Limitations and uncertainty
Secondary automated summary of minutes; staff self-report of issues; no WCAG audit results, defect counts or chatbot accuracy data. English/Spanish chatbot limit is from the minutes.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-07; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- A newly launched 311 portal and chatbot has known screen-reader and contrast defects, with full AA review months away.
- Stakeholders
- 311 Service Center
- MACOPD
- Vendor Catalyst Consulting
- Residents using assistive technology
- Discovery questions
- Which accessibility defects are logged and prioritized?
- Who tests chatbot and map with screen readers?
- How can residents report barriers without a 311 ticket?
- Value hypothesis
- Targeted assistive-technology testing could close known defects before April 2027; benefit depends on city prioritization.
- Potential engagement
- An assistive-technology test sprint on core request, chatbot and map flows feeding Phase B.
- Unsupported claims
- That MARS is WCAG AA compliant
- That the chatbot serves non-English/Spanish speakers
- Any resident satisfaction gain
Pre-sales engineering
Role takeaway
- Fit
- Fits cities with new CRM-based portals and embedded chat that launched ahead of accessibility review.
- Architecture and integration
- Salesforce-based CRM, public portal, knowledge-base chatbot, case map with confidentiality filters and account preferences.
- Prerequisites
- Accessibility defect backlog
- Screen-reader test scripts
- Disability-community test group
- Constraints
- Chatbot languages limited to English and Spanish
- Phase B timeline to April 2027
- Vendor-dependent language expansion
- Security
- Publish chatbot-specific privacy terms and confirm map filters withhold confidential case types.
- Proof of value
- Screen-reader pass on submit-a-request flow
- Contrast defects closed
- Accessible bug-report channel live
Delivery
Role takeaway
- Work
- Run Phase B accessibility walk-through and committee-requested changes on the live portal.
- Dependencies
- Catalyst Consulting
- Salesforce language features
- MACOPD volunteers
- Ownership
- Minneapolis 311 Service Center with MACOPD advisory input.
- Skills and adoption
- Plain-language screenshot guide and transcript training video, already in progress per staff.
- Governance checkpoints
- Committee review of Phase B fixes
- Accessibility statement and menu published
- Privacy statement covering chatbot
- Acceptance criteria
- Core flows meet WCAG 2.1 AA by April 2027
- Known screen-reader defects closed and retested
- Bug channel response time tracked
- Risks
- Residents excluded until fixes land
- Compressed timelines repeat
- Chatbot language gaps persist
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Salesforce-based 311 CRM with public portal, global search, chatbot drawing on knowledge base and partner sites, public case map with confidentiality filters, signed-in tracking and language/interpreter preferences.
Governance
Who approves, reviews and stays accountable for outcomes?
Disability advisory committee review before and after go-live; compressed eight-month timeline traded accessibility completeness for launch date; Phase B review gate set for April 2027.
Security and privacy
What data, permissions and controls need testing?
Committee asked for a general and chatbot-specific privacy statement and highlighted map privacy; certain case types are withheld from the public map for confidentiality.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Known screen-reader and contrast defects at launch; committee requests accessible bug-report channel, plain-language guide and transcript training video; LIMS meeting-calendar accessibility also failed for the chair.
Procurement
What should contracts, pricing and exit terms secure?
Vendor (Catalyst Consulting) delivered on a compressed timeline; accessibility acceptance deferred to Phase B rather than gating go-live.
Operating model
Which teams own the service once it runs?
Phase B backlog includes accessibility walk-through, batch submission, expanded translation and more granular case statuses; committee offers a volunteer focus group.
Publication history
Read preserved resource versions (JSON)Stable resource ID: minneapolis-311-mars-known-accessibility-gaps-macopd-20261021