Interface accessibility

You should not need to use the map to use AccessPath.

Route planning should work through clear controls and readable directions, with the map as another way to inspect the same information.

Plan a route in words.

  1. Open the explorer and select a start and destination using the labeled fields.
  2. Choose a route mode and any additional preferences, then calculate.
  3. Read the route explanation, barrier and uncertainty summaries, and ordered itinerary.
  4. If no route qualifies, use the explicit alternative or change the destination. A map gesture is not required.

Keyboard and movement.

Use Tab and Shift+Tab to move between controls. Use Enter or Space to activate buttons and the arrow keys for native selection controls. The skip link goes directly to the main content. Essential tasks have alternatives to dragging or selecting small map points.

Visible focus identifies the active control. The interface respects your device’s reduced-motion setting and does not require an animation to explain a route result.

Walking and rolling, with your preferences.

The street planner offers wheelchair / mobility access preferences for mapped stairs, ramps, slopes, width, kerbs and reviewed obstacles. Missing access data remains visible. Local access-aware paths are not field-verified and can still contain unmapped barriers; use strict mapped-detail mode when unknown information does not meet your needs.

Opt-in live guidance provides a moving GPS position, next-step display, optional spoken prompts and controlled rerouting. Low-accuracy fixes pause automatic decisions. A device location permission is optional; every route can still be planned with manual coordinates and labeled fields.

Open access-aware planning

More than a colored line.

Route labels, line patterns, and written summaries distinguish route types and uncertain information. A blocked segment is identified in words. Forms use labels and feedback, and the layout is designed to reflow across desktop, tablet, and mobile screens.

What still needs human review.

No community usability study or formal assistive-technology audit has been completed. Campus data is synthetic; street routes use external map data with explicit limitations. The app’s purpose should not be mistaken for proof that a real pathway is accessible.

Explore routes Read the methodology