-
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
Site title: link text and accessible name mismatch #62644
Comments
@up1512001 thanks. Personally, I would use the Note: All the available iocns from the |
@afercia used the |
Currently the UI is shifting from text based external links to leverage the |
Thanks, I'm seeing it now in a few places in the UI. Can you please point me to the relevant discussion issue / PR for that change? [Edit] Found the PR: #60255 As a first thought, I'm not sure I can support a design change that makes things less visible. I see a trend in the editor design where low vision users needs aren't very well considered. I'd like to read the argumentations behind that change first though. Thanks. |
I created a separate issue for the design of the external icon / new unicode character. See #62832 |
Description
Follow up to #61258
The Site Title in the Site editor navigation panel is now a link to the front end. So far so good. However, there's a couple issues to fix:
blogname
value, for example: "My awesome site".aria-label="View site (opens in a new tab)"
which is an hardcoded string.↗
unicode character via a CSS pseudo element) mismatches other icons used for the same 'view site' functionality. I'm not sure this helps building a cohesive visual language. Icons usage should be consistent, as also mentioned in the original PR Site Editor: Use site title as a link #61258 (review)Step-by-step reproduction instructions
aria-label="View site (opens in a new tab)"
that mismatches the visible text.Screenshots, screen recording, code snippet
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
The text was updated successfully, but these errors were encountered: