Re: MS03 - 1.4.1 Basic Text formating

Is it our policy now to delete things that lack two implementations, or to merely list them as At Risk and make the determination at a later draft?

If we do delete it, can we list it as a recommendation?

What if it's possible to comply by using Stylish, GreaseMonkey, or similar add-ins? (You can come close using Stylish to apply something like * { line-height: 200%; }, but that admittedly simplistic solution works very inconsistently.)

-------- Original Message --------
Subject: MS03 - 1.4.1 Basic Text formating
From: Jim Allan <jimallan@tsbvi.edu>
To: WAI-ua <w3c-wai-ua@w3.org>
Date: 1/6/2015 9:34 AM
> Was doing document forensics with Jeanne, and in discussion got to thinking about 1.4.1
>
>  
> 1.4.1 Basic text formatting (Globally): The user can globally set all of the following characteristics of visually rendered text content: (Level A)
> * Text scale with preserved size distinctions (e.g. keeping headings proportional to main font)
> * Text color and background color, choosing from all platform color options
> * Font family, choosing from all installed fonts
> * Line spacing, choosing from a range with at least three values
>
> I don't believe any browser allows (provides a UI to easily set) except via CSS for
> * Line spacing, choosing from a range with at least three values
>
> the other 3 bullets have UI for easily setting these in desktop browsers. the mobile browsers I checked, Android and Chrome (Android), only allow font size change and zoom override.
>
>
> Propose removing the last bullet from 1.4.1
>
>
> -- 
> http://www.tsbvi.edu <http://www.tsbvi.edu>Jim Allan, Accessibility Coordinator & Webmaster
> Texas School for the Blind and Visually Impaired
> 1100 W. 45th St., Austin, Texas 78756
> voice 512.206.9315    fax: 512.206.9264 http://www.tsbvi.edu/
> "We shape our tools and thereafter our tools shape us." McLuhan, 1964

Received on Thursday, 8 January 2015 05:24:37 UTC