Closed Bug 304805 Opened 19 years ago Closed 19 years ago

Links are not read by screen reader

Categories

(Firefox :: Disability Access, defect)

x86
Linux
defect
Not set
critical

Tracking

()

RESOLVED FIXED

People

(Reporter: Louie.Zhao, Assigned: ginnchen+exoracle)

References

Details

When navigating links using "Tab" in a webpage, nothing is read by gnopernicus.
This is a critical bug for firefox a11y on Unix platform.
Using "Tab" in any XUL dialog, the form controls can neither be read by
gnopernicus. Change the title to include both links and form controls.
Summary: Links are not read by screen reader → Links & Form Controls are not read by screen reader
Part of cause is regression of bug 168624.
That patch changed atk/nsAccessibleHyperText.cpp and atk/nsHTMLLinkAccessibleWrap.cpp
-      if (parentNode == focusedNode) {
+      if (parentNode == nsAccessNode::gLastFocusedNode) {

-  *aIsSelected = (focusedNode == mDOMNode);
+  *aIsSelected = (gLastFocusedNode == mDOMNode);

But nsAccessNode::gLastFocusedNode is not updated when a link is focused.
Assignee: Louie.Zhao → ginn.chen
(In reply to comment #1)
> Using "Tab" in any XUL dialog, the form controls can neither be read by
> gnopernicus. Change the title to include both links and form controls.

Form controls in webpage & XUL WFM.
Summary: Links & Form Controls are not read by screen reader → Links are not read by screen reader
Depends on: 320387
After applied patch of bug 320388, this bug disappeared.
Status: NEW → ASSIGNED
Fixed bu 320388
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.