W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > October to December 2015

Re: IER for 1.4.5 Default to platform text settings

From: Jim Allan <jimallan@tsbvi.edu>
Date: Sat, 12 Dec 2015 22:38:24 -0600
Message-ID: <CA+=z1WmjFt90LVuYzb4n62UcASUndEWmfRQMOuFbX4TdSOczxQ@mail.gmail.com>
To: Greg Lowney <gcl-0039@access-research.org>
Cc: WAI-ua <w3c-wai-ua@w3.org>
On Dec 12, 2015 5:32 PM, "Greg Lowney" <gcl-0039@access-research.org> wrote:

> Greetings! Per our most recent conference call, here are draft Intent,
> Examples, and Related Resources sections for 1.4.5.
> 1.4.5 Default to platform text settings: The user can specify that
> platform text settings be used as the default values for text
> configuration. (Level AA)
> *Applies to:*
> *UA user interface*, *Content user interface*, *Configuration settings*
> *Typically Implemented in:*
> browser, reader
> *Intent of Success Criterion 1.4.5:*
> Some people find that it easier to read when text is displayed using a
> specific set of attributes, such as font, size, text and background colors,
> or spacing. While some requirements are most common (such as larger text),
> the combination that works best will vary from one individual to the next.
> They will typically want these setting applied to both user interfaces and
> rendered content. On many platforms the user can adjust platform preference
> settings to meet their needs, and these settings are available to
> applications such as user agents. Each applications can then provide a
> simple user option to follow those settings, rather than make the user
> repeat the configuration process in every application. Likewise it means
> that if their needs change, or they discover settings that work better for
> them, they can make that change in one place rather than repeating it over
> and over again. This also makes it easier for the user to maintain a
> consistent presentation across all their applications. If the user relies
> on these settings, they can instruct the user agent to override
> author-specified text attributes (per other success criteria in *Guideline
> 1.4*).
> *Examples for Success Criterion 1.4.5:*
> Lee has low vision from albinism and when the background is white, it is
> hard for her to read and hurts her eyes. She changes the colors in her
> operating system to white text on a black background. However, many web
> pages specify their own colors, so she adjusts the user preferences in her
> browser to always use the system colors, regardless of how the pages are
> authored.
> Erin has dyslexia and finds it easiest to read sans serif text with
> relatively low brightness and color differences between text and its
> background. She changes the font and colors in her operating system’s
> Control Panel to work well for her. These settings are automatically
> reflected in her browser’s user interface. However, many web pages specify
> their own colors, so she adjusts the user preferences in her browser to
> always use the system fonts and colors, regardless of how the pages are
> authored.
> Sebeeya has low vision. She finds text easiest to read at 16 pt Palatino
> and adjusted her operating system’s preference settings to use these for
> its menus and other controls. She appreciates that her browser
> automatically respects these settings by displaying its menus and controls
> in this same style.
> *Related Resources for Success Criterion 1.4.5:*
> *Guideline 1.4 Provide text configuration* discusses additional success
> criteria about options for text presentation.
> *Guideline 2.6 Preference settings discusses* additional success criteria
> about configuring preference settings.
Received on Sunday, 13 December 2015 04:38:54 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 13 December 2015 04:38:55 UTC