{"resourceId":"minneapolis-311-mars-known-accessibility-gaps-macopd-20261021","versions":[{"version":"external-ae26d19f5f894fa99143258810f267f3ab85245f7f5f6fa06273fcd6e3065c44","resource":{"id":"minneapolis-311-mars-known-accessibility-gaps-macopd-20261021","title":"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","organization":"City of Minneapolis 311 / Minneapolis Advisory Committee on People with Disabilities","sector":"Municipal 311 portal accessibility","geography":"Minneapolis, Minnesota, United States","publishedAt":"2026-11-03 (covers Oct. 21, 2026 meeting)","publicationDate":"2026-11-03","eventDate":"2026-10-21","sourceName":"Muyni (automated coverage generated from public meeting minutes)","sourceLabel":"Minneapolis 311's new MARS portal launched with known accessibility problems, city tells disability committee","sourceUrl":"https://www.muyni.com/municipalities/minneapolis-mn/articles/minneapolis-311-s-new-mars-portal-launched-with-known-accessibility-problems-cit-20261021","evidenceClass":"independent-reporting","outcomeClass":"mixed","topics":["accessibility-workforce","operating-model","governance-procurement"],"finding":"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.","sledRelevance":"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":"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.","architectureImplications":"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.","governanceImplications":"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.","securityPrivacyImplications":"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.","caveats":"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.","streamIds":["citizen-engagement"],"roles":{"sales":"Sales framing: launching a resident portal before accessibility conformance creates exactly the gap an assessment can close. Minneapolis staff told the disability committee that MARS went live after an eight-month rush with known screen-reader and contrast problems and that AA review waits until April 2027. Discovery should ask which defects are logged, who tests with assistive technology, and how residents report barriers. A bounded engagement is an assistive-technology test sprint before Phase B. Do not claim the portal or chatbot is compliant.","engineering":"Engineering framing: the Salesforce-based MARS portal combines a knowledge-base chatbot in English and Spanish, global search, a public case map and signed-in tracking. Integration must preserve screen-reader semantics in dynamic chat and map components, contrast, and keyboard paths. Prerequisites are a defect backlog and assistive-technology test scripts. Constraints include the vendor's language support and an April 2027 Phase B date. Proof of value is closed accessibility defects and tested chatbot and map flows, not feature counts.","delivery":"Delivery framing: Phase B must turn committee feedback into tracked, verified fixes. Minneapolis 311 owns the backlog with Catalyst Consulting, while MACOPD offers a volunteer focus group for testing. Acceptance criteria below are proposals: AA conformance on core request flows, an accessibility-bug channel outside the 311 ticket system, and chatbot and map privacy statements. Keep phone, text and in-person channels prominent until accessibility defects close, and report progress back to the committee."},"roleDetails":{"sales":{"customerProblem":"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"],"discoveryQuestions":["Which accessibility defects are logged and prioritized?","Who tests chatbot and map with screen readers?","How can residents report barriers without a 311 ticket?"],"valueHypothesis":"Targeted assistive-technology testing could close known defects before April 2027; benefit depends on city prioritization.","potentialEngagement":"An assistive-technology test sprint on core request, chatbot and map flows feeding Phase B.","unsupportedClaims":["That MARS is WCAG AA compliant","That the chatbot serves non-English/Spanish speakers","Any resident satisfaction gain"]},"engineering":{"fit":"Fits cities with new CRM-based portals and embedded chat that launched ahead of accessibility review.","architectureIntegration":"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.","proofOfValue":["Screen-reader pass on submit-a-request flow","Contrast defects closed","Accessible bug-report channel live"]},"delivery":{"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.","skillsAdoption":"Plain-language screenshot guide and transcript training video, already in progress per staff.","governanceCheckpoints":["Committee review of Phase B fixes","Accessibility statement and menu published","Privacy statement covering chatbot"],"acceptanceCriteria":["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"]}},"retrievedAt":"2026-11-07T22:12:05-06:00","enrichedAt":"2026-11-07T22:18:01-06:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"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.","procurementImplications":"Vendor (Catalyst Consulting) delivered on a compressed timeline; accessibility acceptance deferred to Phase B rather than gating go-live.","operatingModelImplications":"Phase B backlog includes accessibility walk-through, batch submission, expanded translation and more granular case statuses; committee offers a volunteer focus group.","sourceVerification":{"openedUrl":"https://www.muyni.com/municipalities/minneapolis-mn/articles/minneapolis-311-s-new-mars-portal-launched-with-known-accessibility-problems-cit-20261021","referenceExcerpt":"a full accessibility review will not be finished until April 2027","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}