Open Bug 1464049 Opened 7 years ago Updated 3 years ago

IAccessibleText::scrollSubStringTo() doesn't scroll far enough

Categories

(Core :: Disability Access APIs, defect, P3)

52 Branch
x86
Windows
defect

Tracking

()

People

(Reporter: mike.hill, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36 Steps to reproduce: If you have a block of text that is broken across multiple lines, but is represented as a single object in the accessibility tree, you can call IAccessibleText::scrollSubStringTo() to scroll the pane so that a specific line or section of text is made visible. Actual results: The page scrolls, but doesn't scroll far enough to make the section of text completely visible, if the object is off the bottom of the page. If the object is off the top, then it scrolls correctly. It looks like it's scrolling to make the top,left corner of the bounding box of the substring visible, not not taking into account the height/width of the string. Expected results: It should scroll so that the entire substring becomes visible (assuming it fits in the window).
Status: UNCONFIRMED → NEW
Component: Untriaged → Disability Access APIs
Ever confirmed: true
Product: Firefox → Core
Target Milestone: --- → Future
Thanks Mike! The Target Milestone is set when the bug fix lands on Mozilla-Central. Clearing it to avoid confusion.
Blocks: texta11y
OS: Unspecified → Windows
Hardware: Unspecified → x86
Target Milestone: Future → ---
Priority: -- → P3

I can confirm this issue on Linux as well, tested with today's nightly.

This is a concern for us because then the screen reader is speaking some text which isn't visible on the screen, thus confusing sighted users working with non-sighted users. It's even worse for partially-sighted users who are using a screen magnifier: they get to see the first words which correctly get scrolled, but not what is on the subsequent lines.

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