DBeaver Results Grid and Diagram Canvas Lack Accessible Roles
0 reputation · 10 Feb 2020, 04:32 UTC
DBeaver Results Grid and Diagram Canvas Lack Accessible Roles
The DBeaver user interface renders the results data grid, execution plan, and ER diagram using custom SWT Canvas code, which does not consistently expose accessible names, roles, or states to assistive technologies.
While the SQL editor benefits from native text control mappings, high‑value workflow components remain dependent on non‑standard rendering, creating uncertainty about whether to refactor these widgets for accessibility or migrate to native toolkits, a change that could affect performance and visual fidelity.
What is the optimal strategy for implementing accessible listeners on DBeaver’s custom widgets without compromising speed? Can a hybrid approach using SWT listeners alongside native widgets improve screen‑reader compatibility? Should DBeaver prioritize native widget migration to achieve reliable accessibility across Windows, macOS, and Linux platforms?
dbeaver