--- a/master/access.html Thu May 17 16:09:19 2012 +1000
+++ b/master/access.html Thu May 17 16:14:06 2012 +1000
@@ -18,115 +18,125 @@
<h2 id="AccessibilityAndSVG">WAI Accessibility Guidelines</h2>
- <p>This appendix explains how accessibility guidelines
- published by W3C's Web Accessibility Initiative (WAI) apply to
- SVG.</p>
- <ol>
- <li>The <a href="http://www.w3.org/TR/2008/REC-WCAG20-20081211/"><cite>Web Content Accessibility Guidelines (WCAG) 2.0</cite></a>
- [<a href="refs.html#ref-WCAG2">WCAG2</a>]
- explains how authors can create Web content that is
- accessible to people with disabilities.</li>
- <li>The <a href="http://www.w3.org/TR/2000/REC-ATAG10-20000203/"><cite>Authoring Tool Accessibility Guidelines 1.0</cite></a>
- [<a href="refs.html#ref-ATAG">ATAG</a>] explains how
- developers can design accessible authoring tools such as SVG
- authoring tools. <a
- href="conform.html#ConformingSVGGenerators">To conform to the
- SVG specification</a>, an SVG authoring tool must conform to
- ATAG (priority 1). SVG support for element <a
- href="struct.html#Groups">grouping</a> and <a
- href="struct.html#UseElement">reuse</a> is relevant to
- designing accessible SVG authoring tools.</li>
- <li>The <a href="http://www.w3.org/TR/2002/REC-UAAG10-20021217/"><cite>User Agent Accessibility Guidelines 1.0</cite></a>
- [<a href="refs.html#ref-UAAG">UAAG</a>] explains how
- developers can design accessible user agents such as
- SVG-enabled browsers. To conform to the SVG specification, an
- SVG user agent should conform to UAAG. SVG support for
- scaling, style sheets, the DOM, and metadata are all relevant
- to designing accessible SVG user agents.</li>
- </ol>
- <p>The W3C Note <a href="http://www.w3.org/TR/2000/NOTE-SVG-access-20000807/"><cite>Accessibility Features of SVG</cite></a>
- [<a href="refs.html#ref-SVG-ACCESS">SVG-ACCESS</a>]
- explains in detail how the requirements of the three guidelines
- apply to SVG.</p>
+<p>This appendix explains how accessibility guidelines
+published by W3C's Web Accessibility Initiative (WAI) apply to SVG.</p>
+
+<ol>
+ <li>The <a href="http://www.w3.org/TR/2008/REC-WCAG20-20081211/"><cite>Web Content Accessibility Guidelines (WCAG) 2.0</cite></a>
+ [<a href="refs.html#ref-WCAG2">WCAG2</a>]
+ explains how authors can create Web content that is
+ accessible to people with disabilities.</li>
+
+ <li>The <a href="http://www.w3.org/TR/2000/REC-ATAG10-20000203/"><cite>Authoring Tool Accessibility Guidelines 1.0</cite></a>
+ [<a href="refs.html#ref-ATAG">ATAG</a>] explains how
+ developers can design accessible authoring tools such as SVG
+ authoring tools. <a href="conform.html#ConformingSVGGenerators">To conform to the
+ SVG specification</a>, an SVG authoring tool must conform to
+ ATAG (priority 1). SVG support for element <a href="struct.html#Groups">grouping</a>
+ and <a href="struct.html#UseElement">reuse</a> is relevant to
+ designing accessible SVG authoring tools.</li>
+
+ <li>The <a href="http://www.w3.org/TR/2002/REC-UAAG10-20021217/"><cite>User Agent Accessibility Guidelines 1.0</cite></a>
+ [<a href="refs.html#ref-UAAG">UAAG</a>] explains how
+ developers can design accessible user agents such as
+ SVG-enabled browsers. To conform to the SVG specification, an
+ SVG user agent should conform to UAAG. SVG support for
+ scaling, style sheets, the DOM, and metadata are all relevant
+ to designing accessible SVG user agents.</li>
+</ol>
+
+<p>The W3C Note <a href="http://www.w3.org/TR/2000/NOTE-SVG-access-20000807/"><cite>Accessibility Features of SVG</cite></a>
+[<a href="refs.html#ref-SVG-ACCESS">SVG-ACCESS</a>]
+explains in detail how the requirements of the three guidelines
+apply to SVG.</p>
<h2 id="SVGAccessibilityGuidelines">SVG Content Accessibility Guidelines</h2>
- <p>This section explains briefly how authors can create
- accessible SVG documents; it summarizes <a href="http://www.w3.org/TR/2000/NOTE-SVG-access-20000807/"><cite>Accessibility Features of SVG</cite></a>
- [<a href="refs.html#ref-SVG-ACCESS">SVG-ACCESS</a>].</p>
- <dl>
- <dt><span class="gl">Provide text equivalents for
- graphics.</span></dt>
- <dd>
- <ul>
- <li>When the text content of a graphic (e.g., in a
- <a>'text'</a> element) explains its function, no text
- equivalent is required. Use the <a>'title'</a> child element
- to explain the function of <a>'text'</a> elements whose meaning
- is not clear from their text content.</li>
- <li>When a graphic does not include explanatory text
- content, it requires a text equivalent. If the equivalent
- is complex, use the <a>'desc'</a> element, otherwise
- use the <a>'title'</a> child element.</li>
- <li>If a graphic is built from meaningful parts, build
- the description from meaningful parts.</li>
- </ul>
- </dd>
- <dt><span class="gl">Do not rely on color alone.</span></dt>
- <dd>
- <ul>
- <li>Do not use color alone to convey information.</li>
- <li>Ensure adequate color contrast. Use style sheets so
- that users who require certain color combinations may
- apply them through user style sheets.</li>
- </ul>
- </dd>
- <dt><span class="gl">Use markup and style sheets and do so
- properly.</span></dt>
- <dd>
- <ul>
- <li>Represent text as character data, not as images or
- curves. Style text with fonts. Authors may describe their
- own fonts in SVG.</li>
- <li>Separate structure from presentation.</li>
- <li>Use the <a>'g'</a> element and rich
- descriptions to structure SVG documents. Reuse named
- objects.</li>
- <li>Publish highly-structured documents, not just
- graphical representations. Documents that are rich in
- structure may be rendered graphically, as speech, or as
- braille. For example, express mathematical relationships
- in <a href="http://www.w3.org/TR/2001/REC-MathML2-20010221/">MathML</a>
- [<a href="refs.html#ref-MATHML">MATHML</a>] and use
- SVG for explanatory graphics.</li>
- <li>Author documents that validate to the SVG
- grammar.</li>
- <li>Use style sheets to specify graphical and aural
- presentation.</li>
- <li>Use relative units in style sheets.</li>
- </ul>
- </dd>
- <dt><span class="gl">Clarify natural language
- usage.</span></dt>
- <dd>
- <ul>
- <li>Use <a>'xml:lang'</a> to identify the
- natural language of content and changes in natural
- language.</li>
- </ul>
- </dd>
- <dt><span class="gl">Ensure that dynamic content is
- accessible.</span></dt>
- <dd>
- <ul>
- <li>Ensure that text equivalents for dynamic content are
- updated when the dynamic content changes.</li>
- <li>Ensure that SVG documents are usable when scripts or
- other programmatic objects are turned off or not
- supported.</li>
- </ul>
- </dd>
- </dl>
+<p>This section explains briefly how authors can create
+accessible SVG documents; it summarizes <a href="http://www.w3.org/TR/2000/NOTE-SVG-access-20000807/"><cite>Accessibility Features of SVG</cite></a>
+[<a href="refs.html#ref-SVG-ACCESS">SVG-ACCESS</a>].</p>
+
+<dl>
+ <dt><span class="gl">Provide text equivalents for graphics.</span></dt>
+ <dd>
+ <ul>
+ <li>When the text content of a graphic (e.g., in a
+ <a>'text'</a> element) explains its function, no text
+ equivalent is required. Use the <a>'title'</a> child element
+ to explain the function of <a>'text'</a> elements whose meaning
+ is not clear from their text content.</li>
+
+ <li>When a graphic does not include explanatory text
+ content, it requires a text equivalent. If the equivalent
+ is complex, use the <a>'desc'</a> element, otherwise
+ use the <a>'title'</a> child element.</li>
+
+ <li>If a graphic is built from meaningful parts, build
+ the description from meaningful parts.</li>
+ </ul>
+ </dd>
+
+ <dt><span class="gl">Do not rely on color alone.</span></dt>
+ <dd>
+ <ul>
+ <li>Do not use color alone to convey information.</li>
+
+ <li>Ensure adequate color contrast. Use style sheets so
+ that users who require certain color combinations may
+ apply them through user style sheets.</li>
+ </ul>
+ </dd>
+
+ <dt><span class="gl">Use markup and style sheets and do so properly.</span></dt>
+ <dd>
+ <ul>
+ <li>Represent text as character data, not as images or
+ curves. Style text with fonts. Authors may describe their
+ own fonts in SVG.</li>
+
+ <li>Separate structure from presentation.</li>
+
+ <li>Use the <a>'g'</a> element and rich
+ descriptions to structure SVG documents. Reuse named
+ objects.</li>
+
+ <li>Publish highly-structured documents, not just
+ graphical representations. Documents that are rich in
+ structure may be rendered graphically, as speech, or as
+ braille. For example, express mathematical relationships
+ in <a href="http://www.w3.org/TR/2001/REC-MathML2-20010221/">MathML</a>
+ [<a href="refs.html#ref-MATHML">MATHML</a>] and use
+ SVG for explanatory graphics.</li>
+
+ <li>Author documents that validate to the SVG grammar.</li>
+
+ <li>Use style sheets to specify graphical and aural presentation.</li>
+
+ <li>Use relative units in style sheets.</li>
+ </ul>
+ </dd>
+
+ <dt><span class="gl">Clarify natural language usage.</span></dt>
+ <dd>
+ <ul>
+ <li>Use <a>'xml:lang'</a> to identify the
+ natural language of content and changes in natural
+ language.</li>
+ </ul>
+ </dd>
+
+ <dt><span class="gl">Ensure that dynamic content is accessible.</span></dt>
+ <dd>
+ <ul>
+ <li>Ensure that text equivalents for dynamic content are
+ updated when the dynamic content changes.</li>
+
+ <li>Ensure that SVG documents are usable when scripts or
+ other programmatic objects are turned off or not
+ supported.</li>
+ </ul>
+ </dd>
+</dl>
</body>
</html>
--- a/master/minimize.html Thu May 17 16:09:19 2012 +1000
+++ b/master/minimize.html Thu May 17 16:14:06 2012 +1000
@@ -16,120 +16,135 @@
<p class="normativity"><em>This appendix is informative, not normative.</em></p>
- <p>Considerable effort has been made to make SVG file sizes as
- small as possible while still retaining the benefits of XML and
- achieving compatibility and leverage with other W3C
- specifications.</p>
- <p>Here are some of the features in SVG that promote small file
- sizes:</p>
- <ul>
- <li>SVG's path data definition was defined to produce a
- compact data stream for vector graphics data: all commands
- are one character in length; relative coordinates are
- available; separator characters do not have to be supplied
- when tokens can be identified implicitly; smooth curve
- formulations are available (cubic Béziers, quadratic
- Béziers and elliptical arcs) to prevent the need to
- tesselate into polylines; and shortcut formulations exist for
- common forms of cubic Bézier segments, quadratic
- Bézier segments, and horizontal and vertical straight
- line segments so that the minimum number of coordinates need
- to be specified.</li>
- <li>Text can be specified using XML character data — no need
- to convert to outlines.</li>
- <li>SVG contains a facility for defining symbols once and
- referencing them multiple times using different visual
- attributes and different sizing, positioning, clipping and
- client-side filter effects</li>
- <li>User agents that support <a
- href="styling.html#StylingWithCSS">styling with CSS</a> can
- use CSS selectors and property inheritance to define commonly
- used sets of attributes once as named styles.</li>
- <li>Filter effects allow for compelling visual results and
- effects typically found only in image-authoring tools using
- small amounts of vector and/or raster data</li>
- </ul>
- <p>Additionally, HTTP/1.1 allows for compressed data to be
- passed from server to client, which can result in significant
- file size reduction. Here are some sample compression results
- using <a href="http://www.ietf.org/rfc/rfc1952.txt">gzip
- compression</a> on SVG documents [<a href="refs.html#ref-RFC1952">RFC1952</a>]:</p>
- <table class='vert' summary="gzip compression results on SVG file sizes">
- <tr style="text-align: center">
- <th>Uncompressed
- SVG</th>
- <th>With gzip
- compression</th>
- <th>Compression
- ratio</th>
- </tr>
- <tr style="text-align: right">
- <td>12,912</td>
- <td>2,463</td>
- <td>81%</td>
- </tr>
- <tr style="text-align: right">
- <td>12,164</td>
- <td>2,553</td>
- <td>79%</td>
- </tr>
- <tr style="text-align: right">
- <td>11,613</td>
- <td>2,617</td>
- <td>77%</td>
- </tr>
- <tr style="text-align: right">
- <td>18,689</td>
- <td>4,077</td>
- <td>78%</td>
- </tr>
- <tr style="text-align: right">
- <td>13,024</td>
- <td>2,041</td>
- <td>84%</td>
- </tr>
- </table>
- <p>A related issue is progressive rendering. Some SVG viewers
- will support:</p>
- <ul>
- <li>the ability to display the first parts of an SVG document
- fragments as the remainder of the document is downloaded from
- the server; thus, the user will see part of the SVG drawing
- right away and interact with it, even if the SVG file size is
- large.</li>
- <li>delayed downloading of images and fonts. Just like some
- HTML browsers, some SVG viewers will download images and
- <a href="http://www.w3.org/TR/2008/REC-CSS2-20080411/fonts.html#q1">WebFonts</a>
- ([<a href="refs.html#ref-CSS2">CSS2</a>], section 15.1)
- last, substituting a temporary image and system fonts,
- respectively, until the given image and/or font is
- available.</li>
- </ul>
- <p>Here are techniques for minimizing SVG file sizes and
- minimizing the time before the user is able to start
- interacting with the SVG document fragments:</p>
- <ul>
- <li>Construct the SVG file such that any links which the user
- might want to click on are included at the beginning of the
- SVG file</li>
- <li>Use default values whenever possible rather than defining
- all attributes and properties explicitly.</li>
- <li>Take advantage of the <a href="paths.html#PathData">path
- data</a> data compaction facilities: use relative
- coordinates; use <em>h</em> and <em>v</em> for horizontal and
- vertical lines; use <em>s</em> or <em>t</em> for cubic and
- quadratic Bézier segments whenever possible; eliminate
- extraneous white space and separators.</li>
- <li>Utilize symbols if the same graphic appears multiple
- times in the document</li>
- <li>For user agents that support <a
- href="styling.html#StylingWithCSS">styling with CSS</a>,
- utilize CSS property inheritance and selectors to consolidate
- commonly used properties into named styles or to assign the
- properties to a parent <a>'g'</a> element.</li>
- <li>Utilize filter effects to help construct graphics via
- client-side graphics operations.</li>
- </ul>
+<p>Considerable effort has been made to make SVG file sizes as
+small as possible while still retaining the benefits of XML and
+achieving compatibility and leverage with other W3C
+specifications.</p>
+
+<p>Here are some of the features in SVG that promote small file sizes:</p>
+
+<ul>
+ <li>SVG's path data definition was defined to produce a
+ compact data stream for vector graphics data: all commands
+ are one character in length; relative coordinates are
+ available; separator characters do not have to be supplied
+ when tokens can be identified implicitly; smooth curve
+ formulations are available (cubic Béziers, quadratic
+ Béziers and elliptical arcs) to prevent the need to
+ tesselate into polylines; and shortcut formulations exist for
+ common forms of cubic Bézier segments, quadratic
+ Bézier segments, and horizontal and vertical straight
+ line segments so that the minimum number of coordinates need
+ to be specified.</li>
+
+ <li>Text can be specified using XML character data — no need
+ to convert to outlines.</li>
+
+ <li>SVG contains a facility for defining symbols once and
+ referencing them multiple times using different visual
+ attributes and different sizing, positioning, clipping and
+ client-side filter effects</li>
+
+ <li>User agents that support <a href="styling.html#StylingWithCSS">styling with CSS</a>
+ can use CSS selectors and property inheritance to define commonly
+ used sets of attributes once as named styles.</li>
+
+ <li>Filter effects allow for compelling visual results and
+ effects typically found only in image-authoring tools using
+ small amounts of vector and/or raster data</li>
+</ul>
+
+<p>Additionally, HTTP/1.1 allows for compressed data to be
+passed from server to client, which can result in significant
+file size reduction. Here are some sample compression results
+using <a href="http://www.ietf.org/rfc/rfc1952.txt">gzip
+compression</a> on SVG documents [<a href="refs.html#ref-RFC1952">RFC1952</a>]:</p>
+
+<table class='vert' summary="gzip compression results on SVG file sizes">
+ <tr style="text-align: center">
+ <th>Uncompressed
+ SVG</th>
+ <th>With gzip
+ compression</th>
+ <th>Compression
+ ratio</th>
+ </tr>
+ <tr style="text-align: right">
+ <td>12,912</td>
+ <td>2,463</td>
+ <td>81%</td>
+ </tr>
+ <tr style="text-align: right">
+ <td>12,164</td>
+ <td>2,553</td>
+ <td>79%</td>
+ </tr>
+ <tr style="text-align: right">
+ <td>11,613</td>
+ <td>2,617</td>
+ <td>77%</td>
+ </tr>
+ <tr style="text-align: right">
+ <td>18,689</td>
+ <td>4,077</td>
+ <td>78%</td>
+ </tr>
+ <tr style="text-align: right">
+ <td>13,024</td>
+ <td>2,041</td>
+ <td>84%</td>
+ </tr>
+</table>
+
+<p>A related issue is progressive rendering. Some SVG viewers will support:</p>
+
+<ul>
+ <li>the ability to display the first parts of an SVG document
+ fragments as the remainder of the document is downloaded from
+ the server; thus, the user will see part of the SVG drawing
+ right away and interact with it, even if the SVG file size is
+ large.</li>
+
+ <li>delayed downloading of images and fonts. Just like some
+ HTML browsers, some SVG viewers will download images and
+ <a href="http://www.w3.org/TR/2008/REC-CSS2-20080411/fonts.html#q1">WebFonts</a>
+ ([<a href="refs.html#ref-CSS2">CSS2</a>], section 15.1)
+ last, substituting a temporary image and system fonts,
+ respectively, until the given image and/or font is
+ available.</li>
+</ul>
+
+<p>Here are techniques for minimizing SVG file sizes and
+minimizing the time before the user is able to start
+interacting with the SVG document fragments:</p>
+
+<ul>
+ <li>Construct the SVG file such that any links which the user
+ might want to click on are included at the beginning of the
+ SVG file</li>
+
+ <li>Use default values whenever possible rather than defining
+ all attributes and properties explicitly.</li>
+
+ <li>Take advantage of the <a href="paths.html#PathData">path
+ data</a> data compaction facilities: use relative
+ coordinates; use <em>h</em> and <em>v</em> for horizontal and
+ vertical lines; use <em>s</em> or <em>t</em> for cubic and
+ quadratic Bézier segments whenever possible; eliminate
+ extraneous white space and separators.</li>
+
+ <li>Utilize symbols if the same graphic appears multiple
+ times in the document</li>
+
+ <li>For user agents that support <a
+ href="styling.html#StylingWithCSS">styling with CSS</a>,
+ utilize CSS property inheritance and selectors to consolidate
+ commonly used properties into named styles or to assign the
+ properties to a parent <a>'g'</a> element.</li>
+
+ <li>Utilize filter effects to help construct graphics via
+ client-side graphics operations.</li>
+</ul>
</body>
</html>
--- a/master/refs.html Thu May 17 16:09:19 2012 +1000
+++ b/master/refs.html Thu May 17 16:14:06 2012 +1000
@@ -50,11 +50,11 @@
<br/>This edition of CSS2 is http://www.w3.org/TR/2008/REC-CSS2-20080411/ and is no longer maintained.
<br/>The <a href="http://www.w3.org/TR/CSS2/">latest edition of CSS2</a> is available at
http://www.w3.org/TR/CSS2/. The CSS Working Group encourages authors and
-implementors to reference <a href="http://www.w3.org/TR/CSS21/">CSS 2.1</a> (or its <a href="http://www.w3.org/TR/CSS/">successor</a>) instead of this
-document and,
-when features common to CSS2 and CSS 2.1 are defined differently
-to follow the definitions in CSS 2.1. A list of <a href="http://www.w3.org/TR/CSS21/changes.html">changes between CSS2 and CSS 2.1</a> may be helpful.
-In particular, future editions of SVG are expected to reference CSS 2.1 and CSS 3 Fonts.
+ implementors to reference <a href="http://www.w3.org/TR/CSS21/">CSS 2.1</a> (or its <a href="http://www.w3.org/TR/CSS/">successor</a>) instead of this
+ document and,
+ when features common to CSS2 and CSS 2.1 are defined differently
+ to follow the definitions in CSS 2.1. A list of <a href="http://www.w3.org/TR/CSS21/changes.html">changes between CSS2 and CSS 2.1</a> may be helpful.
+ In particular, future editions of SVG are expected to reference CSS 2.1 and CSS 3 Fonts.
</dd>
<dt id="ref-DOM1"><strong class="normref">[DOM1]</strong></dt>