Re: I solved the Adapting Text Problem

Wayne,
I don’t think I understand, the effect of letter spacing of 0.12 is around a 30% increase in width, how can that be constrained to 5%?
We need a criterion that is simple to apply & test, if content were capable of increasing width-ways by 10%, I think that would be well tested by applying 0.05em letter spacing.
What’s wrong with simply asking content to be capable of that?
Cheers,
-Alastair


From: Wayne Dick <wayneedick@gmail.com>
Date: Wednesday, 12 July 2017 at 17:57
To: Laura Carlson <laura.lee.carlson@gmail.com>
Cc: Alastair Campbell <acampbell@nomensa.com>, LVTF - low-vision-a11y <public-low-vision-a11y-tf@w3.org>
Subject: Re: I solved the Adapting Text Problem

Just this last suggestion. Alastair, I'm sorry I did not translate my stuff to content language. We need to add a 5% width limit on the effect of all changes as given below.
...

  1.  line spacing (leading) to at least 1.5 (space-and-a-half)
  2.  spacing between paragraphs to at least 2 (two spaces) larger than the line spacing
  3.  letter spacing (tracking) to at least 0.12 em
  4.  word spacing to at least 0.16 em
Add the following overall constraint after point 4:

"The total increase in pixel width of effected fields cannot exceed 5%."
This means that authors must allow for 5% growth in width, but no more. That is the only requirement put on authors. It is not trivial. It's a good compromise.

For a user to qualify for protection under the SC, the font size and possibly font family must be adjusted to fit [field size]+5%. We computed how to do that meaning users can meet the upper bound and still be accommodated.
As far as line height is concerned we cannot solve that because line-height of 1.5 will be 1.5*(font-size). Reducing to 14px will cut that to 1.3 real growth, but that is the best we can get.
One last thing regarding growth of width. If the authors leave the 5% pad and users follow the limit, the change will never force word wrapping. I know this because the loop test for the fontStats app is the point where word wrap is triggered. That means the only growth in height will result from line spacing.
I think this fixes everything. And I'm just going to trust you on font-family even if it scares me.

Nice working with this team,
Wayne

On Wed, Jul 12, 2017 at 7:33 AM, Laura Carlson <laura.lee.carlson@gmail.com<mailto:laura.lee.carlson@gmail.com>> wrote:
Hi Alastair and Wayne,

I think in the future we may likely have to change the values to
something like you are suggesting. I really appreciate your hard work.

But the time being can we please table that discussion to get what we
have out to the public for comment?

If possible, can  try to get the SC into the editor's draft before we
make changes to the values that will take weeks or months to explain
to everyone and come consensus on? We are running out of time.

Thank you for your consideration.

Kindest Regards,
Laura


On 7/12/17, Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>> wrote:
> Hi Wayne,
>
> That’s good, but it isn’t a solution until it is a content requirement.
>
> I *think* a 10% increase in text-width is equivalent to letter spacing of
> 0.05em:
> https://alastairc.ac/tests/letter-spacing.html

>
> I’d suggest going for that level to start with, 5% as a useful fall-back
> position.
>
> What you’ve created is a great basis for a user-agent tool that allows a
> user to customise what they want up to that limit, but it doesn’t help
> designers/developers directly.
>
> What we need for the content is a vertical and horizontal buffer size.
> Line-height (and possibley paragraph margin) is vertical, letter-spacing is
> good for consistent horizontal increases, so we’d have two or three bullets
> such as:
>
>
>   *   line spacing (leading) of text to at least 1.5 times the font size
>   *   letter spacing (tracking) to at least 0.05 of the font size
>   *   spacing (leading) between paragraphs to at least 2 times the font
> size
>
> That brings us back to applying it to all text, so I dropped the ‘blocks of
> text’ phrasing.
>
> Cheers,
>
> -Alastair
>
>
> From: Wayne Dick <wayneedick@gmail.com<mailto:wayneedick@gmail.com>>
> Date: Wednesday, 12 July 2017 at 08:52
> To: LVTF - low-vision-a11y <public-low-vision-a11y-tf@w3.org<mailto:public-low-vision-a11y-tf@w3.org>>
> Subject: I solved the Adapting Text Problem
> Resent-From: LVTF - low-vision-a11y <public-low-vision-a11y-tf@w3.org<mailto:public-low-vision-a11y-tf@w3.org>>
> Resent-Date: Wednesday, 12 July 2017 at 08:53
>
> Two things for the group.
> At
> http://nosetothepage.org/ExactRelationship.docx

> you will find a solution to our numeric difficulties regarding Adapting
> Text. It was a hard problem.
> To understand the method you will probably need to play with my string
> length app, fontStats.
> ]
> http://nosetothepage.org/fontStats/FDSDoc.html

> My proposal is this. The user can change letter and line spacing as much as
> they like but they cannot increase text length by more than 5%.
> The problem is doable with only changing spacing with minor adjustments of
> font size. It is much easier to solve if the ability to change font family
> is available to the user.
> Wayne
>

--
Laura L. Carlson