You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If it's convenient, pull out h1 out of the form element. Elements in a form that aren't form inputs/buttons/labels can get missed in screen readers' form modes, but the page title would be announced when the page is first loaded anyways.
When a site logo is uploaded, there should still be an h1 element containing the site name. It should be the site logo image with the site name as its alt value nested in an h1.
It would be more clear if the login page form fields had persistent visible labels. Since it's a log-in form, users generally likely expect to enter a username/email and password. Maybe can be something to redesign for 4.0 if not sooner. Moved to: Persistent labels for login form fields #7296
Required form fields are not announced to AT
Password visibility toggle is not keyboard accessible
The "Forgot your password" link doesn't have an href value so it isn't focusable/usable with the keyboard. Change to a valid a tag or button element. I would go with button since the URL isn't changing. Related: Keyboard accessibility- admin login #7287
There should be some way to get back to the log-in form view after going to the reset password form view.
The text should be updated for the forgot password form's submit button. It currently still says "Login". Should be changed to "Reset password" or similar.
Description
Some ares for accessibility improvements on the CP login page (
/admin/login
):h1
out of theform
element. Elements in a form that aren't form inputs/buttons/labels can get missed in screen readers' form modes, but the page title would be announced when the page is first loaded anyways.h1
element containing the site name. It should be the site logo image with the site name as its alt value nested in anh1
.href
value so it isn't focusable/usable with the keyboard. Change to a valida
tag orbutton
element. I would go withbutton
since the URL isn't changing. Related: Keyboard accessibility- admin login #7287Steps to reproduce
/admin/login
Additional info
The text was updated successfully, but these errors were encountered: