This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The sentence says "If the content and interaction is only supported in a scripting-enabled browsing context, i.e. Google docs (its applications require JavaScript enabled to work), it is not safe to include the ARIA markup inline." If the application relies on scripting then it is safe to include ARIA markup inline OR via scripting. This sentence states that in this case you cannot add ARIA inline which is incorrect. Please remove the not so this reads "If the content and interaction is only supported in a scripting-enabled browsing context, i.e. Google docs (its applications require JavaScript enabled to work), it is safe to include the ARIA markup inline."
(In reply to James Nurthen from comment #0) > The sentence says > "If the content and interaction is only supported in a scripting-enabled > browsing context, i.e. Google docs (its applications require JavaScript > enabled to work), it is not safe to include the ARIA markup inline." > > If the application relies on scripting then it is safe to include ARIA > markup inline OR via scripting. > > This sentence states that in this case you cannot add ARIA inline which is > incorrect. Please remove the not so this reads > > "If the content and interaction is only supported in a scripting-enabled > browsing context, i.e. Google docs (its applications require JavaScript > enabled to work), it is safe to include the ARIA markup inline." I have modified the text commit https://github.com/w3c/aria-in-html/commit/488534666dcc7ce32524e4ad4a03f11240d9fd7e please review, and re-open if needed http://w3c.github.io/aria-in-html/#add-aria-inline-or-via-script