Skip to content

[$250] Keyboard Navigation: Track Distance: Map start/stop points cannot be reordered by using a keyboard #74764

@nbhardwaj-del

Description

@nbhardwaj-del

Action Performed

Prerequisites:

  • the user is signed in.
  • The start and stop points has been selected on the track distance page.
  1. Using Chrome, open the URL - https://new.expensify.com/
  2. Navigate to the "+" icon and press Enter
  3. Tab to the "Track distance' menu item and press Enter to open the Pop-up
  4. Navigate and select 'Start' map points and select any address for the start point.
  5. Navigate and select 'Stop' map points and select any address for the start point.
  6. Try and observe to reorder the points using the keyboard (Tab, arrow keys, Enter, or Space).

Expected Result

Users must be able to reorder the 'start/stop' points on the map using only the keyboard. A keyboard accessible control (such as dedicated Up and Down arrow buttons next to each waypoint) should allow the user to change the position of a selected waypoint in the route list.

Actual Result

The 'start/stop' points on the Map can be reordered only via mouse drag-and-drop. When navigating with the keyboard, the user can focus the points, but no keyboard controls are provided to change or activate their order. The reordering function is not available for the keyboard users and remains exclusively available for mouse users only.

HTML:

Start
y9jx r-
(...)

Area issue was found

Track Distance

Failed Checkpoint

WCAG 2.1.1 Keyboard
https://www.w3.org/WAI/WCAG22/Understanding/keyboard

User Impact

People who are blind cannot use pointing devices like a mouse that require eye-hand coordination. People with low vision may have trouble finding or tracking a pointer indicator on screen. Some people with hand tremors find using a mouse very difficult and therefore usually use a keyboard.

Suggested Resolution

Provide accessible keyboard controls (e.g., “Move up / Move down” buttons) for each point, or implement keyboard drag-and-drop functionality using ARIA best practices. Ensure controls are focusable and announced properly by screen readers.
https://community.articulate.com/discussions/discuss/keyboard-accessible-drag--drop-example/1072955/replies/1072993

Environment(s)

Windows Windows 11 Home - Chrome

Image

**Version Number: NA
Reproducible in staging?: NA
Reproducible in production?: Yes
Email or phone of affected tester (no customers): NA
Logs: https://stackoverflow.com/c/expensify/questions/4856 NA
Notes/Photos/Videos: Any additional supporting documentation - Yes
Expensify/Expensify Issue URL: https://platform.applause.com/company/12102/products/36605/community-issues/6996762
Issue reported by: NA
Slack conversation: NA

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~022009685666729799188
  • Upwork Job ID: 2009685666729799188
  • Last Price Increase: 2026-01-28
Issue OwnerCurrent Issue Owner: @TaduJR

Metadata

Metadata

Labels

AccessibilityIssues affecting WACG accessibility on any platform.Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.ExternalAdded to denote the issue can be worked on by a contributorWeeklyKSv2

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions