- Important note: This Wiki page is edited by participants of the User Agent Accessibility Guidelines working group (UAWG). It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.
Guideline 1.4 Text Customization Proposal
Contents
UAAG 2.0 text customization recommendations
Guideline 1.4
All of the Success Criteria under Guidelines 1.4 allow users to override the text characteristics specified by authors, and override user agents defaults. [<- new text recommendation to keep from having to repeat it in every SC below]
[In Implementing say something like: Guideline 1.4 addresses text configuration and the success criteria specifies text characteristics that users need to be able to configure. Several characteristics are in different success criteria because ... @@ the more important characteristics are at higher levels... some are global, some are element-level... things that are easier to do on all platforms at higher level and harder to do in some platforms at lower level...]
[For Implementing: it is probably more efficient and equally effective to have examples that cover multiple SC under Guideline 1.4, instead of different examples for each SC.]
[JS 09/24/2013] we need a Note for 1.4 that explains that these SC can be met by user stylesheets when user stylesheets are available, but need to be met using other techniques when user stylesheets aren't available.
(Level A)
1.4.1 The user can globally set all of the following characteristics of visually rendered text content:
- Text scale (the general size of text)
- Text color (foreground and background), choosing from all platform color options
- Font family, choosing from all platform fonts
(Level AA)
1.4.2. The user can set all of the following characteristics of visually rendered text content for headings, main text, and other elements:
- Text scale (the general size of text)
- Text color (foreground and background), choosing from all platform color options
- Font family, choosing from all platform fonts
1.4.3. The user can globally set all of the following characteristics of visually rendered blocks of text:
- Line spacing of at least 1.0, 1.5, and 2.0.
- Character spacing
- Word spacing
- Text style (underline, italic, bold)
- Justification (undoing full justification)
1.4.4. Printing reflowed, zoomed, and configured text: Blocks of text that have been reflowed according to SC 1.8.12 (including text that is zoomed) and text that is configured according to Guideline 1.4 can be printed with those [configurations|customizations|settings].
(Level AAA)
1.4.5 The user can set all of the following characteristics of visually rendered text content for headings, main text, and other elements:
- Text style (underline, italic, bold)
- Margins (for example, space above headings, indentation of lists)
- Borders
1.4.6 The user can globally set all of the following characteristics of visually rendered blocks of text:
- Line spacing between 0.7 and 3.0, at increments of 0.10.
- Justification (setting left, right, or full)
- Capitalization (undoing all caps)
- Hyphenation
- Margins (to clear clutter away from blocks of text)
1.4.7. Export text with semantic markup: @@ ...
Already covered elsewhere in UAAG
1.8.3 Resize Viewport: The user can resize viewports within restrictions imposed by the platform, overriding any values specified by the author. (Level AA)
1.8.6 Zoom: The user can rescale content within top-level graphical viewports as follows: (Level A) Zoom in: to 500% or more of the default size...
1.8.12 Reflow Text: The user can specify that when text content in a graphical viewport reflows so that one dimension of the content blocks of text fit within the height or width of the viewport, overriding any values specified by the author. (Level A) [<- edits from UAAG f2f pending I18N OK]
Note: Users should not have to scroll horizontally to read blocks of text, including text that is zoomed. [<- important new requirement clarification.]
Note: Users should not have to scroll from the bottom of one column to the top of another column to read blocks of text. [<- important new requirement clarification.]
internal notes
[fyi, WCAG defines blocks of text as "more than one sentence of text".]
[Wayne confirmed: With the requirements above for element-level customization, users do not need this success criteria: "Preserving Size Distinctions: The user can specify whether or not distinctions in the size of rendered text are preserved when that text is rescaled (e.g. headers continue to be larger than body text). (Level A)"]
[Notes for gathering implementation evidence:
- Most browsers support all these SC through user style sheets.
- Microsoft Word and most other word processing software support all SC.
- VIP PDF-Reader supports some of these SC. It provides zoom with reflow (which avoids horizontal scrolling and column scrolling) in a window of adjustable width ("resize viewport" in UAAG language); line, word, and character spacing at seemingly-unlimited settings; and a range of fonts of different types (including serif, sans serif, and fonts specifically designed for people with low vision and dyslexia).
- EPUB-based eBook Readers support all these SC through user style sheets.
- ...]