DataGrip Schema Explorer & Screen Readers: Is Database Metadata Fully Accessible?

Question

Schema Explorer Accessibility Gap
The goal is to determine whether DataGrip’s database view panels expose complete schema information—such as foreign‑key links, stored procedure signatures, and column types—to assistive technologies. Current documentation indicates that the IntelliJ Accessibility API is available, yet the Schema Explorer’s AccessibleContext implementation appears incomplete, leaving screen readers uncertain about node content.
Constraints include the lack of a documented API surface for database metadata within the accessibility layer and the absence of a quick shortcut to the Accessibility Settings dialog, making verification difficult for users relying on NVDA or VoiceOver.
Unresolved decision: Should database metadata be represented as fully navigable, screen‑reader‑friendly tree nodes?
Specific questions:

Does DataGrip expose foreign‑key relationships as navigable nodes for screen readers?
Are stored procedure signatures announced when navigating the schema tree?
What API changes are required to provide a complete AccessibleContext for database view panels?

Tasadduq Burney · Answer

Answer
DataGrip does not expose foreign‑key relationships as separate navigable nodes for screen readers, and stored‑procedure signatures are announced only as the procedure name and return type – the full parameter list (types and modes) is missing.
Confirmed facts

DataGrip inherits the IntelliJ platform accessibility API; basic tree nodes expose object names and types via AccessibleContext.
In the Schema Explorer, foreign‑key details appear only as tooltip text on the parent table node – no distinct child node is created.
Stored‑procedure nodes expose the procedure name and return type, but the full signature (parameter names, types, and IN/OUT modes) is not included in the accessible name or description.

Likely explanation
The Schema Explorer uses a custom JTree renderer that does not call AccessibleContext.setAccessibleName (or setAccessibleDescription) for foreign‑key child nodes or for procedure parameter nodes. Consequently, screen readers such as NVDA or VoiceOver announce only the table name and column list, or the procedure name and return type, leaving the relationship and signature information inaccessible.
Steps to verify and improve

Enable the IDE accessibility plugin (Help → Accessibility Settings) and ensure the screen reader is active.
Open DataGrip, connect to a database that contains known foreign keys and stored procedures.
Navigate the Schema Explorer tree with arrow keys while listening to the screen reader; note whether FK child nodes are announced and whether procedure parameters are spoken.
Use an accessibility inspection tool (e.g., Inspect.exe on Windows or the Accessibility Inspector on macOS) to examine the AccessibleContext of selected tree nodes; verify that the accessible name/description lacks FK details and full procedure signatures.
If the information is missing, file a feature request in JetBrains YouTrack describing the gaps and requesting that the IDE set appropriate accessible names/descriptions for FK child nodes and procedure parameter nodes, or implement a custom AccessibleObject that exposes these as navigable children.

Missing diagnostic detail
To tailor the recommendation, please confirm: What version of DataGrip and which JDK are you using? Accessibility behavior can vary between releases and JDK versions.

DataGrip Schema Explorer & Screen Readers: Is Database Metadata Fully Accessible?

Schema Explorer Accessibility Gap

1 answer

Answer

Confirmed facts

Likely explanation

Steps to verify and improve

Missing diagnostic detail

Your perspective belongs here.

0 question comments