- From: SVG Working Group repository <cam@mcc.id.au>
- Date: Thu, 10 Jan 2013 19:45:36 -0800
- To: public-svg-wg@w3.org
details: https://svgwg.org/hg/svg2/rev/7463bba69e00 branches: changeset: 413:7463bba69e00 user: Cameron McCormack <cam@mcc.id.au> date: Fri Jan 11 14:47:20 2013 +1100 description: More formatting. diffstat: master/struct.html | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diffs (24 lines): diff --git a/master/struct.html b/master/struct.html --- a/master/struct.html +++ b/master/struct.html @@ -2072,18 +2072,18 @@ the appropriate SVG value type according <a href="http://www.w3.org/TR/wai-aria/appendices#typemapping">Mapping WAI-ARIA Value types to langauges</a> using the SVG mapping ([<a href="refs.html#ref-ARIA">ARIA</a>], section 10.2).</p> <p>WAI-ARIA State and Property attributes can be used on any element. They are not always meaningful, however, and in such cases user agents might not perform any processing aside from including them in the DOM. Unlike some other host languages, SVG is not considered to have strong native host language semantics in terms of the user interface, consequently state and property attributes are -processed according to the <a href="http://www.w3.org/TR/wai-aria">ARIA</a> and -<a href="http://www.w3.org/TR/wai-aria-implementation/">ARIA User Agent Implementation Guide</a> +processed according to the <a href="http://www.w3.org/TR/wai-aria"><cite>ARIA</cite></a> and +<a href="http://www.w3.org/TR/wai-aria-implementation/"><cite>ARIA User Agent Implementation Guide</cite></a> specifications. [<a href="refs.html#ref-ARIA">ARIA</a>] [<a href="refs.html#ref-ARIAIMPL">ARIAIMPL</a>]</p> <h2 id="DOMInterfaces">DOM interfaces</h2> <h3 id="InterfaceSVGDocument">Interface Document</h3> <p>The DOM Core specification defines a <a>Document</a> interface, which this specification extends.</p>
Received on Friday, 11 January 2013 03:45:59 UTC