This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10494 - modify aria example and fix spelling
Summary: modify aria example and fix spelling
Status: VERIFIED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y, aria
Depends on:
Blocks: 10066
  Show dependency treegraph
 
Reported: 2010-08-29 13:20 UTC by steve faulkner
Modified: 2011-01-11 17:26 UTC (History)
8 users (show)

See Also:


Attachments

Description steve faulkner 2010-08-29 13:20:29 UTC
the ascii art example in the ARIA section  is misleading as it states 
"Using the features described in this section, one can instead make the ATs skip the ASCII art and just read the caption:"

In current browser/AT implementations it does not provide this functionality and I can't find the source of the assumption that it would. If a reference can be provided it would be useful.

Suggest removing the example or modify it to reflect that it doesn't do what is says it does.

Also, the spelling of aria-labelledby in the code example is incorrect.
Comment 1 Ian 'Hixie' Hickson 2010-09-07 17:18:13 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Did Not Understand Request
Change Description: fixed spelling; no other changes
Rationale: What would the example do, if not what I described? Isn't what I described the whole point here?
Comment 2 contributor 2010-09-07 17:22:53 UTC
Checked in as WHATWG revision r5425.
Check-in comment: typo
http://html5.org/tools/web-apps-tracker?from=5424&to=5425
Comment 3 steve faulkner 2010-09-09 10:46:04 UTC
(In reply to comment #1)
> EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
> satisfied with this response, please change the state of this bug to CLOSED. If
> you have additional information and would like the editor to reconsider, please
> reopen this bug. If you would like to escalate the issue to the full HTML
> Working Group, please add the TrackerRequest keyword to this bug, and suggest
> title and text for the tracker issue; or you may create a tracker issue
> yourself, if you are able to do so. For more details, see this document:
>    http://dev.w3.org/html5/decision-policy/decision-policy.html
> Status: Did Not Understand Request
> Change Description: fixed spelling; no other changes
> Rationale: What would the example do, if not what I described? Isn't what I
> described the whole point here?


1. As implemented it does not do what you describe, so it is misleading.
2. So please either explain how you came to the conclusion that it does what you say it does or remove the example.
Comment 4 Leif Halvard Silli 2010-09-10 04:44:40 UTC
(In reply to comment #3)
> (In reply to comment #1)
> > EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are

> > Rationale: What would the example do, if not what I described? Isn't what I
> > described the whole point here?
> 
> 1. As implemented it does not do what you describe, so it is misleading.
> 2. So please either explain how you came to the conclusion that it does what
> you say it does or remove the example.

By giving the container element the role "img", all the child elements of the container element will be considered presentationl. This is descirbed in ARIA 1.0:

http://www.w3.org/TR/wai-aria/complete#childrenArePresentational
http://www.w3.org/TR/wai-aria/complete#img

As a result, the the labeling elements for the role="img" element has to be pointed to via aria-labelledby, like Ian has done.

As a result of Ian fixing the spelling of aria-labelledby, VoiceOver on Mac OS X 10.5 works ase Ian describes. Thus I see no error in Ian's description.

Which implementations of ARIA 1.0 works differently and what is the difference?
Comment 5 steve faulkner 2010-09-10 10:07:54 UTC
(In reply to comment #4)
> (In reply to comment #3)
> > (In reply to comment #1)
> > > EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
> > > Rationale: What would the example do, if not what I described? Isn't what I
> > > described the whole point here?
> > 
> > 1. As implemented it does not do what you describe, so it is misleading.
> > 2. So please either explain how you came to the conclusion that it does what
> > you say it does or remove the example.
> By giving the container element the role "img", all the child elements of the
> container element will be considered presentationl. This is descirbed in ARIA
> 1.0:
> http://www.w3.org/TR/wai-aria/complete#childrenArePresentational
> http://www.w3.org/TR/wai-aria/complete#img
> As a result, the the labeling elements for the role="img" element has to be
> pointed to via aria-labelledby, like Ian has done.
> As a result of Ian fixing the spelling of aria-labelledby, VoiceOver on Mac OS
> X 10.5 works ase Ian describes. Thus I see no error in Ian's description.
> Which implementations of ARIA 1.0 works differently and what is the difference?

Hi leif, 
thanks for the info, I now understand how it works and why and it does indeed work as described in voiceover, but not in jaws etc on windows.

closing the issue as resolved fixed.
Comment 6 Marco Ranon 2011-01-11 17:26:58 UTC
The bug-triage sub-team verified that the typo was amended. We are not adding the a11ytf keyword since the bug can be closed. Steve, can you please confirm and close the bug?