Re: Mechanism Disclaimer

Josh asked:

> Is there a worry within the LVTF that font-family and related CSS type or code level changes may not be perceived as a 'mechanism' - and therefore is not sufficient to satisfy some proposed new SCs?

It is that the ‘mechanism’ language implies authors should create it. If you look through font-family, linearise, spacing, & colors; almost everyone assumes that is the case.

It would help if we could build in the assumption that it is allowing the user to achieve something, for example:

“Changing the font-family used on a web page does not cause loss of content or functionality.”

Techniques for that will include things like not relying on font-icons to convey important information.



Received on Friday, 20 January 2017 11:01:30 UTC