Re: [charmod-norm] Terminology examples fonts

On 10/25/2017 9:27 PM, Addison Phillips wrote:
>
> We avoid using color alone for accessibility reasons (color 
> blindness). We need to have two variations when using color (hence 
> red-underlined and blue-with-gray-background).
>
My suggestion was to explain some stuff in terms of where the text 
occurs (inside <>, outside "" etc.) so that some of the color/format 
distinctions become non-essential; if that is done, they can be made 
subtle but redundant. A color blind reader will not be lost, and all 
readers won't have to struggle with so much distraction (like all those 
underlines).

I think the element names would work for that, like syntax characters 
they could stay unmarked. Then you only need to distinguish 
reserved/user-defined attribute identifiers from full text.

> The font defintion in the stylesheet is pretty monospaced:
>
>     font-family: Consolas, "Andale Mono", "Lucida Console", "Lucida
>     Sans Typewriter", Monaco, "Courier New", NoToFu, monospace;
>
> The only font in there that isn't actually a monospaced font is 
> "NoToFu", which is our fallback face for missing glyphs and doesn't 
> draw here. Are you sure the text doesn't just look prettier while 
> being in a mono font on iPad?
>
> I am open to suggestions, but this is a difficult example to build by 
> itself. I could, as you suggest, make a graphic just to be sure 
> everyone gets the picture---as it were ;-).
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub 
> <https://github.com/w3c/charmod-norm/issues/121#issuecomment-339547738>, 
> or mute the thread 
> <https://github.com/notifications/unsubscribe-auth/ANbTHqkCSL3B5c1FlK7D8JpzX55U7YuNks5swApGgaJpZM4P-BBd>.
>



-- 
GitHub Notification of comment by asmusf
Please view or discuss this issue at https://github.com/w3c/charmod-norm/issues/121#issuecomment-339551380 using your GitHub account

Received on Thursday, 26 October 2017 04:57:43 UTC