With the accessibility cache enabled, open Google, search for a term such as "test search" and examine the results. For some results, mousing over a `h3` that defines a search result link will not read the link out with NVDA. Examining further, it appears that the cached bounds of these heading accessibles are incorrect. The bounds appear y-translated down the page. Using NVDA's visual highlighting, I can confirm that mousing over the visually-incorrect location of the bounds does cause NVDA to read out the search result. The pattern of which results have this problem and which don't is unclear to me, but it seems to start occurring after at least the 2nd result. Something very strange to note here: when I inspect the properties of these headings with the Dev Tools, the problem immediately rights itself. Similarly, if I press the "about this result" button next to a busted search result, the problem rights itself when that dialog closes. These factors make it really tough to get an easily reproducible example, since I can't get to whatever state the markup is in before the Dev Tools touch it (at which point it rights itself). But it's annoying for users nonetheless. I tested this on Windows 11 with NVDA.
Bug 1811972 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
With the accessibility cache enabled, open Google, search for a term such as "test search" and examine the results. For some results, mousing over a `h3` that defines a search result link will not read the link out with NVDA. Examining further, it appears that the cached bounds of these heading accessibles are incorrect. The bounds appear y-translated down the page. Using NVDA's visual highlighting, I can confirm that mousing over the visually-incorrect location of the bounds does cause NVDA to read out the search result. The pattern of which results have this problem and which don't is unclear to me, but it seems to start occurring after at least the 2nd result. Something very strange to note here: when I inspect the properties of these headings with the Dev Tools, the problem immediately rights itself. Similarly, if I press the "about this result" button next to a busted search result, the problem rights itself when that dialog closes. These factors make it really tough to get an easily reproducible example, since I can't get to whatever state the markup is in before the Dev Tools touch it (at which point it rights itself). But it's annoying for users nonetheless. I tested this on Windows 11 with NVDA. Note: Originally reported by [:4RJames] [here](https://bugzilla.mozilla.org/show_bug.cgi?id=1809082#c18).
With the accessibility cache enabled, open Google, search for a term such as "test search" and examine the results. For some results, mousing over a `h3` that defines a search result link will not read the link out with NVDA. Examining further, it appears that the cached bounds of these heading accessibles are incorrect. The bounds appear y-translated down the page. Using NVDA's visual highlighting, I can confirm that mousing over the visually-incorrect location of the bounds does cause NVDA to read out the search result. The pattern of which results have this problem and which don't is unclear to me, but it seems to start occurring after at least the 2nd result. Something very strange to note here: when I inspect the properties of these headings with the Dev Tools, the problem immediately rights itself. Similarly, if I press the "about this result" button next to a busted search result, the problem rights itself when that dialog closes. These factors make it really tough to get an easily reproducible example, since I can't get to whatever state the markup is in before the Dev Tools touch it (at which point it rights itself). But it's annoying for users nonetheless. I tested this on Windows 11 with NVDA. Note: Originally reported by :4RJames [here](https://bugzilla.mozilla.org/show_bug.cgi?id=1809082#c18).
With the accessibility cache enabled, open Google, search for a term such as "test search" and examine the results. For some results, mousing over a `h3` that defines a search result link will not read the link out with NVDA. Examining further, it appears that the cached bounds of these heading accessibles are incorrect. The bounds appear y-translated down the page. Using NVDA's visual highlighting, I can confirm that mousing over the visually-incorrect location of the bounds does cause NVDA to read out the search result. The pattern of which results have this problem and which don't is unclear to me, but it seems to start occurring after at least the 2nd result. Something very strange to note here: when I inspect the properties of these headings with the Dev Tools, the problem immediately rights itself. Similarly, if I press the "about this result" button next to a busted search result, the problem rights itself when that dialog closes. These factors make it really tough to get an easily reproducible example, since I can't get to whatever state the markup is in before the Dev Tools touch it (at which point it rights itself). But it's annoying for users nonetheless. I tested this on Windows 11 with NVDA. Note: Originally reported by 4RJames@gmail.com [here](https://bugzilla.mozilla.org/show_bug.cgi?id=1809082#c18).