- From: Michael McCaffrey <mray298@gmail.com>
- Date: Thu, 3 Aug 2017 23:33:42 -0400
- To: "Denis Boudreau (gmail)" <dboudreau01@gmail.com>
- Cc: David MacDonald <david100@sympatico.ca>, Jonathan Avila <jon.avila@levelaccess.com>, Robert Jolly <jolly.robert@gmail.com>, Brian Stevens <bstevens@ilsworld.com>, w3c-wai-ig@w3.org
- Message-ID: <CAA9w55UNxn1MrN-gZT=ArQ4uAhtSBS9pOx1zJLNgsaRLbxod+w@mail.gmail.com>
Agree with Denis. Good approach but, thinking through the customer journay, this could be difficult for some to find."Tucking under the settings" is a quick fix, as you said. I think this would work in the interm while you're working on the long-term fix. On Thu, Aug 3, 2017 at 9:59 PM, Denis Boudreau (gmail) < dboudreau01@gmail.com> wrote: > While the above is all true, I would argue that regardless of how "WCAG > compliant" a contrast switcher could be made inside an equally "WCAG > compliant" modal, hiding a control in this way will always make it harder > to discover for some users than just clearly displaying it in plain sight > for everyone to find. I invite you to not only consider how accessible the > feature will be, but also how usable its implementation will be. IMHO, > hiding stuff behind modals is rarely the best way to go about designing for > inclusion. My $0.05 CDN. > > > > /Denis > > -- > Denis Boudreau, > Accessibility, user experience & inclusive design > Cell: +1-514-730-9168 <(514)%20730-9168> > Email: dboudreau01@gmail.com > Twitter: @dboudreau <http://www.twitter.com/dboudreau> > > On 2017-08-03 7:47:38 PM, David MacDonald <david100@sympatico.ca> wrote: > Yes... > > Cheers, > David MacDonald > > > > *Can**Adapt* *Solutions Inc.* > > Tel: 613.235.4902 <(613)%20235-4902> > > LinkedIn > <http://www.linkedin.com/in/davidmacdonald100> > > twitter.com/davidmacd > > GitHub <https://github.com/DavidMacDonald> > > www.Can-Adapt.com <http://www.can-adapt.com/> > > > > * Adapting the web to all users* > * Including those with disabilities* > > If you are not the intended recipient, please review our privacy policy > <http://www.davidmacd.com/disclaimer.html> > > On Thu, Aug 3, 2017 at 1:33 PM, Jonathan Avila <jon.avila@levelaccess.com> > wrote: > >> Ø As long as the panel conforms to WCAG it's OK. >> >> >> >> And in my opinion the setting button to activate the panel. I.e. the >> path to reach the panel. >> >> >> >> Jonathan >> >> >> >> Jonathan Avila >> >> Chief Accessibility Officer >> >> *Level Access, inc.* (formerly SSB BART Group, inc.) >> >> jon.avila@levelaccess.com >> >> 703.637.8957 <(703)%20637-8957> (Office) >> >> Visit us online: Website <http://www.levelaccess.com/> | Twitter >> <https://twitter.com/LevelAccessA11y> | Facebook >> <https://www.facebook.com/LevelAccessA11y> | LinkedIn >> <https://www.linkedin.com/company/level-access> | Blog >> <http://www.levelaccess.com/blog/> >> >> *Looking to boost your accessibility knowledge? Check out our free >> webinars!* <http://www.ssbbartgroup.com/webinars/> >> >> >> >> The information contained in this transmission may be attorney privileged >> and/or confidential information intended for the use of the individual or >> entity named above. If the reader of this message is not the intended >> recipient, you are hereby notified that any use, dissemination, >> distribution or copying of this communication is strictly prohibited. >> >> >> >> *From:* David MacDonald [mailto:david100@sympatico.ca] >> *Sent:* Thursday, August 03, 2017 1:04 PM >> *To:* Robert Jolly >> *Cc:* Brian Stevens; w3c WAI List >> *Subject:* Re: Can a contrast switcher control be inside a modal >> settings window? (Success Criteria 1.4.3) >> >> >> >> As long as the panel conforms to WCAG it's OK. >> >> >> Cheers, >> David MacDonald >> >> >> >> *Can**Adapt* *Solutions Inc.* >> >> Tel: 613.235.4902 <(613)%20235-4902> >> >> LinkedIn >> <http://www.linkedin.com/in/davidmacdonald100> >> >> twitter.com/davidmacd >> >> GitHub <https://github.com/DavidMacDonald> >> >> www.Can-Adapt.com <http://www.can-adapt.com/> >> >> >> >> * Adapting the web to all users* >> >> * Including those with disabilities* >> >> >> >> If you are not the intended recipient, please review our privacy policy >> <http://www.davidmacd.com/disclaimer.html> >> >> >> >> On Thu, Aug 3, 2017 at 11:37 AM, Robert Jolly <jolly.robert@gmail.com> >> wrote: >> >> Hi Brian, >> >> >> >> My understanding of this is your approach is OK, as long as it’s it’s >> understood that the contrast settings are available in the settings >> panel/modal. >> >> >> >> It’s good to hear you’re working on a design with good contrast >> integrated. :) >> >> >> >> HTH >> >> -Robert >> >> >> >> ----- >> >> >> >> Robert Jolly >> >> Sr. Web Accessibility Strategy Consultant >> >> knowbility.org | @knowbility <https://twitter.com/knowbility> >> >> *Equal access to technology for people with disabilities* >> >> >> >> >> >> >> >> On Aug 3, 2017 at 9:14 AM, Brian Stevens <bstevens@ilsworld.com> wrote: >> >> >> >> Hello, >> >> >> >> We need to meet contrast requirements for 1.4.3 - Level AA. My team is >> considering using a style switcher as a temporary fix. Since our web-app >> already has a modal settings window (which is contrast compliant), we >> prefer to place the switcher under our settings. The only problem is, I >> can’t figure out whether tucking it under settings is allowed. The relevant >> techniques (G174 and C29) just say that the link or control needs to be “on >> the page.” Technically the settings window exists on the same page. Is that >> good enough? Is there some precedent for this? >> >> >> >> Here are the relevant techniques: >> >> G174: Providing a control with a sufficient contrast ratio that allows >> users to switch to a presentation that uses sufficient contrast >> <https://www.w3.org/TR/WCAG20-TECHS/G174.html> >> >> C29: Using a style switcher to provide a conforming alternate version >> <https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/C29> >> >> >> >> Side-note: For the future, we are planning a contrast-compliant redesign, >> but we need a short-term solution to meet a deadline. >> >> >> >> Thanks, >> >> Brian Stevens >> >> >> > >
Received on Friday, 4 August 2017 03:34:09 UTC