-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Description
Description
Admittedly from anecdotal experience but every single time I use and test the font library I struggle to find the UI control to open the 'Manage fonts' modal dialog.
Clicking one of the installed fonrs does open the modal dialog but it brings me to the sub-view of that specific font within the modal dialot. This is useful when I want to manage that specific font.
Instead, when I want to open the Fonts library list, I struggle.
Turns ouf the control to open it is a small Aa icon button. Screenshot:
- The
Aaicon doesn't really represent the concept of 'Manage fonts'. - As a speech recognition software user I can't figure out the accessible name of that button by the visuals of the icon. As such, I wouldn't be able to issue an appropriate voice command and I would be forced to tab to the button to discover its accessible name.
- The same icon is used also for the Elements styles right below the Fonts group, which makes the UI confusing. What is the different meaning of the two icons?
- Icon buttons should only be used when there's not enough space to use visible text.
- Icons should be used when they help clarify meaning. They should not be used to obscure a functionality and make it less discoverable.
Overall, visually, looking at the UI I can't find anything that tells me 'Manage fonts'. I see icons, and I don't know what they mean nor the UI makes it easier to understand these icons meaning.
For accessibility, icon buttons are always less than ideal. In this case, I think this Aa icon does more harm than good and should be replaced with visible text. The placement of the button with visible text could be at the top [Edit:] at the bottom of the list of the installed fonts.
Step-by-step reproduction instructions
- Go to the Site Editor > Styles > Typography
- Observe the UI within the Typography panel.
- Try to determine wich of the UI controls is the one to 'Manage fonts'.
Screenshots, screen recording, code snippet
No response
Environment info
No response
Please confirm that you have searched existing issues in the repo.
Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes
