Mechanism Disclaimer

I am proposing the following change to Font, Issue 79

Only look at the disclaimer, but factor in Font-Family as a 'mechanism'
disclaimer. Is it too general? Should we have disclaimers at all and insist
developers code access? Would you prefer, a mechanism exists, followed by
the disclaimer?

SC: Font

"The user can change the font family down to the element level, to any font
family available to the user agent with the following exception.
*If no mechanism exists to change font family on any user agent for the
target technology, then the author has no responsible to create one. *"


Bold added to emphasize the disclaimer language in question.

I would appreciate help. Please keep your answers as short as possible.
There are no effective mail clients or assistive technologies that support
readers with macular damage. So, I have serious difficulty reading threads.

Thank You,
Wayne