W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2015

RE: Using CSS to insert Content

From: Jonathan Avila <jon.avila@ssbbartgroup.com>
Date: Fri, 17 Apr 2015 02:01:04 +0000
To: Andrew Kirkpatrick <akirkpat@adobe.com>, David MacDonald <david100@sympatico.ca>, James Nurthen <james.nurthen@oracle.com>, WCAG <w3c-wai-gl@w3.org>
Message-ID: <BY2PR03MB2725E5EB5A5C465AB4786AF9BE30@BY2PR03MB272.namprd03.prod.outlook.com>
Ø  .  It looks like the UIA API supports the CSS generated text – is that the API that JAWS uses?

I just looked with IE with Inspect and UIA and I didn’t see any CSS content using the before or after pseudo classes in the accessible name or other obvious properties.

Jonathan

--
Jonathan Avila
Chief Accessibility Officer
SSB BART Group
jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com>

703-637-8957 (o)
Follow us: Facebook<http://www.facebook.com/#%21/ssbbartgroup> | Twitter<http://twitter.com/#%21/SSBBARTGroup> | LinkedIn<http://www.linkedin.com/company/355266?trk=tyah> | Blog<http://www.ssbbartgroup.com/blog> | Newsletter<http://eepurl.com/O5DP>

From: Andrew Kirkpatrick [mailto:akirkpat@adobe.com]
Sent: Wednesday, April 01, 2015 9:28 AM
To: David MacDonald; James Nurthen; WCAG
Subject: RE: Using CSS to insert Content

Thanks David,
Looking at the results I wonder whether the issue is with IE or with JAWS in how it gathers information from IE.  It looks like the UIA API supports the CSS generated text – is that the API that JAWS uses?  Seems possible that IE is doing the right thing and JAWS is using the DOM for that information.

Knowing that the generated content not working is an issue for IE, I wouldn’t rely on this mechanism to deliver substantial content, but I think that one of the main use cases we were talking about was to apply open and closing quotes to the quote.

Would we say that the quote is not properly indicating the relationship expressed in the presentation (SC1.3.1) for AT users?  Clearly if you said that IE11 was not part of your accessibility support statement then you’d have no issue, but what if you did include IE11?  In my example below I could make an argument that the fact that there is a quote is going to be obvious to a non-sighted user because of the “David said” lead in, but I’m sure I could make a counter-example also.  What do people think?

Sample code:
HTML <p>David said <q>CSS Generated Content has a problem in IE11</q>.</p>

Sample CSS:
q:lang(en) { quotes: '"' '"' "'" "'" }
q:before {content: open-quote;}
q:after {content: close-quote;}


From: David MacDonald [mailto:david100@sympatico.ca]
Sent: Wednesday, April 01, 2015 8:45 AM
To: James Nurthen; WCAG
Subject: Using CSS to insert Content

Hi James
As a follow up to our discussion yesterday about inserting content using <q> with the CSS fallback. It appears to be an IE problem.

http://davidmacd.com/blog/inserting-content-with-css-accessibility.html



Cheers,

David MacDonald



CanAdapt Solutions Inc.

Tel:  613.235.4902<tel:613.235.4902>

LinkedIn<http://www.linkedin.com/in/davidmacdonald100>

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>


Received on Friday, 17 April 2015 02:01:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:34:19 UTC