Re: Prototype Silver SC

I really would like to remove the comment "return to user stylesheets". The
article was written when user style sheets were a viable possibility.

Element Level Personalization is a much deeper concept than stylesheets. It
recognizes the need to style the principle language elements differently to
aid visual navigation. Also, things like text boxes are often more rigid
with regard to text width, so controlling text width for <input> elements
makes sense, while controlling width dilation caused by change in text
spacing or font family is harmless.

Yes, effective access for people with low vision requires finely granulated
access to typographic parameters. The method today is through JavaScript.

Although, style sheets work in a pinch.

User stylesheets are assistive technology even if the AG doesn't recognize
them.

Wayne

On Tue, Jul 17, 2018 at 4:21 PM Alastair Campbell <acampbell@nomensa.com>
wrote:

> Hi Jim,
>
>
>
> This has been on my mind, I think for the purpose of silver it would be
> good to pick one that is high on the user-benefit scale, and high on the
> difficulty scale as well, something over-lapping with user-agent issues.
>
>
>
> Perhaps personalisation, but a specific example of that?
>
>
>
> E.g. User can change the foreground and background colour of text content.
>
>
>
> Printing is probably a similar scale, but I wasn’t sure which would be of
> more benefit.
>
>
>
> Cheers,
>
>
>
> -Alastair
>
>
>
>
>
> *From:* Jim Allan <jimallan@tsbvi.edu>
> *Sent:* 17 July 2018 20:25
> *To:* public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>;
> Jeanne Spellman <jspellman@paciellogroup.com>
> *Subject:* Prototype Silver SC
>
>
>
> Last week, the Silver Task Force asked the LVTF for SC that did not make
> it in to WCAG21. Several items were mentioned, see below. Which is our #1
> choice
>
>    - Browser exemptions/issues
>
>
>    -  1.4.11 [1] -  "... where the appearance of the component is
>       determined by the user agent and not modified by the author;" the exemption
>       for contrast of native active elements (form element, focus ring, media
>       controls, etc.) failing WCAG20 3:1 contrast threshold
>       - 1.4.13 [2] - "Exception: The visual presentation of the
>       additional content is controlled by the user agent and is not modified by
>       the author."  the exemption for 'title' attribute
>
>
>    - Element Level Customization [3] - user interface for UA to allow
>    override of many values. Closely related to Personalization. It is the
>    super set of the proposed SCs on font size, family, color,
>    justification, hyphenation, etc. Also know as Return of User Stylesheets
>    - Printing [4] - documents printed do not loose content. Huge
>    discussion - much having to do with testing. Closely related to this is the
>    user being able to print what is on the screen after all of the font,
>    spacing, and sizing changes have been applied. Would be nice not to have to
>    write a print style sheet. If I zoom a page a bit to make it easier to
>    read, I want to print at that size.
>
> ​
> <https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Issues_to_be_addressed_in_Silver>
> 1. https://www.w3.org/TR/WCAG21/#non-text-contrast
>
> 2. https://www.w3.org/TR/WCAG21/#content-on-hover-or-focus
>
> 3.
> https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Element_Level_Customization
>
> 4. https://github.com/w3c/wcag21/issues/76    [Printing SC]
>
>
>
> LVTF issues for Silver
> <https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Issues_to_be_addressed_in_Silver>
>
> --
>
> Jim Allan, Accessibility Coordinator
>
> Texas School for the Blind and Visually Impaired
> 1100 W. 45th St., Austin, Texas 78756
> voice 512.206.9315    fax: 512.206.9452 http://www.tsbvi.edu/
>
> "We shape our tools and thereafter our tools shape us." McLuhan, 1964
>