RE: Agenda: Low Vision Task Force 8 Nov 2018

HI Jim,

I can’t make it today, but just on this agenda bit:
>  what got morphed and missed the point

I’d say what got morphed and didn’t cover the original user-need completely.

It is about going back to the original user-needs, seeing what is better covered now, and seeing what is left.

Anything that isn’t covered is potentially an SC for 2.2, but also this will be needed for silver, so it’s useful in anycase.

For example (making it up on the spot):
Some users need to transform large areas of content so that they:

  1.  Increase in size, upto 100px tall text
  2.  Reflow the layout, staying within a viewport (often a reduced resolution screen such as 640px wide)
  3.  Remove / reset author-set margins around headings and paragraphs.
  4.  Change the colours, so the background is a user-prefered colour, and the foreground has high contrast.
  5.  Change the font-family.
  6.  Change the letter and word spacing.
  7.  Style certain elements (e.g. bold) to a user-preference so they are a different colour instead of different size.

So we can then look at those user-needs and say things like (hypothetically):

  *   Reflow covers 2 well, and in combination with text-size covers 1 to some extent. In practice we could do with a minimum text-size.
  *   The user-agent side is not useful for 4 & 7 yet, so that isn’t coved.
  *   There is a scenario where 4 is undermined by sites, that’s really important to address.

So the process would be:

  1.  TF sets up the user-needs and current coverage, highlighting the most important gaps post 2.1.
  2.  TF + people from AG collaborate on what tests could be created for each.
  3.  AG + TF works on potential criteria.

Hope that helps,

-Alastair