Accessibility/JSON ARIA: Difference between revisions

Accessibility/JSON ARIA (view source)

446 bytes added , 7 January 2009

346

edits

@@ Line 58: / Line 58: @@
 ===XUL, SVG===
-XUL doesn't define the <link> tag, an open question is how the roles can be included in such documents.
+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>
+* 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.
 == Authoring content with the new widget ==