For blind and low-vision (BLV) screen-reader users, a website that appears accessible in a static snapshot can become difficult or impossible to navigate once interaction begins. Yet, most automated accessibility checkers miss failures involving focus, interface state, and accessible feedback across interactions. We present A11yLTLNav, a property-based approach for automatically detecting accessibility navigation failures. Through a structured review of prior research, we organize accessibility navigation failures into a failure taxonomy and formalize a browser-observable subset as executable Linear Temporal Logic properties over action-state traces. A11yLTLNav combines random keyboard exploration with runtime property monitoring to detect these failures during interactions. We evaluate A11yLTLNav on 31 generated websites based on real-world websites and tasks. It reported 309 accessibility failures, of which 274 were confirmed, achieving 88.7% precision and identifying more confirmed failures than the comparison checkers. Our results show that A11yLTLNav transforms accessibility knowledge into reusable checks of interface behavior over time.
Abstract
Video
Method
A11yLTLNav combines keyboard exploration, accessibility-state extraction, and runtime monitoring of temporal properties. Each reported violation records the triggering action and the observed state.
Example property: opening a dialog should move keyboard focus inside.
Temporal properties
G means “every time”; X means “in the next checked state”; d is the dialog. The checker observes the relevant state after the interaction settles.
Linear Temporal Logic (LTL) expresses rules about action sequences. Random testing tries varied sequences of available keyboard actions against those fixed rules. Each failure report records the interaction and resulting state.
Exploration does not guarantee that every failure will be found. Read the method.
Demos
Checker replay
00:03 · Focus stays outside. 01:47 · Escape does not close the player.
Full replay · Evidence & checker output
Focus restoration
Full recording
All four annotated states
Text-editor navigation
An exit-path check needs more than one Tab press.
Evaluation
| Checker | Reported | Confirmed errors | False positives | Precision |
|---|---|---|---|---|
| AxeStatic | 18 | 17 | 1 | 94.4% |
| WAVEStatic | 68 | 34 | 34 | 50.0% |
| Adapted TaskAuditAgentic | 276 | 158 | 118 | 57.2% |
| A11yLTLNavRun 1 | 309 | 274 | 35 | 88.7% |
Confirmed errors were verified by human reviewers. Static checkers scanned the first page only; counts include findings relevant to blind and low-vision users. Paper · Table 4



