- From: Gregg C Vanderheiden <greggvan@umd.edu>
- Date: Sat, 15 Apr 2017 14:52:33 -0400
- To: Dick <wayneedick@gmail.com>
- Cc: "w3c-waI-gl@w3. org" <w3c-wai-gl@w3.org>
- Message-Id: <AA810ABB-887D-48AB-944C-F258DD73B7D1@umd.edu>
Hi Dick This isnt my language — but what I think they are doing is making an SC that is testable — and proves that the basic operations can be done. Take the item that says that you can switch to another font. You can’t test switching to ALL fonts (where is the list of ALL) or ANY font (again where is the list of all so that you can test that it works with ANY) — so you test it by just showing that you can change to another ( 1 other) font. You can’t name it since you don’t know the platform they are on. If you can change fonts and it doesn’t crash then you know that changing fonts won’t crash it. Ditto for the rest items. G Gregg C Vanderheiden greggvan@umd.edu > On Apr 15, 2017, at 9:57 AM, Wayne Dick <wayneedick@gmail.com> wrote: > > How will being able to switch to one font family help? I really don't understand it. What is the justification of this limitation in terms of helping anyone. What family? > > Again how does the ability to switch to one color combination help anyone. What color? > > Let's pick H. > > How do either of these help users pick colors and fonts that lie outside a small list provided by developers? > > I can see ruling out ridiculous color combinations that don't have enough contrast for visibility. I can see ruling out fonts with extreme dimensions for the em unit (16px). > > Now there are many sites that can handle 200% enlargement and break at 225%. > > As stated I cannot see why a developer would not design a sight to enable a change to one different color and one different font. What language prevents that narrow interpretation? > > Is that narrow interpretation it? > > These SCs just do not make any sense.
Received on Saturday, 15 April 2017 18:53:10 UTC