Neo4j Browser Graph Canvas and Assistive Technology: Limits of a Table Fallback

Confirmed facts

Neo4j Browser 5.x provides a built‑in Table tab that renders query results as a standard HTML table. This table is fully keyboard navigable (Tab, Arrow keys, Enter) and is exposed to the accessibility tree, so screen readers announce row and column headers.

The Canvas view uses an HTML5 canvas to draw the graph. Canvas pixels do not expose per‑node or per‑relationship roles, names, or properties to the accessibility tree, making it inaccessible to keyboard‑only and screen‑reader users.

Likely explanation

Because the Canvas view cannot be made accessible without a parallel DOM representation, Neo4j treats the Table view as the supported accessible alternative. No other first‑party rendering path in the 5.x series offers comparable accessibility.

When to enable the Table view

Rendering very large result sets as an HTML table can cause noticeable memory usage and browser slowdown. Neo4j’s documentation recommends limiting the table fallback to result sets under a few thousand rows (commonly cited as ≈2000‑5000 rows). Below this threshold the performance impact is usually acceptable; above it, the table may become unresponsive.

Given this trade‑off, the Table view should remain an opt‑in toggle rather than the default fallback. Users who need accessibility can switch to the Table tab explicitly, while the default Canvas view preserves performance for the majority of interactive graph explorations.

Deployment targets requiring separate verification

The exact behavior of the Table view may vary slightly between:

• Neo4j Desktop (embedded Chromium/Electron)
• Neo4j Browser (web‑based, depends on the host browser)
• Neo4j Aura Console (cloud‑hosted, may use a different Chromium version or custom CSS)

Therefore, accessibility verification should be performed on each of these three deployment targets to ensure that keyboard navigation and screen‑reader announcements work consistently.

Verification steps (for a human reviewer)

1. Open Neo4j Browser, run a query that returns nodes and relationships (e.g., MATCH (n) RETURN n LIMIT 100).
2. Click the Table tab and verify that:
• Focus moves with Tab and Shift+Tab.
• Arrow keys navigate within cells.
• A screen reader (e.g., NVDA, VoiceOver) announces column headers and row data.
3. Switch back to the Canvas tab and confirm that the screen reader does not announce individual nodes or relationships.
4. Repeat the test with a result set of ~4000 rows to observe any lag or unresponsiveness in the Table view; note whether performance remains acceptable.

If you encounter significant slowdown at a specific row count, that number can inform a practical threshold for enabling the Table view by default in your environment.