HTML Writers Guild Web Accessibility Standards
The HTML Writers Guild's policy on web accessibility requires that all official Guild sites be at least minimally accessible to our members with disabilities.
Our definition of minimal accessibility is based upon the World Wide Web Consortium's Web Content Accessibility Guidelines (WCAG). WCAG defines three levels of checkpoint priority, and Guild policy requires at least single-A WCAG compliance, which means all priority one checkpoints.
In addition, the Guild may establish other accessibility requirements beyond single-A compliance on a case-by-case basis; these will be documented here as well.
The Guild's policy on web accessibility also covers any sites provided by external partners that bear the Guild's name and symbols, and are designated as official Guild services. (Exceptions may be made on a case-by-case basis for specific sites, at the option of the Board.)
Last Update: 21 November 1999 by Kynn Bartlett
Twelve Required Accessibility Features of Guild Websites
The following list details, point by point, what is necessary for compliance with the Guild's accessibility policy. References in the text below, of the form [WCAG 1.1], are to version 1.0 of the Web Content Accessibility Guideines.
1. Provide text equivalents for non-text elements.
The ALT attribute must be used on all images and imagemap AREAs.
LONGDESC should be used for images that convey information beyond
simply raw text -- such as an organization chart or a data graph. Text
equivalents must be provided for all multimedia files indicating what
information is contained in the multimedia file. Transcripts may or
may not be required, depending on the content type; if used, transcripts
or captions should be synchronized (e.g. with SMIL).
2. Don't rely solely upon color.
The use of colored text or images to convey information is encouraged,
but this must not be the only way in which that information is conveyed.
Use context or additional markup as well as pure color changes.
For example, if indicating strong
emphasis with the color green, also use the <STRONG>
3. Identify language changes.
Screenreaders and other assistive technologies have different libraries
for different languages. A French phrase pronounced according to English
"rules" may lose all meaning. Use the LANG attribute (and likely the
SPAN element) to identify a language change, such as
<SPAN LANG="fr">Cette phrase est en
4. Make sure pages are usable without style sheets.
The Guild's web page
templates rely heavily upon stylesheets for visual presentation, and
use of CSS is highly encouraged. However, older browsers and many
adaptive technology browsers may not support stylesheets, so it's important
to make sure that the pages can still be used without CSS. For example,
if CSS is used to position elements on a page, those elements might appear
visually in one order using CSS, and out of order if CSS is turned off.
You can test this by using a non-CSS browser or by turning off CSS in
your browser and seeing if the page is still usable.
5. Update equivalents for generated content.
If a page is autogenerated in some way, the textual equivalents for that
page should be in synch with the visually oriented content.
6. Don't make the screen flicker.
Flashing or strobing screen effects can trigger seizures in people with
photosensitive epilepsy. These kinds of effects should never be found on
7. Use plain, understandable English.
The Guild's sites should be understandable by anyone, including people with
cognitive disabilities, poor readers, younger web designers, and those for
whom English is not their primary language. Jargon and technical terms
should be defined when first used or a glossary/reference link provided,
if the meaning is not clear from context.
8. Use client-side imagemaps, not server-side.
Client-side imagemaps are supported by all current browsers and have many
accessibility benefits when used appropriately. Server-side imagemaps may
be used in addition to client-side maps, but should never replace
them. A text equivalent list of links should be provided for all imagemaps.
9. Use HTML 4.0 table markup on data tables.
For tables that express tabular information -- content laid out in columns
and rows -- use HTML 4.0's features that associate cell content with
column and row headers. For more on this, see the
10. Frames should have NOFRAMES and TITLEs.
The Guild's sites should avoid using frames whenever possible. If frames
are used, a valid NOFRAMES element should be set, and each frame within
the frameset should have the TITLE attribute set. For example,
"Navigation Links", "Current Document" and "Help Functions" as titles in
a theoretical three-panel frameset.
11. Don't rely solely upon scripts and applets.
java applet. For this reason, alternatives need to be provided and scripts
has it disabled purposely), and the server should still perform input
field verification. If a script or applet can't be made accessible, an
alternate way to perform the same function should be created.
12. As a last resort, make an alternate page.
Alternate text pages should rarely, if ever, be necessary. If you find
some rare circumstance in which you can't make a page that degrades
gracefully, you should consider creating a second version of that page.
This is dangerous because alternate pages have a tendency to get out of
synch with the "inaccessible" page very quickly. Also, because the HTML
standards are backwards-compatible and forwards-accessible, there should
be no need in all but the most extreme cases for an alternate page.
Therefore, alternate pages should be avoided on Guild sites.