id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc	focuses
65746	Prevent unnecessary announcements for screen readers in the various themes and media browsers	afercia	afercia	"WordPress uses some modal dialogs to display collections of Themes and Media. The code name for these tools is 'browsers', as they allow to browse (navigate) the related collections.

#63760 / https://github.com/WordPress/wordpress-develop/pull/11560 introduces some improvements for screen readers announcements related to the currently displayed Theme or Media.

There's still room for improvements. Basically, in these places in the admin:

Installed themes:
/wp-admin/themes.php

Theme installer:
/wp-admin/theme-install.php?browse=popular

Customizer theme preview (click the 'Change' button and then previwe the themes):
/wp-admin/customize.php?return=%2Fwp-admin%2Fthemes.php

Media grid:
/wp-admin/upload.php


from a user persepctive, the pattern for browsing the collections is similar.

- A modal dialog opens showing a Theme or Media details.
- Users can navigate to the next or previous item by clicking the Next and Previous buttons or by using keyboard shortcuts.
- For screen readers, the currently displayed item name is announced.

I'd like to propose to improve a couple things:

1
Make sure the navigation mechanism is consistent across all these UIs. For example, there are subtle differences about where focus is placed after navigating to another item, which also impacts announcements for screen readers.

2
When navigating to another item, focus is placed (or it is supposed to be) on the most appropriate Next or Previous button. This is necessary because in most of the cases the entire content of the modal dialog is re-rendered. Placing focus on a specific button prevents a focus loss.

However, when one of the navigation buttons receives focus, screen readers will announce the newly focused element. This is standard screen readers behavior.

When the button is announced, it often delays or conflicts with other important announcements, for example the name of the currently displayed item. The announcement of the button is really unnecessary for screen reader users. It just adds undesired noise. We should try to find a way to prevent it and provide users with only the most useful information.
"	defect (bug)	assigned	normal	7.2	Administration		normal				accessibility