- From: Wayne Dick <wayneedick@gmail.com>
- Date: Mon, 18 Jan 2016 17:43:46 -0800
- To: Andrew Kirkpatrick <akirkpat@adobe.com>
- Cc: "WCAG (w3c-wai-gl@w3.org)" <w3c-wai-gl@w3.org>
- Message-ID: <CAJeQ8SAzVGOomUQc5AzXi6aOu2POxGjSgQ2OD1ayo5KspE6Gyw@mail.gmail.com>
Regarding Issue 80. Since I'll be absent here is my thinking on issue 80. When people use sprites for foreground images (images with important semantics) they should not use background-image to import them. The "before" and "after" pseudo elements work just fine for this purpose. AT looks for background images because they are dispensable and most background images create reading havoc for people who cannot process detail well, a very big group. AT like Windows High Contrast and others that enable removing background images have a perfectly natural way to find these images, the background-image property. When people misuse background-image they disable this programmatic access for AT. The proposed solution does fix the text alternative issue I agree. The proposed language does not address the semantic issue for low vision access. The LV user may want to see the sprite image, they just don't want to read text in front of visually confusing backgrounds. F3 should be kept. It is an obvious failure of 1.3.1. ARIA is not the solution because CSS already supports semantically appropriate a way to load sprites and not violate properties that are needed for other reasons. That what I have. I don't think the proposed language gives a complete solution. Wayne I think that sums it up. On Mon, Jan 18, 2016 at 5:23 PM, Wayne Dick <wayneedick@gmail.com> wrote: > I cannot make tomorrow's meeting. I know I promised to scribe. I did my > scribing homework and practice, but I had to make an appointment for > personal business, and Tuesday 8:30-10:30am PST is my only time for it. I > am very sorry, and I promise to scribe next week. > > Sorry, wayne > > On Mon, Jan 18, 2016 at 7:52 AM, Andrew Kirkpatrick <akirkpat@adobe.com> > wrote: > >> The WCAG WG will be meeting on Tuesday, 19 January 2015 at 11AM Eastern >> US (Length: up to 90 minutes) >> >> >> >> Scribe list: https://www.w3.org/WAI/GL/wiki/Scribe_List >> >> >> >> Agenda: >> >> 1. Extension document comment survey ( >> https://www.w3.org/2002/09/wbs/35422/Ext_req_comments/) >> 2. Survey (Items 3-5 only): >> https://www.w3.org/2002/09/wbs/35422/20161stSurvey/ >> 3. Github issues walkthru. https://github.com/w3c/wcag/issues >> >> >> To connect to the meeting: >> >> Join WebEx meeting ( >> https://mit.webex.com/mit/j.php?MTID=m064eab3e5485b640231a7fe56dc4785c) >> >> Meeting number: 642 418 206 >> Meeting password: Find in the irc meeting room header if you >> don’t know it >> >> or >> >> Join by phone >> +1-617-324-0000 US Toll Number >> Access code: 642 418 206 >> >> IRC: irc.w3.org<http://irc.w3.org> port: 6665 channel #wai-wcag >> >> WebEx client information: >> WebEx on Windows (IE, Chrome, FF) or Mac: Download the client (Meeting >> Center Application) from >> https://mit.webex.com/mc0901lsp13/meetingcenter/support/support.do?siteurl=mit&Action=downloads >> >> WebEx on mobile platforms: >> http://www.webex.com/products/web-conferencing/mobile.html >> >> >> >> Thanks, >> >> AWK >> >> >> >> Andrew Kirkpatrick >> >> Group Product Manager, Accessibility >> >> Adobe Systems >> >> >> >> akirkpat@adobe.com <akirkpatrick@adobe.com> >> >> http://twitter.com/awkawk >> >> http://blogs.adobe.com/accessibility >> >> >> > >
Received on Tuesday, 19 January 2016 01:44:55 UTC