- From: Andrew Kirkpatrick <akirkpat@adobe.com>
- Date: Wed, 30 Sep 2015 22:20:41 +0000
- To: "jon.avila@ssbbartgroup.com" <jon.avila@ssbbartgroup.com>, "Sailesh Panchang" <sailesh.panchang@deque.com>, GLWAI Guidelines WG org <w3c-wai-gl@w3.org>, Gregg Vanderheiden <gregg@raisingthefloor.org>
- CC: "paul.adam@deque.com" <paul.adam@deque.com>
Of course we may not get to dictate the technical specifics of how alternative text is provided, among other topics. If a site owner was able to make a claim that showed Accessibility Support for a solution that we consider non-standard or even non-preferred but that was able to meet the success criteria we would need to consider that an appropriate use of the WCAG standard. If there are loopholes that an implementation finds in WCAG that results in a solution that is compliant with WCAG 2.0 but has accessibility barriers for end users then we should take note and think about it when we discuss the next version. Thanks, AWK Andrew Kirkpatrick Group Product Manager, Accessibility Adobe Systems akirkpat@adobe.com http://twitter.com/awkawk http://blogs.adobe.com/accessibility On 9/30/15, 17:20, "Jonathan Avila" <jon.avila@ssbbartgroup.com> wrote: >I'm not sure this totally solves the issue for low vision users. For example, some assistive technologies turn off symbol fonts in browsers (ZoomText and Firefox) and some users may need to change the font face. Relying on CSS alt won't help them if they change the font when icon fonts are used. > >I personally would prefer to see a solution in the native markup languages such as HTML and proper support with assistive technology to solve these issues. > >Jonathan > >-- >Jonathan Avila >Chief Accessibility Officer >SSB BART Group >jon.avila@ssbbartgroup.com > >703-637-8957 (o) >Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter > > >-----Original Message----- >From: Sailesh Panchang [mailto:sailesh.panchang@deque.com] >Sent: Wednesday, September 30, 2015 4:24 PM >To: GLWAI Guidelines WG org; Gregg Vanderheiden >Cc: paul.adam@deque.com >Subject: HTML for markup and CSS for presentation: valid? > >What's the current thinking on use of CSS to deliver content including alt for CSS images? Can this become sufficient if screen reader support becomes widespread? >This will then impact techniques for SC 1.1.1 and 1.3.1 too. >Also content of C22: Using CSS to control visual presentation of text. > >Consider: >http://pauljadam.com/demos/css-line-through-del-ins-accessibility.html >http://pauljadam.com/demos/css4altgeneratedcontent.html >http://www.brucelawson.co.uk/2014/notes-on-draft-css-alt-property/ > >Clearly screen readers exposing CSS tables is problematic: >http://www.456bereastreet.com/archive/201110/using_displaytable_has_semantic_effects_in_some_screen_readers/ > >It became bad practice to use tags like FONT and attributes like >color, border, etc. in HTML markup with the validator flagging warnings . Now we have CSS providing a method for alt text. > >Thanks a lot, >Sailesh Panchang >
Received on Wednesday, 30 September 2015 22:21:13 UTC