- From: Milliken, Neil <neil.milliken@atos.net>
- Date: Fri, 1 Dec 2017 17:32:57 +0000
- To: "lisa.seeman" <lisa.seeman@zoho.com>
- CC: Bradley Montgomery <rbradley@mitre.org>, Andrew Kirkpatrick <akirkpat@adobe.com>, "W3c-Wai-Gl-Request@W3. Org" <w3c-wai-gl@w3.org>
- Message-ID: <D20F9F7C-7F9A-4AC0-991E-6EC1D5098E08@atos.net>
I’m also ok with this. Neil Milliken BA Oxon, MBA Open, FRSA, Atos Distinguished Expert Head of Accessibility & Digital Inclusion Atos T: +442036180957<tel:+442036180957> M: 07812325386<tel:07812325386> E: Neil.Milliken@atos.net<mailto:Neil.Milliken@atos.net> www: http://atos.net/iux Twitter:@neilmilliken<https://twitter.com/neilmilliken> Assistant Monika Tomczak E: Monika.Tomczak@atos.net<mailto:Monika.Tomczak@atos.net> M: +48517727304<tel:+48517727304> On 1 Dec 2017, at 07:51, lisa.seeman <lisa.seeman@zoho.com<mailto:lisa.seeman@zoho.com>> wrote: Thanks Rachel I can live with this wording All the best Lisa Seeman LinkedIn<http://il.linkedin.com/in/lisaseeman/>, Twitter<https://twitter.com/SeemanLisa> ---- On Fri, 01 Dec 2017 02:48:50 +0200 Bradley Montgomery<rbradley@mitre.org<mailto:rbradley@mitre.org>> wrote ---- I think we revised the wording we left off with at TPAC was: (Level AA) [New] A mechanism is available to postpone and suppress unnecessary interruptions and changes in content, unless they are initiated by the user or involve an emergency. Unnecessary interruptions: Secondary information, pop-ups, or actions that are not part of the workflow. Error, success, and warning messages, timeout notifications, and live updates when the purpose of the application is monitoring are not unnecessary interruptions. From: lisa.seeman [mailto:lisa.seeman@zoho.com<mailto:lisa.seeman@zoho.com>] Sent: Thursday, November 30, 2017 4:17 PM To: Andrew Kirkpatrick <akirkpat@adobe.com<mailto:akirkpat@adobe.com>> Cc: W3c-Wai-Gl-Request@W3. Org <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>> Subject: Re: can we live with the wording for Interruptions LOL....I need to sleep This (I think) Is the 2.1 AA text A mechanism is easily available<http://rawgit.com/w3c/wcag21/purpose_of_controls_changes2/guidelines/index.html#dfn-easily-available> to postpone and suppress interruptions and changes in content, unless they are initiated by the user or involve an emergency. All the best Lisa Seeman LinkedIn<http://il.linkedin.com/in/lisaseeman/>, Twitter<https://twitter.com/SeemanLisa> ---- On Thu, 30 Nov 2017 22:48:21 +0200 Andrew Kirkpatrick<<mailto:akirkpat@adobe.com>akirkpat@adobe.com<mailto:akirkpat@adobe.com>> wrote ---- Lisa, I can live with that, but that language is already in WCAG 2.0, as SC 2.2.4. Are you thinking about different language? Thanks, AWK Andrew Kirkpatrick Group Product Manager, Accessibility Adobe <mailto:akirkpat@adobe.com>akirkpat@adobe.com<mailto:akirkpat@adobe.com> <http://twitter.com/awkawk>http://twitter.com/awkawk From: "<mailto:lisa.seeman@zoho.com>lisa.seeman@zoho.com<mailto:lisa.seeman@zoho.com>" <<mailto:lisa.seeman@zoho.com>lisa.seeman@zoho.com<mailto:lisa.seeman@zoho.com>> Date: Thursday, November 30, 2017 at 14:01 To: WCAG <<mailto:w3c-wai-gl@w3.org>w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>> Subject: can we live with the wording for Interruptions Resent-From: WCAG <<mailto:w3c-wai-gl@w3.org>w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>> Resent-Date: Thursday, November 30, 2017 at 13:59 Interruptions is at Level AAA Can we live with the current wording? Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Frawgit.com%2Fw3c%2Fwcag21%2Fpurpose_of_controls_changes2%2Fguidelines%2Findex.html%23dfn-emergency&data=02%7C01%7Cakirkpat%40adobe.com%7C9f4112cf8fb64f2ae06508d53824ba11%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636476652751455732&sdata=GzSDRGCSLJBgP5ID0uIiVPmRMb0WBGaoR9Ea%2B8aGYBM%3D&reserved=0>. All the best Lisa Seeman LinkedIn<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fil.linkedin.com%2Fin%2Flisaseeman%2F&data=02%7C01%7Cakirkpat%40adobe.com%7C9f4112cf8fb64f2ae06508d53824ba11%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636476652751455732&sdata=BuSBAUtB36LbggbBtZZE2CXsOGtWbAHXTcqiAKR33dY%3D&reserved=0>, Twitter<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2FSeemanLisa&data=02%7C01%7Cakirkpat%40adobe.com%7C9f4112cf8fb64f2ae06508d53824ba11%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636476652751455732&sdata=afe73oPpK%2Fdqz4mYjBYtj1q9V2N7274ELPkOSgYoQL4%3D&reserved=0> Atos, Atos Consulting, Worldline and Canopy The Open Cloud Company are trading names used by the Atos group. The following trading entities are registered in England and Wales: Atos IT Services UK Limited (registered number 01245534), Atos Consulting Limited (registered number 04312380), Atos Worldline UK Limited (registered number 08514184) and Canopy The Open Cloud Company Limited (registration number 08011902). The registered office for each is at 4 Triton Square, Regent’s Place, London, NW1 3HG.The VAT No. for each is: GB232327983. This e-mail and the documents attached are confidential and intended solely for the addressee, and may contain confidential or privileged information. If you receive this e-mail in error, you are not authorised to copy, disclose, use or retain it. Please notify the sender immediately and delete this email from your systems. As emails may be intercepted, amended or lost, they are not secure. Atos therefore can accept no liability for any errors or their content. Although Atos endeavours to maintain a virus-free network, we do not warrant that this transmission is virus-free and can accept no liability for any damages resulting from any virus transmitted. The risks are deemed to be accepted by everyone who communicates with Atos by email.
Received on Friday, 1 December 2017 17:33:46 UTC