=== User Story
As a user using a screen reader, I want to be able to navigate the mobile web version of Special:Preferences and change my preferences.
=== Technical information
`TBD`
=== Testing and QA steps
- Use a screen reader (e.g. [[ https://help.gnome.org/users/orca/stable/index.html.en | Orca ]])
- Navigate to Special:Preferences via mobile web
- Attempt to navigate the form via keyboard, and select subsections
- Attempt to change and save a preference
=== Acceptance Criteria
[] Special:Preferences on mobile can be navigated via keyboard
[] Audible hints should be provided by screen readers when navigating the page with a screen reader running
[] It should be possible to browse and save preferences via keyboard with the assistance of a screen reader
=== Original ticket
**Steps to replicate the issue** (include links if applicable):
Everything here is done with a screen reader running (I used orca with structural navigation enabled)
To experience the current state of desktop preferences:
* load https://en.wikipedia.org/w/index.php?title=Special:Preferences&mobileaction=toggle_view_desktop and keep the cursor on the page title
* the reader will announce the loading progress of various page elements, beginning with top level nav
* after the reader says preferences in done loading, listen to the help and skin nav options, followed by keyboard navigation hints for the form
* use the keyboard to navigate the form
To experience the current state of mobile preferences:
* load https://en.m.wikipedia.org/w/index.php?title=Special:Preferences&mobileaction=toggle_view_mobile and keep the cursor on the page title
* after preferences loads, there are no additional nav choices (this could be okay since there are reduced tools on mobile), nor are there nav hints
* the section descriptions are announced as heading level 5 which is a surprising jump in structure
* use the keyboard to navigate the form
**What happens?**:
* you can change focus between the sections, but can't open them, the form is totally inoperable
**What should have happened instead?**:
* the form should be keyboard navigable and offer hints on how to navigate it via keyboard
* the form should present section descriptions as such, eg. using [[ https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-describedby | aria-describedby ]] or markup with similar functionality
**Software version** (skip for WMF-hosted wikis like Wikipedia):
**Other information** (browser name/version, screenshots, etc.):
Edge 108 with Orca 42.0