Skip to content
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

[BUG] Cookie notice overrides intended tabindex order #526

Open
5 of 19 tasks
danieltaylor opened this issue Jun 7, 2023 · 0 comments
Open
5 of 19 tasks

[BUG] Cookie notice overrides intended tabindex order #526

danieltaylor opened this issue Jun 7, 2023 · 0 comments
Labels

Comments

@danieltaylor
Copy link

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

  • 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?

Issue Type

Is this (add an x in the boxes that apply)

  • A difference between the components and the Official Specification?
  • A bug, such as a Javascript error, or the UI not rendering properly
    on a page?
  • Inconsistent appearance/behavior between browsers?
  • An issue on mobile browsers?
  • A request for a new feature/enhancement?

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

  • Google Chrome
  • Mozilla Firefox
  • Apple Safari
  • Microsoft Edge
  • Other (please specify)

Mobile Browsers

  • Any browser on iOS
  • Chrome for Android
  • Firefox Mobile for Android
  • Other (please specify)

Web Site Platform

What is hosting your website?

  • Drupal 7
  • Drupal 8
  • Wordpress
  • Custom Site
  • Don't Know
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant