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
When a user accesses certain sites, the username field is automatically focused for text entry. When they press the tab key, it is expected that the password field will be brought into focus, as was the case before the cookie notice was added. With the latest changes, the X button of the cookie notice gets focused on, rather than the password field. While not a breaking change, it is an inconvenience to the user and is even more so in the development process where we are often using private windows and will repeatedly encounter the cookie notice.
If it is not strictly required that the notice behave this way, I would like for it to respect the tabindex order specified on the page the cookie notice is appearing on. It is also not possible to use the tab key to escape the focus of the cookie notice without interacting with the notice (e.g., pressing the enter key while the X is in focus). Again, I'm not sure if this is required behavior, intended to be helpful, or just an attempt to force the user to interact with the cookie notice in a way that is not required of users using cursor interaction. Thanks!
Websites Affected
cas.byu.edu
cas-stg.byu.edu
Note that this issue does not occur on cas-dev.byu.edu, so perhaps measures were already taken to reduce inconveniences in the development process?
Description
When a user accesses certain sites, the username field is automatically focused for text entry. When they press the tab key, it is expected that the password field will be brought into focus, as was the case before the cookie notice was added. With the latest changes, the X button of the cookie notice gets focused on, rather than the password field. While not a breaking change, it is an inconvenience to the user and is even more so in the development process where we are often using private windows and will repeatedly encounter the cookie notice.
If it is not strictly required that the notice behave this way, I would like for it to respect the tabindex order specified on the page the cookie notice is appearing on. It is also not possible to use the tab key to escape the focus of the cookie notice without interacting with the notice (e.g., pressing the enter key while the X is in focus). Again, I'm not sure if this is required behavior, intended to be helpful, or just an attempt to force the user to interact with the cookie notice in a way that is not required of users using cursor interaction. Thanks!
Websites Affected
Note that this issue does not occur on cas-dev.byu.edu, so perhaps measures were already taken to reduce inconveniences in the development process?
Issue Type
Is this (add an x in the boxes that apply)
on a page?
Browsers Affected
Add an x in all the boxes that apply. Please mark desktop and mobile
browsers separately.
We support the last two versions of Chrome, Firefox, Safari, and Edge.
Desktop Browsers
Mobile Browsers
Web Site Platform
What is hosting your website?
The text was updated successfully, but these errors were encountered: