- From: Joseph Scheuhammer <clown@alum.mit.edu>
- Date: Fri, 10 Oct 2014 09:43:04 -0400
- To: "Schnabel, Stefan" <stefan.schnabel@sap.com>, Steve Faulkner <faulkner.steve@gmail.com>, Marco Zehe <mzehe@mozilla.com>
- CC: James Nurthen <james.nurthen@oracle.com>, Dominic Mazzoni <dmazzoni@google.com>, W3C WAI Protocols & Formats <public-pfwg@w3.org>
Stefan,
I see the same search/selection failures for FF32.0.3, Safari 6.2, and
Chrome 38.0 on OS X (Mountain Lion).
The irony is that this is a UI failure of the browsers, and not a
failure at the accessibility layer. Accessibility is ahead for a
change. I wonder if one could use the AAPIs for selection and search
since they have access to the text.
On 2014-10-10 4:10 AM, Schnabel, Stefan wrote:
>
> I already have something for the list:
>
> 1.Implemented Search in User agents should also be able to *find*
> generated CSS content on page
>
> 2.*Selecting*generated CSS content by mouse or by keyboard (F7 Caret
> Mode in FF or IE) should be possible
>
> 1+2 definitely fails in win7 for
>
> -IE 11
>
> -Chrome 37
>
> -Firefox 32
>
> -Opera 24
>
--
;;;;joseph.
'Array(16).join("wat" - 1) + " Batman!"'
- G. Bernhardt -
Received on Friday, 10 October 2014 13:43:36 UTC