RE: Reminder: Text customization in browsers

Hi Shawn, sorry I'm still visiting family in Dorset with very little access to the Internet but yes please do feel free to put them on the public list and sorry for this terribly-formatted post. Silas


-----Original Message-----
From: Shawn Henry <shawn@w3.org>
Sent: 9 January 2014 21:11
To: Silas S. Brown <ssb22@cam.ac.uk>
Subject: Reminder: Text customization in browsers

Hi Silas,

I'm resending below in case it got lost in the holiday post. :-)

All the best,
~shawn


-------- Original Message --------
Subject: Re: Text customization in browsers
Date: Tue, 24 Dec 2013 07:42:29 -0600
From: Shawn Henry <shawn@w3.org>
To: Silas S. Brown <ssb22@cam.ac.uk>
CC: Jeanne Spellman <jeanne@w3.org>, Wayne Dick <wayneedick@gmail.com>

Thank you so much for taking the time to review the text customization requirements in UAAG, Silas!

I have one reply below.

Would you be willing to submit your comments to the formal (publicly-archived) comment list? It is <public-uaag2-comments@w3.org>

Also, if you want to review more, the companion document (which is informative, not a normative standard) is at <http://www.w3.org/TR/IMPLEMENTING-UAAG20/>

Happy holidays!

~Shawn


On 12/21/2013 9:29 AM, Silas S. Brown wrote:
> Thanks Shawn.  It's good work.
>
> 1.4.3 and 1.4.6 BOTH mention "line spacing" - does it really
> need to be listed twice?  With different settings ranges?  or
> maybe I've misunderstood (which means others might misunderstand).

Shawn reply:

The issue is that some user agents might not be able to easily provide the wide range of line spacing settings. Therefore, 1.4.3. at Level AA says users can set "Line spacing of at least 1.0, 1.3, 1.5, and 2.0 times the font height". Whereas 1.4.6. at Level AAA says users can set "Line spacing between 0.7 and 3.0 times the font height, at increments of 0.10". This way user agents (such as e-book readers) can provide basic line spacing at Level AA, even if they cannot easily meet the Level AAA requirement.

Maybe more needs to be said about that in the companion document: "Implementing UAAG 2.0: A guide to understanding and implementing User Agent Accessibility Guidelines 2.0" at <http://www.w3.org/TR/IMPLEMENTING-UAAG20/>

<end reply>

>
> I'm not sure if 1.7.4 (Save Copies of Stylesheets) is really needed.
>
> 1.8.7 (Reflow Text) - I think there's a possible
> misunderstanding here with the wording "text content in a
> graphical top-level viewport".  Some developer might think "oh,
> if it's only about text in a top-level viewport, then it doesn't
> apply to text in a table (or other layout device) within that
> viewport", which is not ideal especially if such layout device
> is being used unnecessarily.  Maybe add something like "This
> applies even if such text is included within other structures"?
>
> Re 1.8.11 (Allow Top-Level Viewport Open on Request) it might
> also be worth explicitly stating that, if the user performs some
> action whose normal meaning is "open link in new tab" (for
> example, middle-click on some browsers) then it should be
> possible for users to specify that such actions must ALWAYS
> perform that meaning, and cannot be overridden by the page
> author.  Some Javascript "onClick" events manage to
> (accidentally) override middle-clicks and cause something to
> happen on the current page instead of opening a new tab.  (In
> many cases this can be worked around by right-clicking on the
> link and selecting "open in new tab", instead of
> middle-clicking, but that can be extra effort and it's an
> annoyance.)
>
> Re 2.6 - I think there definitely needs to be some easily-accessible
> switch to temporarily STOP all event handlers, then start them again
> later.  Some websites have badly-implemented scripts that try to do
> fancy things as you move the mouse over elements, and these play
> badly with user stylesheets.  For example, eBay's feedback mechanism
> can go horribly wrong at very large zoom levels.  You move the
> mouse over the "5 star" rating, but as you do so, it adds an
> extra element into the text, causing the whole thing to reflow
> (the designers weren't expecting it to reflow - they didn't
> think it might be zoomed), and the reflow takes the star
> somewhere else so it is no longer under the mouse pointer, and
> this causes another event, undoing the first event, but then the
> star is again under the pointer, and so on ... result is a
> rapidly-flickering control, and less than 50/50 chance of it being
> activated when you click.  Only workaround is to zoom out or
> increase the window size, but I wish I had a button that says
> "stop all event handlers until my next click" (bonus points if
> the user agent can AUTOMATICALLY detect the "rapid-fire" situation
> and turn them off until the next click).
>
> Re 2.9.1 (Adjustable Time Limits) "the user can extend the time
> limits", would it be a good idea to add "indefinitely"?  Just
> in case some developer thinks "just let them have a 50% extension".
>
> Thanks.
>
> Silas
>

Received on Monday, 13 January 2014 14:08:23 UTC