Open Bug 1816514 Opened 1 year ago Updated 1 year ago

[CTW] Can't focus some elements when scrolling

Categories

(Core :: Disability Access APIs, defect)

Product:
Core
Component:
Disability Access APIs
Version:
Firefox 109
Type:
defect

Tracking

()

Status:
UNCONFIRMED

People

(Reporter: brunoprietog, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/109.0

Steps to reproduce:

Go to a Twitter profile, for example
https://twitter.com/dhh.

Scroll through the tweets.

Actual results:

The first tweets are correctly focused. After a few, there is no way to focus on the other elements that belong to a tweet. This does not happen with the cache disabled, as you can always focus on the elements. It happens on other pages, I will comment when I find more.

Expected results:

It should be possible to focus the elements correctly

The Bugbug bot thinks this bug should belong to the 'Core::Disability Access APIs' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Disability Access APIs
Product: Firefox → Core

Thanks for reporting. Some questions:

  1. How are you scrolling through tweets? Are you using j and k, the mouse, the arrow keys on the keyboard, a screen reader browse mode or something else?
  2. How many tweets do you scroll through before this becomes a problem?
  3. Specifically what elements are you trying to focus and how are you trying to focus them? Are you pressing tab or some other method of focus?

Thanks.

Blocks: a11y-ctw
Flags: needinfo?(brunoprietog)

The way you scroll is not very relevant here. You can do so by pressing the down arrow or j. You can also do it with some shortcut to move to the next article. In my case, I changed the shortcut in NVDA, and with A I move to the next article. Approximately after the third or fourth tweet this starts to happen.
If you use NVDA, you can try it with the ObjectLocationTones add-on. In the NVDA settings, the auto focus mode for cursor movement must be enabled, in the browse mode options.
If it works properly, NVDA should emit tones every time the cursor passes over focusable elements, which means that the element is on the screen. With CTW disabled this works fine.

Flags: needinfo?(brunoprietog)

Once you reach the fifth tweet, or to exaggerate, the tenth. Try pressing the arrows for any link or button. It's not really on the screen. If you press tab the same thing happens.

So when you say focus here, you're referring to whether NVDA reports it as visually on screen, rather than whether it got keyboard focus? Those are two separate things. They're both important of course, but I just need to be clear on exactly where the bug lies.

Are you running the latest Firefox Nightly? There have been a lot of fixes in this area in the last few days.

Yes, I thought both might be happening at the same time but I think the problem is just that they are off screen.
Apparently I didn't have the latest version because now I checked the updates and I can no longer reproduce the error on Twitter.
I can still reproduce it in other contexts but they are very specific and I don't know how to report it here.
Specifically, it's on hey.com, but it's a paid service where hy you have to sign up and do a few actions to get the interface to change.
It has improved a lot anyway! I can still reproduce some of these problems but not consistently.
I don't know how I could help improve this. If you give me some ideas, for example on how to replicate styles and html I could send examples.
Thanks!

Severity: -- → S4
You need to log in before you can comment on or make changes to this bug.