10000 NVDA browse mode doesn't recognize focus function in some situations with chrome browser · Issue #12084 · nvaccess/nvda · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

NVDA browse mode doesn't recognize focus function in some situations with chrome browser #12084

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.

Sign up for GitHub

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

Jump to bottom
Closed
khsbory opened this issue Feb 20, 2021 · 4 comments
Closed

NVDA browse mode doesn't recognize focus function in some situations with chrome browser #12084

khsbory opened this issue Feb 20, 2021 · 4 comments
Labels
bug close/invalid feature/browse-mode

Comments

@khsbory
Copy link
khsbory commented Feb 20, 2021 •
edited
Loading

Prior to explain this issue, I created sample page for testing.
Issue description:
In chrome browser,

  1. There is a edit field and button.
  2. If I press the button, that button will be hidden with display none and edit field is focused since there is a focus function.
    In that case, if this edit field and button is the DOM last element or connected with div with role group and aria-label, browse mode doesn't recognize focus function.
    Once I turn off browse mode and press the button, focus is moved to edit field and NVDA says edit.
    But once I turn on browse mode and press the button, NVDA says nothing.
    How to test:
  3. Go to sample page. There are two edit fields.
  4. In example 1 heading, type keyowrd and press tab key. You can find delete keyword button.
  5. Press the button. NVDA browse mode can recognize focus function and take you to search field.
  6. Go to example 2 heading and type search keyword and press tab key. This heading, edit and button are connected with div with role group and aria-labelledby.
  7. Press the button. NVDA says nothing and screen reader user doesn't know what is happened.
    NVDA browse mode should recognize focus function with any conditions.
    Thank you so much.
@khsbory khsbory changed the title management NVDA browse mode doesn't recognize focus function in some situations NVDA browse mode doesn't recognize focus function in some situations with chrome browser Feb 20, 2021
@khsbory
Copy link
Author
khsbory commented Apr 10, 2021

@feerrenrut Hey, there. May I ask did you check my NVDA bug report regarding this issue?
Thank you.

@feerrenrut
Copy link
Contributor

In the future, please fill out the bug template. It is structured to ensure that you provide the information we need in an easy to read way.

This does look to me like a legitimate bug. I tested this with Edge (Anaheim) Version 89.0.774.75 (Official build) (64-bit)

To anyone else looking at this, the test sample contains two variations (Example 1 and Example 2), the first one works as expected the second one doesn't. The difference between the two is only that the wrapping div on the second has role group and aria-label. The javascript for both is equal, all other elements are also equal.

Note that after pressing the button for Example 2 the virtual cursor is not updated, with focus highlight, it seems to be left with the button (now hidden), focus is tracked to the edit field but NVDA does not report this.

@Adriani90
Copy link
Collaborator

Not sure if this is completely in line with Aria spec. @jcsteh what do you think?

@Adriani90
Copy link
Collaborator

After testing with NVDA 2025 Beta and firefox 138 or Chrome canary 138

  1. Open sample page
  2. In the first edit field, type something
  3. Change to browse mode and press "delete button"
  4. Navigate to second edit field
  5. Repeat steps 2 and 3
    Actual:
    In step 3, Focus is redirected to "example 2 heading"
    In step 5, focus is redirected to the edit field in Chrome, but in Firefox it selects an empty area.
    Expected: Focus should be redirected to the edit field with exact coordinates

This is probably bad web authoring. I am closing as invalid. Focus redirection should be handled by the web author.

@Adriani90 Adriani90 closed this as not planned Won't fix, can't repro, duplicate, stale May 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug close/invalid feature/browse-mode
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@feerrenrut @khsbory @Adriani90
0