Source-linked AI summary

MAP: A Benchmark on Multimodal Accessibility Planning for Real World Places

Jason Armitage, Ioannis Tsochantaridis, Linda Mazzone, Chuqiao Yan, Srini Narayanan, Sarah Ebling

arXiv:2608.28384v1cs.AI

TL;DR

Planning real-world visits can be difficult when accessibility information is incomplete or outdated, and the safety and usefulness of AI assistance remain unclear. MAP evaluates multimodal systems through claim-verification and visual-evidence tasks; its results show that search access increased “Useful and Safe” response counts for closed-weight systems.

  • Problem

    People with disabilities often encounter incomplete, dispersed, or outdated accessibility information when planning activities, while the safety and usefulness of AI assistance remain unclear.

    Source: §1 · p. 1
  • Method

    MAP benchmarks multimodal systems through claim verification against accessibility ground truth and visual-evidence retrieval for requested places and features, with ground truth updated for scheduled evaluations.

    Source: §3 · p. 3, §6 · p. 9
  • Results

    Across evaluations, performance varied: search raised GPT-5.2 “Useful and Safe” outputs from 17 to 141, while correct visual-evidence selection also varied by system and feature.

    Source: §4.1.1 · p. 7, §4.2 · p. 8
  • Takeaways & Limitations

    The evaluation can account for changing real-world information by updating ground truth and running assessments within specified windows.

    Source: §6 · p. 9

    Because MAP depends on public digital sources, coverage is uneven across accessibility features and source updates may lag changes in the physical world.

    Source: §5 · p. 8

Abstract

from arXiv · show

We introduce MAP, the first benchmark to evaluate multimodal AI systems as assistants for users with accessibility requirements when planning visits to places in the real world. In our evaluation, systems are presented with requests to verify or recommend a point of interest meeting an accessibility requirement. MAP contains two novel assessments: Claim verification for accessibility planning assesses if information on places and stated accessibility features is supported and identifies places that satisfy requested accessibility features. Visual evidence retrieval for accessibility planning checks if a multimodal AI system can select visual evidence for the requested place and accessibility feature. Our methodology supports comparison of AI systems in a setting where place information and accessibility information can change over time by evaluating systems and refreshing ground truth data at scheduled times. The benchmark is based on automatic rating and human rating for a proportion of responses.

1 INTRODUCTION

People with disabilities face barriers when planning real-world activities because relevant accessibility information can be incomplete, scattered across sources, or outdated. MAP evaluates whether multimodal AI can assist with accessibility-aware place planning and evidence retrieval.

1 INTRODUCTION

  • The paper uses “disability” in the ICF sense: an interaction between an individual’s impairment and restricted access to society.The introduction motivates MAP by noting that the safety and usefulness of multimodal AI assistance for real-world planning remain unclear.Source: §1 · p. 1
  • MAP evaluates multimodal AI assistants for accessibility-aware visits to real-world places, covering mobility, vision, hearing, and cognition requirements.Its assessments compare system responses with ground-truth accessibility-feature data, using automated evaluation and human checks.Source: §1 · p. 1
  • MAP introduces claim verification for accessibility-related place claims and visual evidence retrieval for images showing the requested place and feature area.The tasks assess response correctness and whether a model can find relevant visual evidence supporting an accessibility query.Source: §1 · p. 1, Figure 1 · p. 2
  • Its time-based ground truth integrates public place and accessibility sources, with agent construction, human review, provenance tracking, and conflict resolution.Refreshed ground truth and fixed scoring procedures support system comparisons as places and accessibility information change over time.Source: §1 · pp. 1–2

2 BACKGROUND

The background positions MAP against prior multimodal, accessibility, and evaluation research, emphasizing its focus on current, factual accessibility information for real-world places.

2.1 Benchmark Design

2.2 Assessing AI Systems on Accessibility

  • Prior accessibility studies focus on particular disability types and application domains, while MAP evaluates multiple disability types using updated real-world location information across diverse features.Examples include auditing built-environment mobility with Accessibility SCOUT (Huang et al., 2025), virtual navigation with StreetReaderAI, and micro-navigation queries for blind and low-vision users.Source: §2.2 · pp. 2–3

2.3 Evaluation Methods and Metrics

3 THE MAP BENCHMARK

MAP benchmarks multimodal AI assistants for accessibility-aware visits to real places through claim verification and visual evidence retrieval. It checks whether place and accessibility claims are supported by ground-truth data and whether selected images show the requested place and feature.

3 THE MAP BENCHMARK

  • MAP evaluates responses to structured prompts against ground-truth place and accessibility-feature information in two tasks: claim verification and visual evidence retrieval.Claim verification checks feature-check and search-by-feature responses; visual evidence retrieval tests selection of evidence for a requested place and accessibility feature.Source: §3 · p. 3

3.1 Structured Prompts

  • Prompts combine disability and accessibility requirements with feature-check, search-by-feature, or visual-evidence questions across Zurich places.Visual retrieval presents 20 candidate images, including a ground-truth image and controlled distractors, and checks both the correct POI and visibility of the requested feature. The three prompt sets cover 59 accessibility features, 257 place types, and 34 local areas.Source: §3.1 · pp. 3–4, Figure 2 · p. 4

3.2 Ground Truth Data

  • Ground truth represents a finite set of POIs with place attributes and accessibility features, assembled from place-information and accessibility-specific sources and reviewed by humans.Sources include Google Places, Ginto, official websites, targeted search results, user reviews, and POI images; the workflow aims to retain current, relevant information.Source: §3.2 · p. 4

3.2.1 Places

  • The first MAP iteration builds a Zurich POI reference list to cover relevant place types across target areas.Records are matched and merged into POI entries while retaining distinct visitor destinations within larger buildings.Source: §3.2.1 · p. 4

3.2.2 Accessibility Features

  • A single accessibility schema covers mobility, vision, hearing, and cognition, integrating evidence into field values such as booleans, text, measurements, or nulls.An agent weighs relevance, recency, source type, and agreement when reconciling evidence.Source: §3.2.2 · pp. 4–5

3.2.3 GT Construction and Updating

  • Human reviewers fill missing accessibility values by inspecting sources, and MAP refreshes ground-truth data shortly before scheduled evaluations.Provenance records retain source details, timestamps, reconciliation notes, and conflicting information for auditing field selections and investigating model errors.Source: §3.2.3 · p. 5

4 EVALUATION

MAP evaluates accessibility planning through claim verification and visual evidence retrieval, comparing system outputs with consolidated ground truth. Its scheduled evaluations and reruns after benchmark updates support tracking performance over time.

4.1 Claim Verification for Accessibility Planning

  • Claim verification pairs feature-check prompts for a named place with search-by-feature prompts to find qualifying places, assessing whether POIs and accessibility claims match ground-truth evidence.Full runs use automatic rating, with human assessment checking a proportion of responses.Source: §4.1 · p. 5, §4 · p. 5

4.1.1 Auto-rating

  • Unverified was the dominant label; search increased Safe counts for several closed-weight systems but also increased Contradictory labels for most, while open-weight systems remained mostly Unverified.Retrieved evidence more often elicited cautious rather than Safe responses from open-weight systems.Source: §4.1.1 · p. 7
  • With search, GPT-5.2’s Useful and Safe responses rose from 17 to 141, while search also increased Useful but Potentially Unsafe outputs.Gemini 3.1 Pro Preview had over 200 Useful and Safe responses with search; despite these gains, cautious and Not Useful responses remained prevalent.Source: Table 2 · p. 6, §4.1.1 · p. 7

4.1.2 Human Assessment

  • Two humans’ assessments aligned with auto-rating for GPT-5.2, Claude Sonnet 4.6, Claude Sonnet 5, Gemini 3.6 Flash, and open-weights models; widest label-allocation gaps involved Grok 4.3 and Grok 4.5.The claim-verification scoring comparison used n=30. Scoring challenges included unprompted features, contradictions, and insufficient specificity.Source: §4.1.2 · pp. 7–8

4.2 Visual Evidence Retrieval for Accessibility Planning

  • Visual retrieval asks systems to select an image or None for a specified place, feature, and visitor need, scoring whether the image shows the correct place and relevant physical area.A 0–1 score reflects place correctness and feature-area visibility; high scores indicate the correct place with the relevant area in focus.Source: §4.2 · p. 8
  • More than two thirds of cases yielded Correct Visual Evidence for Gemini 3.6, Gemini 3.1 Pro Preview, GPT-5.6 Terra, and Claude Sonnet 4.6.Across 300 test prompts without search, responses also showed two common error patterns: selecting None or choosing images of the right feature area at the wrong place; results varied by feature.Source: §4.2 · p. 8, Table 4 · p. 8

5 LIMITATIONS

MAP’s limitations stem from uneven and potentially outdated digital ground truth, constrained prompts and feature coverage, and evaluation in Zurich alone. Its findings therefore do not directly establish accessibility-planning performance across regions or all real-world requests.

5 LIMITATIONS

  • Digital ground truth overrepresents visible physical-access features, while sources may lag behind changes to venues and visitor support.MAP refreshes ground truth before scheduled evaluation runs, but remains dependent on source timeliness and coverage.Source: §5 · p. 8
  • MAP prompts use American English and may retain synthetic wording unlike the shorter, underspecified, or error-prone requests people use in practice.The prompt sets may not reflect regional, cultural, or multilingual language use.Source: §5 · p. 9
  • MAP covers only features specified in its schema and assessable for scoring, excluding possible out-of-scope, temporary, or journey-level access requirements.Journey-level requirements concern the route from a source to a destination.Source: §5 · p. 9
  • The first MAP iteration and its ground truth are limited to Zurich, so results are evidence for that city rather than a direct measure across regions.Source: §5 · p. 9

6 CONCLUSION

MAP evaluates multimodal AI systems as assistants for accessibility planning when visiting real places. It introduces two assessment tasks and supports open-world evaluation as information changes over time.

6 CONCLUSION

  • MAP assesses multimodal AI systems as assistants for users with accessibility requirements when planning visits to real places.Source: §6 · p. 9
  • Its two novel tasks assess factual accuracy in system responses and whether presented visual evidence is relevant to the user’s request.Source: §6 · p. 9
  • The benchmark supports open-world evaluation by updating ground-truth data and running assessments within specified time windows.Source: §6 · p. 9

Appendices · 1 QUESTION TYPES AND SYSTEM PROMPTS

The appendix describes how user-facing question prompts and standardized system prompts structure MAP evaluations. It points to examples of question types and system prompts used for evaluation runs.

1 QUESTION TYPES AND SYSTEM PROMPTS

  • At inference, task prompts are served as user requests to align evaluation with how human users query systems.Source: §1 · p. 11
  • The appendix distinguishes task prompts, presented as user requests, from system prompts, supplied separately to guide responses.Source: §1 · p. 11
  • A separate system prompt instructs models to produce outputs suitable for evaluation.Source: §1 · p. 11
  • System prompts are concise and standardized across the evaluated models.Source: §1 · p. 11
  • Table 5 presents sample prompts for each question type in claim verification and visual evidence retrieval.The table lists elements that make up the task prompts.Source: Table 5 · p. 11, §1 · p. 11
  • Table 6 lists the system prompts used for evaluation runs by question type.Source: Table 6 · p. 11

2 ADDITIONAL RESULTS

This section presents validation-partition results for claim verification and visual evidence retrieval.

  • Validation-partition results for the three question types across claim verification and visual evidence retrieval appear in Tables 7–9.Source: §2 · p. 11

3 HUMAN ASSESSMENTS

Human assessment highlighted cases where extra claims, ambiguous feature wording, or multiple feature statements complicate response scoring. The examples show how the final label can change when a response includes unsupported or conflicting information.

Human Assessments

  • A response that correctly addresses the requested feature can become “Contradictory” when it adds a conflicting claim about a wheelchair-accessible entrance.This case illustrates how an additional claim can change the overall score despite a correct answer to the requested feature.Source: §3 · p. 11
  • For wheelchair-accessible seating, the broad phrase “wheelchair accessible” is ambiguous because it does not specify seating rather than another feature.The assessed subset contained this response type only for wheelchair-accessible seating.Source: §3 · p. 11
  • Auto-rater validation results cover 300 feature-check questions and 200 search-by-feature prompts in the claim-verification task.The search-prompt table reports counts for labels in the Verified/supported framework, including Useful and Safe, Safe but Uninformative, and Not useful.Source: Table 7 · p. 12, Table 8 · p. 12
  • A response with correct restroom and seating claims can be labeled “Unverified” if it also claims parking that is absent from the ground-truth data.When “Safe”, “Unverified”, and “Contradictory” labels all apply, the final label is “Contradictory”, reflecting the potential consequences of incorrect information.Source: §3 · p. 12

4 SPECIFICATIONS FOR EVALUATION RUNS

Evaluation runs use single, stateless prompts and specify distinct scoring procedures for claim verification and visual evidence retrieval. The section also documents inference settings, model serving, and compute requirements.

4 SPECIFICATIONS FOR EVALUATION RUNS

  • Reported results use a single run, with prompts processed independently and without prior-prompt context.Claim verification is auto-rated against ground-truth values and provenance context.Source: §4 · p. 12
  • Supported inference settings use temperature 0 and low reasoning; open-weight models run through Ollama on a Google Cloud VM with one 24 GB NVIDIA L4 GPU.Tools are disabled during inference, Qwen2.5-VL-32B-Instruct has a 500-token generation limit, and search conditions use current data from the Brave Search API.Source: §4 · pp. 12–13
  • Claim verification uses Gemini 3.1 Pro Preview to map response claims to MAP fields and compare them with ground truth and evidence; visual retrieval scoring is deterministic.Claim assessment considers the full response, including unrequested accessibility features, while visual prompts contain 20 candidate images with a ground-truth sample and controlled distractors; Table 9 validation uses 100 prompts without search.Source: §4 · pp. 12–13, Table 9 · p. 13
Loading 2608.28384v1…