Closed
Bug 575976
Opened 15 years ago
Closed 13 years ago
ARIA conformance, relation trumps role=presentation
Categories
(Core :: Disability Access APIs, defect)
Core
Disability Access APIs
Tracking
()
RESOLVED
DUPLICATE
of bug 768296
People
(Reporter: davidb, Assigned: davidb)
References
(Blocks 1 open bug)
Details
(Whiteboard: [ARIA conformance])
Attachments
(1 file, 1 obsolete file)
|
4.48 KB,
patch
|
Details | Diff | Splinter Review |
It looks like the group will ask that we don't strip the h1 element in the following case:
<img role="button" src="orgchart.png" aria-labelledby="o1">
<h1 id="o1" role="presentation">placeholder</h1>
I'll hang a patch in case we need to handle this.
| Assignee | ||
Comment 2•13 years ago
|
||
Finally getting back to this one. Alex would you like to review?
Attachment #455137 -
Attachment is obsolete: true
Attachment #618384 -
Flags: review?(surkov.alexander)
Comment 3•13 years ago
|
||
Comment on attachment 618384 [details] [diff] [review]
updated patch (includes test)
Review of attachment 618384 [details] [diff] [review]:
-----------------------------------------------------------------
::: accessible/src/base/nsAccessibilityService.cpp
@@ +1067,1 @@
> return nsnull;
note: the way you ignore presentation role in case of IsFocusable and hasRelatedContent is different. When focusable then we ignore it entirerly, in second case you create an accessbile but ignore native semantics. Which way we should do for hasRelatedContent? If the way you did then you need to comment it properly.
@@ +1219,5 @@
> if (!newAcc && content->Tag() != nsGkAtoms::body && content->GetParent() &&
> ((weakFrame.GetFrame() && weakFrame.GetFrame()->IsFocusable()) ||
> (isHTML && nsCoreUtils::HasClickListener(content)) ||
> HasUniversalAriaProperty(content) || roleMapEntry ||
> + hasRelatedContent || HasRelatedContent(content) ||
just to be on safe side? then I'd recommend to do
hasRelatedContent || HasRelatedContent(content) || hasRelatedContent
it looks mystery ;)
Attachment #618384 -
Flags: review?(surkov.alexander)
| Assignee | ||
Comment 4•13 years ago
|
||
Thanks for making me double check. The spec (now) says (regarding elements that should be included in the tree):
"Elements that have an ID which is referenced by another element via a WAI-ARIA relation (aria-controls, aria-describedby, aria-flowto, aria-labelledby or aria-owns), are not hidden, and do not have a role of presentation directly or inherited from an owning element."
Closing invalid.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
| Assignee | ||
Comment 5•13 years ago
|
||
Sigh.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Whiteboard: [ARIA conformance]
| Assignee | ||
Comment 7•13 years ago
|
||
I guess we'll call this one a dupe.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•