Bug 19451 - Guidance on when to add ARIA inline vs script is misleading
Guidance on when to add ARIA inline vs script is misleading
Status: NEW
Product: HTML WG
Classification: Unclassified
Component: HTML a11y APIs (editor: Steve Faulkner, Cynthia Shelly)
unspecified
Other All
: P3 major
: ---
Assigned To: steve faulkner
HTML a11y API spec bugbot
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-10 21:19 UTC by lazd
Modified: 2012-11-06 17:59 UTC (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lazd 2012-10-10 21:19:22 UTC
The sentence in question:

"If the content and interaction is only supported in a scripting enabled browsing context, for example Google docs applications require JavaScript enabled to work, so it is safe for them to include the ARIA markup inline.

Otherwise add ARIA via scripting."

It seems like the author meant to say:

"If the content and interaction is only supported in a scripting enabled browsing context, for example Google docs applications require JavaScript enabled to work, it is safe to add the ARIA via scripting."

Either way, some additional elaboration on when to use markup inline and when to add via scripting would be beneficial.

Thanks!
Comment 1 Andi Snow-Weaver 2012-10-18 21:26:33 UTC
Please specify the section of the User Agent Implementation Guide that this comment refers to. This sounds like text that is in the Authoring Practices Guide, not the UAIG.
Comment 2 lazd 2012-10-18 21:36:07 UTC
Hi Andi,
The specific article is: "Using ARIA in HTML" http://dvcs.w3.org/hg/aria-unofficial/raw-file/tip/index.html

The section is:
Notes on ARIA use in HTML > First rule of ARIA use > Paragraph 1

This bug should be filed under the "Using ARIA in HTML5" component of the "HTML WG" product... I'm not sure why "ARIA UA Implementors" is assigned.