- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Wed, 22 Mar 2017 17:30:07 +0000
- To: Laura Carlson <laura.lee.carlson@gmail.com>
- CC: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
HI Laura,
I missed most of the good bits of the call yesterday, but I noticed that JF, MichaelC and others were supportive of dropping the specific values for font & colour?
I’d be happy with that, but there would be some objections to over-rule as it is either there or not, I don’t see a compromise position.
The “mechanism” language does lead people to think it requires a widget. Is this what we want?
For the LVTF, there are a couple of assumption it would be good to get agreement on, and the first is:
If the styles of a site prevent you from usefully adapting text, would you want a widget on the site to enable that?
I’ve been leaning towards ‘no’, as if people provide a widget, it will be based on their colours/fonts rather than the ones you want.
Also, I think we had changed the SC so that it works in a PDF context as well, is that correct?
I have replied on github, but I wanted to check my assumptions!
Thanks,
-Alastair
Received on Wednesday, 22 March 2017 17:30:43 UTC