Hi Sam,
I'm one of Chrome's accessibility developers. I think this is a really
great idea, I think the ability for WebKit to do the searching rather
than the screen reader could be a big performance win for users.
In order to take advantage of this feature on multiple platforms, we'd
need to add
I just had another thought: how would this work in a multi-process browser?
As you may know, Chrome runs an instance of webkit in a separate
renderer process for each tab, but the GUI and all accessibility
handling happens in the main browser process. Because accessibility
calls are synchronous,
On Jun 22, 2011, at 3:34 PM, Dominic Mazzoni wrote:
I just had another thought: how would this work in a multi-process browser?
As you may know, Chrome runs an instance of webkit in a separate
renderer process for each tab, but the GUI and all accessibility
handling happens in the main
On Wed, Jun 22, 2011 at 4:21 PM, Chris Fleizach cfleiz...@apple.com wrote:
I think this is one drawback of Chrome's approach, the inability to retrieve
dynamic information. I suspect Chrome has similar issues for the
NSAccessibilityParameterizedAttribute attributes, and that it doesn't
On Wed, Jun 22, 2011 at 4:21 PM, Chris Fleizach cfleiz...@apple.com wrote:
On Jun 22, 2011, at 3:34 PM, Dominic Mazzoni wrote:
I just had another thought: how would this work in a multi-process
browser?
As you may know, Chrome runs an instance of webkit in a separate
renderer process
Hey Dominic,
Thanks for the feedback. I've been prototyping this idea here and it does
included text searching as you mentioned. My philosophy was to put the search
functionality right into the AccessibilityObject class and leave the job of
exposing external APIs up to the experts of each
On Jun 22, 2011, at 3:21 PM, Dominic Mazzoni wrote:
On Wed, Jun 22, 2011 at 3:14 PM, Samuel White samuel_wh...@apple.com wrote:
Thanks for the feedback. I've been prototyping this idea here and it does
included text searching as you mentioned. My philosophy was to put the
search
On Jun 22, 2011, at 4:29 PM, James Robinson wrote:
On Wed, Jun 22, 2011 at 4:21 PM, Chris Fleizach cfleiz...@apple.com wrote:
On Jun 22, 2011, at 3:34 PM, Dominic Mazzoni wrote:
I just had another thought: how would this work in a multi-process browser?
As you may know, Chrome runs
Hey everybody,
I'm new to the list and thought it would be a good idea to get some feedback on
an accessibility feature before filing a bug or submitting anything. Currently,
no functionality exists in WebKit to search through AccessibilityObjects using
basic search criteria like next link or
On Jun 21, 2011, at 4:30 PM, Samuel White samuel_wh...@apple.com wrote:
Hey everybody,
I'm new to the list and thought it would be a good idea to get some feedback
on an accessibility feature before filing a bug or submitting anything.
Currently, no functionality exists in WebKit to
Searching for elements on a webpage is one of the important functions for a
screen reader, so this has the potential for vastly improving screen reader
access on the web.
What's nice about this approach is that it will allow other platforms to also
take advantage. It should significantly
On Jun 21, 2011, at 5:45 PM, Charles Pritchard wrote:
On Jun 21, 2011, at 4:30 PM, Samuel White samuel_wh...@apple.com wrote:
Hey everybody,
I'm new to the list and thought it would be a good idea to get some feedback
on an accessibility feature before filing a bug or submitting
12 matches
Mail list logo
