-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Font Library: Consider clarifying which fonts are uploaded vs theme provided in modal #55220
Comments
I added #58403 to reinforce any work that might be done here and surface it in the Global Styles > Typography. This would reduce site builders of having to even launch the Font Library modal to see the different sources of where fonts were installed, e.g. Theme, User, etc. |
#58834 will solve this problem. |
I have added this issue to WP6.5 project board. See this comment for the reason. |
Moved this to 6.6 because it's an enhancement that can land later which will allow us to focus on the main font library issues for 6.5. |
Totally agree. I think this was also mentioned in other conversatios as well as an accessibility issue as any section of content should be clearly identified by a heading. These are lists of content items. It's not clear why one of the list does have a heading and the other doesn't. |
In the latest Font Library, the text for headings exists in both font lists. Should we change "Installed Fonts" to another text? By the way, accessibility improvements should be addressed by #58834. |
I dig this! I think installed fonts works great. I think we can close this out if I'm understanding correctly. Let me know and I can reopen too. At least on my end, this addresses the distinction between the two for me. |
Pulling in feedback from the FSE Outreach Program's Final Touches call for testing:
Right now, after uploading a font, it's not clear which comes from the theme vs uploaded separately. There's an argument to be had that this can make it easier for folks to just do what they want to do with fonts without worrying about that kind of separation but I can also see why folks might want to know what came with the theme vs what they are customizing.
The text was updated successfully, but these errors were encountered: