NetBeans Quick Fix popup focus management for screen readers

Direct Answer

There is no dedicated NetBeans preference that guarantees focus will return to the exact editor line after a Quick‑Fix popup is dismissed. Focus restoration is handled internally by NetBeans’ Swing focus manager and the Java Access Bridge, and the result depends on the JDK, OS, and screen‑reader combination you’re using.

Likely Explanation

• When a Quick‑Fix popup appears, it temporarily steals the keyboard focus from the editor.
• Upon dismissal, the Swing focus manager attempts to give focus back to the component that had it before, but the Java Access Bridge may not propagate the focus change promptly to the screen reader.
• Gutter icons that indicate syntax errors are visual decorations; they do not emit separate accessibility events. The screen reader will only announce them if it receives a property‑change event from the editor or if the user navigates to the line via an error‑navigation command.

Practical Steps for Your Setup

1. Verify Java Access Bridge is enabled:

   java -Djava.accessibility.forceAccessBridge=true -jar netbeans.jar

   On Windows, ensure the Access Bridge service is running. On macOS/Linux, the bridge is typically bundled with the JDK.

2. Test focus after Quick‑Fix dismissal:
   • Open a source file, place the caret on a line with a syntax error.
   • Invoke the Quick‑Fix via Ctrl+Space (or the context‑menu key).
   • Choose a fix and dismiss the popup with Esc or Enter.
   • Listen to the screen reader. If focus does not return, note which UI element receives focus instead.
3. Work‑around if focus is lost:
   • Use the Navigate → Go to Last Edit Location command (Ctrl+Shift+L by default) to return to the caret position.
   • Alternatively, open the Problems window, double‑click the error, and the editor will jump to the offending line.
4. Verify gutter icon announcements:
   • After dismissing the popup, move the caret to the line with the syntax error.
   • The screen reader should announce the line number and, if it supports the JDK’s accessibility events, the error description.
   • If no announcement occurs, the gutter icon is not being exposed as an accessible object; you can use the Problems window or error navigation commands instead.

What to Do Next

If you consistently experience focus loss, consider filing a bug with the NetBeans issue tracker and include:

• NetBeans version
• JDK version and whether the Java Access Bridge is enabled
• Operating system and screen‑reader version
• Steps to reproduce the focus loss

Ask for Missing Diagnostic Detail

Could you share the specific NetBeans release, JDK/Java Access Bridge version, OS, and screen‑reader you are using? Those details will help narrow down whether the issue is a known incompatibility or a configuration problem.