264
edits
Changes
→XUL, SVG
XUL and SVG don't define the <link> tag, an open question is how the roles can be included in such documents.
* One suggestion is to create a new processing instruction like: <code> <?xml-aria href="chrome://calendar/content/access/roles.json" type="text/json"?></code> (Note from **Aaron, : can we do this on a role by role basis for SVG? We have that advantage in the link solution for HTML)
* Also, since XUL has XBL, and this is effectively a new widget, we could require that it be a new element. The nsIAccessibleProvider interface used in XBL could be extended to provide a property that points to the JSON file. Or, in XBL we could actually directly define the properties that would have been in the JSON.
** Fallen: processing instruction has the advantage that its a more general form of inclusion, which could possibly lead to allowing aria extensions for any type of XML document.
** Fallen: In XBL, we could probably use the <resources> block to add something, i.e:
<pre>
<binding id="foobar">
<resources>
<stylesheet src="chrome://calendar/skin/foosheet.css"/>
<aria-roles src="chrome://calendar/content/access/roles.json/>
<aria-roles src="chrome://calendar/locale/access/roles-l10n.json" l10n="true"/>
</resources>
...
</binding>
== Authoring content with the new widget ==
