W3C home > Mailing lists > Public > public-low-vision-a11y-tf@w3.org > April 2017

Re: Special fonts don't matter for font-family change.

From: Wayne Dick <wayneedick@gmail.com>
Date: Thu, 6 Apr 2017 06:42:23 -0700
Message-ID: <CAJeQ8SDS2RtqAdrODi-56-WiDa5JNUkPjyV3uzLmc_fx=4HUtg@mail.gmail.com>
To: Jonathan Avila <jon.avila@ssbbartgroup.com>
Cc: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
​If I am not mistaken the problem is: Can an author test if all fonts can
be mapped into the font of the user's choice. Also, are the space
disruptions sever enough to prevent usability.

At this point we do not need to demonstrate ​finished AT that can be
selective enough to change fonts the user wants changed and not change
fonts the user wants to stay unchanged. That is something that can happen
once we ensure a change can occur.

The author or accessibility tester does not need to use AT to determine if
the font changed. They only need to check that every occurrence of text can
change.  In HTML based pages that should mean: Can it be changed with CSS.

CSS will never be sophisticated enough to perform an intelligent
transformation for users. That will take a procedural programming language
like JavaScript. That will be the actual AT. The JavaScript will have need
the ability to change with CSS to work. But the output of the JavaScript
will will be able to determine what should be changed and what should not
much better.

The author and accessibility tester only need to test that the change can
be made with the style language.

Now, images are something different. If you know it is an image display the
alt-text. If you cannot determine an images is being used, 1.3.1 fails.

Am I missing something?
Received on Thursday, 6 April 2017 13:43:37 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 27 April 2017 14:44:34 UTC