Summary

  • The W3C's May 1999 Web Content Accessibility Guidelines 1.0 set out fourteen guidelines, checkpoint priorities and three conformance levels.
  • Guideline 10 explicitly labeled five page-author workarounds as interim measures needed while browsers and assistive technologies lacked particular capabilities.

Imagine shipping a door whose hinges are still being invented, then asking the person entering to wait for the next hardware revision. The Web Content Accessibility Guidelines 1.0 took a less leisurely view of 1999 Web software. People needed to use pages now. Some browsers and assistive tools could not yet present common interactions reliably. The W3C's Guideline 10 therefore told page authors to install temporary ramps: extra explanations, alternate paths and little pieces of markup that bridged the gap until user agents improved.

The word interim carried an unusually precise promise. The working group considered these checkpoints necessary when the Recommendation appeared on 5 May 1999, but expected them to become unnecessary after the relevant software acquired better capabilities. That made the page author responsible for today's visitor while leaving a visible work order for browser and assistive-technology makers. The patch went where a page could actually be changed; the upgrade belonged to the machinery behind it.

The five examples are a guided tour of little disasters. Until user agents let people turn spawned windows off, authors should warn before opening a new window or changing the current one. Until software supported explicit associations between labels and form controls, authors had to place implicitly associated labels carefully. Until side-by-side text in layout tables could be rendered properly, authors should supply a linear alternative. Empty edit fields needed default placeholder characters until user agents handled empty controls; adjacent links needed printable separators until they were reliably distinguished.

None of this sounds heroic. That is precisely how a person ends up able to complete a form.

The larger document organized accessibility into fourteen guidelines with checkpoints ranked by effect. Priority 1 addressed barriers that could make information impossible to access for some groups; Priority 2 addressed significant difficulty; Priority 3 addressed lesser difficulty. Conformance levels A, Double-A and Triple-A corresponded to satisfying the first one, first two or all three priority sets. Guideline 10's window and label rules sat at Priority 2; its table, empty-control and adjacent-link workarounds sat at Priority 3. Even a temporary shim had a place on the checklist.

WCAG 1.0 also separated a relatively stable Recommendation from a Techniques document expected to change more often. That arrangement suited the interim drawer. A durable principle could say a person must be able to understand and navigate a page, while the practical recipe responded to the browser in front of them. The specific fixes reveal the state of the Web in 1999 more sharply than a slogan about access ever could: a new window could disorient, a label could lose its field, and a neat pair of columns could arrive as nonsense when read linearly.

The standard's bargain was blunt. The people writing pages could not outsource today's reader to tomorrow's browser. The software vendors could not treat authors' workarounds as a permanent excuse to leave their machines unfinished. Guideline 10 put temporary carpentry into a formal Recommendation, then left the workshop door open for the day the proper hinges arrived.