Serious accessibility issues in Settings UI with screen readers on Windows 10

Windows Terminal version

1.24.10921.0

Windows build number

Windows 10 22H2 (OS Build 19045.5968)

Other Software

• NVDA (latest version at time of writing)
• Windows Narrator
• Windows 10 Accessibility features

Both screen readers reproduce the same accessibility and keyboard navigation problems inside the Settings UI.

Steps to reproduce

1. Open Windows Terminal.

2. Open Settings.

3. Go to any profile such as Command Prompt or PowerShell.

4. Navigate to editable controls such as:

   • Font face
   • Profile name
   • Command line
   • Starting directory

5. Enter one of the editable combo box controls using keyboard navigation.

6. Try navigating to the next control using Tab.

7. Try activating buttons such as "Browse...".

8. Try editing profile names or selecting fonts using only keyboard navigation and a screen reader.

Expected Behavior

• Keyboard focus should move normally using Tab and Shift+Tab.
• Editable combo boxes should follow standard accessibility behavior.
• Screen readers should correctly announce controls and states.
• Users should be able to leave edit fields normally.
• Buttons such as "Browse..." should be reachable by keyboard.
• Font selection and profile renaming should be fully accessible with screen readers.

Actual Behavior

• Focus sometimes becomes trapped inside editable fields.
• Tab does not always move to the next control.
• Some editable combo boxes and autocomplete edits are difficult or impossible to use.
• Font selection is not practically usable with screen readers.
• Editing profile names is unreliable.
• Several controls are not announced correctly or behave inconsistently with NVDA and Narrator.
• The Settings UI is difficult to navigate using keyboard-only accessibility workflows.