SWT Widgets ↔ Eclipse Workbench: What is the optimal strategy to expose ARIA labels for custom views?

SWT Widgets ↔ Eclipse Workbench: What is the optimal strategy to expose ARIA labels for custom views?

The Eclipse IDE offers high‑contrast themes and basic keyboard navigation, yet many custom views and dialogs lack explicit mnemonics or a logical tab order. Screen readers expose accessible names for standard SWT controls, but complex widgets such as the Outline view or Project Explorer often present unlabeled or ambiguous roles. The Eclipse Accessibility Framework (EAF) allows plug‑in developers to contribute ARIA‑like labels, yet adoption is uneven and there is no enforced policy for new contributions.

Given this landscape, an unresolved decision is whether future Eclipse releases should transition from the custom SWT accessibility layer to native OS accessibility APIs (e.g., Windows UI Automation, macOS AXAPI) to provide a consistent, standards‑compliant experience.

Key questions remain:

• Should Eclipse adopt native OS accessibility APIs for all future releases, and if so, how will backward compatibility be maintained?
• What enforcement mechanisms can the Eclipse Accessibility Framework implement to ensure that custom views expose proper ARIA labels?
• What policy should be defined for third‑party plug‑in developers to guarantee consistent accessibility support across the ecosystem?