Closed Bug 401107 Opened 13 years ago Closed 13 years ago

Some ARIA Buttons fail to be rendered as such (effective Sep 29, 2007)

Categories

(Core :: Disability Access APIs, defect)

x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED INVALID

People

(Reporter: MarcoZ, Assigned: aaronlev)

References

(Blocks 1 open bug, )

Details

(Keywords: access, regression)

On the above given page, which is an ARIA button example, the buttons are no longer rendered as buttons, but as clickables, starting build 2007-07-29.
Other examples, such as the Mozilla XHTML button example, are not affected.
Flags: blocking1.9?
Aaron, while investigating this, I noticed that on the page given in the URL field, the button title was not correctly converted to the button's caption in builds up to 2007-09-28. Do you want a separate bug filed for that?
Starting with builds 2007-09-29, the title is still not used, but now, the image's SRC is used as the caption for the clickable.
Keywords: regression
Blocks: aria
I believe this is intentional behavior. We sent out a message to related newsgroups and known ARIA implementors that we're changing how we process markup and that people would need to change their code.

It's the result of our fix for 
https://bugzilla.mozilla.org/show_bug.cgi?id=397100

We're aiming torward
http://simon.html5.org/specs/aria-proposal

This means we won't allow the role attribute to be namespaced in HTML anymore. It won't be recognized. It will also still work in Firefox 2 if you just use |role| in no namespace on an HTML element.

The problem in the example for this bug is the line:
setAttrNS(elmAccessible, NS_XHTML2, "role", "wairole:" + sClass);

If it still wants to set the role attribute in JS, then it can just do:
element.setAttribute("role", "wairole:" + sClass);

Marking INVALID because this is the cause of authors not catching up to the changes that we published.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
Flags: blocking1.9?
You need to log in before you can comment on or make changes to this bug.