- From: Jim Allan <jimallan@tsbvi.edu>
- Date: Thu, 10 Nov 2016 07:32:32 -0600
- To: Alastair Campbell <acampbell@nomensa.com>
- Cc: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
- Message-ID: <CA+=z1WntXDaG7ioG_wSDtBDfpkiWVwGEuSk6fAtnj8z3j0=YUg@mail.gmail.com>
Great news. Always good to have the view of folks who have to implement an SC. On Nov 10, 2016 4:22 AM, "Alastair Campbell" <acampbell@nomensa.com> wrote: > Hi everyone, > > I disrupted our design team’s meeting this morning to run this SC past > them and see if it was understandable and feasible. > > At least with the description I gave it (primarily around what ‘important > information’ meant) they all though it was quite reasonable. > > The examples from the page were really helpful, so I think we should pick > three or four to use in the description and/or techniques. > > One of the team also provided an example of how to shrink a large icon > down whilst retaining a 3px stroke width, which I’ve added to the > description: > https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Informational_Graphic_ > Contrast_(Minimum)#Description > > The main technique for icons is stroke thickness if the contrast is > between 3 and 4.5 to 1. > > The three main techniques that jumped out as most useful for charts and > diagrams were: > - Labels, the most useful across various circumstances, especially for > avoid colour-alone issues. > - Borders, trickier to do but useful in some cases. > - Patterns, trickiest to get right as you also run into contrast issues > there unless you have labels. > > There are some examples (like topographical maps) where you cannot have > strong contrasting lines, so the key there would be to convey what is > needed through labels or explanations outside of the graphic. E.g. label > the top of a hill, or explain the implications in text. > > Most importantly nobody panicked, so I think we’re almost there! > > -Alastair > > >
Received on Thursday, 10 November 2016 13:33:07 UTC