Closed Bug 338874 Opened 20 years ago Closed 20 years ago

Safe Browsing alert not exposed to screenreader

Categories

(Toolkit :: Safe Browsing, defect)

2.0 Branch
x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED FIXED
Firefox 2 alpha3

People

(Reporter: pilgrim, Assigned: pilgrim)

References

()

Details

(Keywords: access, fixed1.8.1)

Attachments

(1 file)

The Safe Browsing overlay is not exposed to assistive technologies. Two things need to happen: 1. The speech bubble needs to be focused when it is displayed. This is actually important for two reasons; it will signal to screenreaders to read it, and it will move focus out of the web page which will prevent keyboard users from tabbing around the page under the stack. We can use a -moz-user-focus: normal on the containing vbox, then get a reference to that DOM node and call its focus() method from showMessage_. 2. The speech bubble needs to be exposed as an alert. We can use DHTML Accessibility techniques to simulate this (xhtml2:role="wairole:alert"). This does *not* mean that Firefox will be popping up an actual alert box; it will just be exposing that DOM node as an alert so that DHTML-aware screenreaders such as WindowEyes can read it properly. I have this working on a local copy and am in the process of submitting a patch. It would be really nice if this could go into Bon Echo alpha 3, despite the code freeze.
Status: NEW → ASSIGNED
Implements as described in comment 1.
Assignee: nobody → pilgrim
Attachment #222923 - Flags: review?(tony)
Comment on attachment 222923 [details] [diff] [review] Expose speech bubble as alert and auto-focus You'll need sr for commit (maybe ask mconnor?)
Attachment #222923 - Flags: review?(tony) → review+
Attachment #222923 - Flags: superreview?(darin)
Comment on attachment 222923 [details] [diff] [review] Expose speech bubble as alert and auto-focus sure, this is more of a rubberstamp sr because I don't know the first thing about these technologies. this appears to be the kind of solution being employed elsewhere in the codebase, so i assume that "we" are all in agreement about how this is to be done ;-) sr=darin
Attachment #222923 - Flags: superreview?(darin) → superreview+
Attachment #222923 - Flags: approval-branch-1.8.1+
Whiteboard: [checkin needed]
Checked in on trunk. Branch is closed at the moment.
Flags: blocking-firefox2?
Target Milestone: --- → Firefox 2 alpha3
Bombs away, Robert. Please land this on the branch for Alpha 3.
Flags: blocking-firefox2? → blocking-firefox2+
Landed on branch. ----------------- Checking in browser/components/safebrowsing/content/warning-overlay.xul; /cvsroot/mozilla/browser/components/safebrowsing/content/warning-overlay.xul,v <-- warning-overlay.xul new revision: 1.2.2.2; previous revision: 1.2.2.1 done Checking in browser/components/safebrowsing/content/phishing-afterload-displayer.js; /cvsroot/mozilla/browser/components/safebrowsing/content/phishing-afterload-displayer.js,v <-- phishing-afterload-displayer.js new revision: 1.1.2.3; previous revision: 1.1.2.2 done
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Keywords: fixed1.8.1
Resolution: --- → FIXED
Whiteboard: [checkin needed]
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: