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: Kim Patch <kim@redstartsystems.com>
Date: Sun, 13 Dec 2015 21:46:30 -0500
Message-ID: <566E2D86.2060406@redstartsystems.com>
To: Jim Allan <jimallan@tsbvi.edu>, Greg Lowney <gcl-0039@access-research.org>
CC: WAI-ua <w3c-wai-ua@w3.org>
+1
On 12/12/2015 11:38 PM, Jim Allan wrote:
>
> +++1
> Excellent!
>
> On Dec 12, 2015 5:32 PM, "Greg Lowney" <gcl-0039@access-research.org 
> <mailto: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.
>

-- 
___________________________________________________

Kimberly Patch
President
Redstart Systems, Inc.
(617) 325-3966
kim@redstartsystems.com

www.redstartsystems.com <http://www.redstartsystems.com>
- making speech fly

Blog: Patch on Speech
+Kim Patch
Twitter: RedstartSystems
www.linkedin.com/in/kimpatch <http://www.linkedin.com/in/kimpatch>
___________________________________________________
Received on Monday, 14 December 2015 02:47:01 UTC

This archive was generated by hypermail 2.3.1 : Monday, 14 December 2015 02:47:02 UTC