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 23299 - clarify inline vs script
Summary: clarify inline vs script
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Using ARIA in HTML (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: dmacdona
QA Contact: This bug has no owner yet - up for the taking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-19 21:53 UTC by steve faulkner
Modified: 2014-01-29 22:47 UTC (History)
5 users (show)

See Also:

Attachments

Description steve faulkner 2013-09-19 21:53:12 UTC 
dominic mazzoni:

* I don't quite understand the "Add ARIA inline or via script" section. It'd be helpful to explain why exactly it would not be "safe" to use ARIA inline. Obviously if an ARIA attribute is something that dynamically changes, like aria-checked or aria-activedescendant, it should be modified by a script. But if that's the main concern, why not just say so explicitly? What are the specific concerns about adding ARIA inline in a context where scripting is disabled?
Comment 1 dmacdona 2014-01-13 22:45:39 UTC 
I think addressing mode number 17691 as address this issue. Dominique you please check to see if it's okay now thanks. David
Comment 2 dmacdona 2014-01-17 13:20:49 UTC 
This can now be closed