Missing accessibility notifications in Neo4j Browser result pane

Implementing Accessibility Notifications in Neo4j Browser

The Neo4j Browser architecture, being a web-based frontend, fully supports the implementation of ARIA live regions. Because the result pane is updated dynamically via JavaScript, adding the appropriate semantic attributes to the DOM allows assistive technologies to detect and announce state changes without requiring a manual focus shift.

Recommended Implementation Pattern

To notify screen reader users of query completion without disrupting the input focus in the Cypher editor, the most effective pattern is the use of a hidden live region. Rather than marking the entire result table as live—which could trigger the screen reader to attempt to read the entire dataset—a dedicated status element should be used.

• Use role="status": This provides a semantic equivalent to aria-live="polite". It ensures the notification is announced at the next available opportunity, preventing the interruption of the user's current typing or navigation.
• Avoid role="alert" or aria-live="assertive": These attributes are intended for critical errors and will immediately interrupt the user, which is disruptive during standard query execution.
• Provide a Summary String: Instead of updating the result container directly, update the text content of the hidden status element with a concise summary (e.g., "Query complete, 15 nodes returned").

Technical Verification

To verify the current state or test a proposed fix in versions up to 4.3, use the following steps:

1. Open Browser Developer Tools (F12) and inspect the result pane container.
2. Search for the presence of aria-live or role="status" attributes.
3. Using a screen reader (such as NVDA or VoiceOver), execute a Cypher query and confirm that the completion status is announced while the cursor remains active in the input field.

Assumptions and Constraints

This recommendation assumes a standard web-browser environment. It is important to note that screen reader behavior can vary between software (e.g., JAWS vs. NVDA); therefore, testing across multiple assistive technologies is required for full WCAG compliance. We assume the goal is to maintain the user's workflow in the editor while providing asynchronous feedback.

Diagnostic Detail Needed: Are you implementing this as a custom browser extension/overlay, or are you contributing a patch to the Neo4j Browser source code? The implementation method for injecting these attributes differs significantly between the two.