Closed Bug 279941 Opened 20 years ago Closed 20 years ago

Expose forms in MSAA

Categories

(Firefox :: Disability Access, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: aaronlev, Assigned: aaronlev)

Details

(Keywords: access)

Attachments

(1 file)

Screen readers have features to navigate by "form"

This means we need to expose accessible objects for the form nodes.
Keywords: access
Attachment #172471 - Flags: review?(pkwarren)
Attachment #172471 - Flags: review?(pkwarren) → review+
Attachment #172471 - Flags: superreview?(bryner)
Looks good to me, out of curiosity though which Screen readers have this
feature, and what on "form" is navigateable?

Plus when we have a situation like

<form></form> what happens with the Screen Reader in question?

Our DOM with Forms can be quite onerous in some cases, where we have form
controls (Input, etc.) sitting un-nested from the form element they work with,
as far as I understand the relevant code.
Window-Eyes has the feature, and they're adding capaibility to recognize this
MSAA role.

They know that the <form> elements may not always be placed correctly. The
prev/next form navigation goes to the beginning of each form -- the first
accessible element within that.
Attachment #172471 - Flags: superreview?(bryner) → superreview+
Checking in nsAccessibilityService.cpp;
/cvsroot/mozilla/accessible/src/base/nsAccessibilityService.cpp,v  <-- 
nsAccessibilityService.cpp
new revision: 1.123; previous revision: 1.122
done
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: