Brief summary
In web documents it is impossible to enter the focus /forms / application mode by pressing enter when the focused element is a div with the role of a combobox which in turn nests a further div that contains an input element. Nothing happens upon attempting it. The same is true for trying to exit back in to browse mode when such a control has been entered by tabbing into it, creating a potential keyboard trap or at best a situation where it is difficult to continue exploring the site without advanced knowledge on NVDA's features such as NVDA+ctrl+Space to leave any nested control back into the main document.
Steps to reproduce
- Open the following minimal Codepen example in either Firefox or Chrome:
https://codepen.io/editor/Masarczyk_Wienfluss/pen/019fd211-3286-7243-b7f5-6ee493579b81
- Navigate to the preview and locate the only element, a combobox labelled "test".
- Try to enter the combobox by pressing Enter thereby activating the focus mode
- Once that fails, try to reach the edit field within by pressing Tab;
- Once that succeeds, try to exit the focus mode using the Esc key or the NVDA+Space combination
Actual behavior
On steps 3 and 5 nothing happens. There is no reaction from NVDA's side. The focus mode cannot be entered or left.
Expected behavior
Entering and exiting focus mode works as expected.
NVDA logs, crash dumps and other attachments
NVDA_Log_2026-08-05.txt
NVDA type
installed copy
NVDA version
2026.2 beta 9
Have you tried any other versions of NVDA? If so, please report their behaviors.
Same on an older beta of 2026.2
Windows version
Windows 11 25H2 Build 26200.8875
Name and version of other software in use when reproducing the issue
Firefox V. 153.0.1,
Google Chrome V. Version 151.0.7922.72
Other information about your system
No response
Does the issue still occur after restarting your computer?
I have restarted my computer and the issue still occurs
If NVDA add-ons are disabled, is your problem still occurring?
I have restarted NVDA with add-ons disabled and the issue still occurs
Does the issue still occur after you run the System Accessibility Repair Tool (COM Registration Fixing Tool in older versions) in NVDA's tools menu?
I have run the System Accessibility Repair Tool and the issue still occurs
Brief summary
In web documents it is impossible to enter the focus /forms / application mode by pressing enter when the focused element is a div with the role of a combobox which in turn nests a further div that contains an input element. Nothing happens upon attempting it. The same is true for trying to exit back in to browse mode when such a control has been entered by tabbing into it, creating a potential keyboard trap or at best a situation where it is difficult to continue exploring the site without advanced knowledge on NVDA's features such as NVDA+ctrl+Space to leave any nested control back into the main document.
Steps to reproduce
https://codepen.io/editor/Masarczyk_Wienfluss/pen/019fd211-3286-7243-b7f5-6ee493579b81
Actual behavior
On steps 3 and 5 nothing happens. There is no reaction from NVDA's side. The focus mode cannot be entered or left.
Expected behavior
Entering and exiting focus mode works as expected.
NVDA logs, crash dumps and other attachments
NVDA_Log_2026-08-05.txt
NVDA type
installed copy
NVDA version
2026.2 beta 9
Have you tried any other versions of NVDA? If so, please report their behaviors.
Same on an older beta of 2026.2
Windows version
Windows 11 25H2 Build 26200.8875
Name and version of other software in use when reproducing the issue
Firefox V. 153.0.1,
Google Chrome V. Version 151.0.7922.72
Other information about your system
No response
Does the issue still occur after restarting your computer?
I have restarted my computer and the issue still occurs
If NVDA add-ons are disabled, is your problem still occurring?
I have restarted NVDA with add-ons disabled and the issue still occurs
Does the issue still occur after you run the System Accessibility Repair Tool (COM Registration Fixing Tool in older versions) in NVDA's tools menu?
I have run the System Accessibility Repair Tool and the issue still occurs