- From: Abma, J.D. (Jake) <Jake.Abma@ing.nl>
- Date: Fri, 23 Jun 2017 08:28:43 +0000
- To: Alastair Campbell <acampbell@nomensa.com>, lisa.seeman <lisa.seeman@zoho.com>
- CC: "W3c-Wai-Gl-Request@W3. Org" <w3c-wai-gl@w3.org>
- Message-ID: <1498206523873.89407@ing.nl>
Another +1 here Pseudo-assistive technology like the use of lay-overs are not the same thing as the text in the SC. There’s even a danger to promote such technologies as they are often laborious to handle, one-off on every site and provide for a means to pull out off the real problem for site owners which is making websites accessible / using standards to start with. I also do see the need for these kind of personal adjustments from a user perspective but besides these technologies we also have the accessibility settings in the OS, the settings in a browser, plugins / extensions, different devices and assistive technology. The lay-overs are just another fix op top possibility and the SC should be about a standard implementation. Regards, Jake ________________________________ From: Alastair Campbell <acampbell@nomensa.com> Sent: Thursday, June 22, 2017 4:14 PM To: lisa.seeman Cc: W3c-Wai-Gl-Request@W3. Org Subject: Re: Long list of sites that use personalization to meet wcag Hi Lisa, I think there is quite a big difference between adding something that brings a site up to a reasonable accessibility standard (which generally doesn’t affect layout or what is presented), and customisation which changes which options are shown and adds icons. Bolt-on things are not new at all, I remember writing about BrowseAloud in 2006, and I’ve come across many since. Nothing is needed on the user-agent end because their aim is to use what should be part of a well structured site. What would be new (although envisaged a long time ago [1,2]) is something where the user comes with preferences that are taken on by the site and affect layout and options shown. These are very different things in the context of the web, and the personalisation aspect comes with a chicken & egg problem. Cheers, -Alastair 1] https://www.w3.org/2000/10/DIAWorkshop/bartlett.html 2] https://alastairc.ac/2007/05/user-agent-improvements/#profiles From: "lisa.seeman" <lisa.seeman@zoho.com> Date: Thursday, 22 June 2017 at 14:56 To: Alastair Campbell <acampbell@nomensa.com> Cc: WCAG <w3c-wai-gl@w3.org> Subject: Re: Long list of sites that use personalization to meet wcag Hi Alastair Your are completely correct - these fix existing accessibility issues. They are not using the new coga sc. However the technology is the same - it is just another case. I am bringing it up because people felt the last time we discussed it that personlization in the technology space was completely new. I said it was widely used in Israel and Andrew asked me for some examples of big sites that use this type of technology. All the best Lisa Seeman LinkedIn<http://il.linkedin.com/in/lisaseeman/>, Twitter<https://twitter.com/SeemanLisa> ---- On Thu, 22 Jun 2017 13:00:05 +0300 Alastair Campbell<acampbell@nomensa.com> wrote ---- Hi Lisa, Are these all User1st customers? As James said, it appears to be a bolt-on primarily to fix issues, are there any examples which do the type of things required by the new COGA SCs? E.g. adding icons, reducing the options displayed. Customisation which affects colour and text-size are relatively common, but as I outlined before [1] things which alter the layout and navigation are a step up, and I’m interested in current examples of that. Cheers, -Alastair 1] https://alastairc.ac/2017/02/four-levels-of-accessibility-customisation/#customisation From: "lisa.seeman" <lisa.seeman@zoho.com<mailto:lisa.seeman@zoho.com>> Date: Wednesday, 21 June 2017 at 17:34 To: WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>> Cc: Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>> Subject: Fwd: Long list of sites that use personalization to meet wcag I sent this list to the coga TF but it might be more useful here. People think that personalization is a new technology in the accessibility space. It has been successfully used for years. In Israel lots of big sites use it as the preferred way to meet accessibility requirements. There are three companies with competing technologies that I know who do it based on metadata and aria type semantics. I put together some examples for you in telecom, banking, health care, commerce , airlines, government etc (If this is not enough I could spend some more time and double the list. FYI - The word for accessibility in hebrew is נגישות so if there is no icon do a search for that word to open personlization settings for accessibility or tab though the page. (If the site did a good job it should be the first or second focus point) . Also please do not point out if any of the sites have outstanding accessibility bugs. Like many large sites they often have a road map of what they are adressing first. example: https://www.cellcom.co.il/ https://cellcomtv.cellcom.co.il/#default https://www.ebox.co.il/ https://business.cellcom.co.il/#default http://www.elal.com/he/Israel/Pages/default.aspx https://vacation.elal.co.il/ dev http://www.ikea.co.il/ testing https://www.shbn.co.il/ m.skinbinui.co.il http://recruits.iaf.co.il/2455-he/IAF.aspx http://izkor.iaf.org.il/Templates/HomePage/HomePage.aspx http://m.iaf.org.il/7240-he/IAF.aspx http://www.nblaw.com/ https://trade.psagot.co.il/#/join http://testmobile.fattal.co.il/ dev https://www.lcweb-stg.co.il/ dev mba.biu.ac.il https://www.xnes.co.il/ https://www.maccabitivi.co.il/ http://seiholding.com/ https://amacresearch.gatech.edu/ http://www.mla.ac.il/ https://www.ace.co.il/ www.ace.co.il/<https://www.ace.co.il/> cellcom.co.il All the best Lisa Seeman LinkedIn<http://il.linkedin.com/in/lisaseeman/>, Twitter<https://twitter.com/SeemanLisa> ---------------------------------------------------------------- ATTENTION: The information in this e-mail is confidential and only meant for the intended recipient. If you are not the intended recipient, don't use or disclose it in any way. Please let the sender know and delete the message immediately. ------------------------------------------------------------------------------------------------------
Received on Friday, 23 June 2017 08:29:24 UTC