Skip to content

Commit 86db38c

Browse files
committed
[css2] Removed commented text, added list of accessibility features
--HG-- extra : convert_revision : svn%3A73dc7c4b-06e6-40f3-b4f7-9ed1dbc14bfc/trunk%401655
1 parent b779323 commit 86db38c

1 file changed

Lines changed: 37 additions & 38 deletions

File tree

css2/intro.src

Lines changed: 37 additions & 38 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
22
<html lang="en">
3-
<!-- $Id: intro.src,v 2.29 1998-04-30 17:27:09 howcome Exp $ -->
3+
<!-- $Id: intro.src,v 2.30 1998-05-06 02:22:00 ijacobs Exp $ -->
44
<HEAD>
55
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
66
<TITLE>Introduction to CSS2</TITLE>
@@ -170,10 +170,6 @@ to its surroundings. The "em" unit refers to the font size of the
170170
element. In this case the result is that the margins around the BODY
171171
element are three times wider than the font size.
172172

173-
174-
175-
<!-- Add image, printing, info, positioning, fonts -->
176-
177173
<H2>A brief CSS2 tutorial for XML</H2>
178174

179175
<P>CSS can be used with any structured document format, for example
@@ -206,11 +202,9 @@ INSTRUMENT { display: inline }
206202
ARTICLE, HEADLINE, AUTHOR, PARA { display: block }
207203
</PRE>
208204

209-
<P>The first rule declares INSTRUMENT to be inline <!--(though this rule
210-
is not strictly necessary, because 'inline' is the default),[hmm,
211-
perhaps initial value, but it's anyway too advanced, HWL]--> and the
212-
second rule, with its comma-separated list of selectors, declares all
213-
the other elements to be block-level.
205+
<P>The first rule declares INSTRUMENT to be inline and the second
206+
rule, with its comma-separated list of selectors, declares all the
207+
other elements to be block-level.
214208

215209
<P>One proposal for linking a style sheet to an XML document is to use
216210
a processing instruction:
@@ -315,18 +309,6 @@ during this phase. In particular, content generated due to style
315309
sheets is not fed back to the document language processor (e.g., for
316310
reparsing).
317311

318-
<!-- Is the next statement still true? If so, it should probably
319-
be made specific and moved to visudet.src -->
320-
321-
<!--
322-
<P>If an element A is an ancestor of an element D, all formatting
323-
objects generated for A must be above the formatting objects
324-
rendered for D in the tree of formatting objects. For box
325-
and page box formatting objects, this implies that, to
326-
find a containing box for an element, a user agent need only search
327-
upward in the tree of rendering objects (not left, right, or down).
328-
-->
329-
330312
<li>Transfer the formatting structure to the target medium (e.g., print
331313
the results, display them on the screen, render them as speech,
332314
etc.).
@@ -466,25 +448,42 @@ class="propinst-color">'color'</span> property.</P>
466448
</LI>
467449

468450
<LI>
469-
<P><STRONG>Accessibility</STRONG>. CSS will
470-
increase accessibility to Web documents, not just for people with
471-
disabilities, but for everybody, and even for robots. By retaining
472-
textual information in text form, robots and human users alike will
473-
have more options for digesting the content. Users can provide their
474-
personal style sheets if author-suggested style sheets hinder
475-
accessibility. The cascading mechanism combines and selects from
476-
different style sheets.</P>
477-
478-
<!-- Review this text... -IJ -->
479-
480-
<div class="note"><P>
481-
<em><strong>Note.</strong> For more information
451+
<P><STRONG>Accessibility</STRONG>. CSS has several
452+
features designed to
453+
make the Web more accessible to users with disabilities:</p>
454+
455+
<UL>
456+
<li>Improved media support, including media groups and the
457+
braille, embossed, and tty media types.
458+
<LI>The semantics of <tt>!important</tt> rules mean
459+
that "the user can always win" in the cascade. This allows
460+
users with particular needs (large fonts, color combinations,
461+
etc.) to override the author's styles.
462+
<li>The new 'inherit' value for all properties
463+
improves cascading "generality". For instance:
464+
<PRE class="css-example">
465+
BODY { font-size: 12pt }
466+
P { font-size: inherit }
467+
</PRE>
468+
<LI>The aural properties give control over voice and audio output.
469+
<LI>Access to alternative content through attribute
470+
selectors, the 'attr()' function,
471+
and the 'content' property.
472+
<LI>Counters and section/paragraph numbering. These allow
473+
users with braille/tty devices an alternative to
474+
outlines. <!-- What does this mean? -->
475+
<LI>Generated content.
476+
</UL>
477+
478+
<P>Furthermore, by allowing designers to add style to text rather than
479+
requiring them to use images, CSS will allow human users and robots
480+
alike to reap more information from pages.
481+
</P>
482+
483+
<div class="note"><P> <em><strong>Note.</strong> For more information
482484
about designing accessible documents using CSS and HTML, please
483485
consult [[-WAIGUIDE]].</em>
484486
</div>
485-
486-
</LI>
487-
488487
</UL>
489488

490489

0 commit comments

Comments
 (0)