[Webkit-unassigned] [Bug 52148] [Gtk] Implement support for Embedded Objects

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=52148





--- Comment #4 from Joanmarie Diggs <joanmarie.diggs at gmail.com>  2011-01-15 16:08:05 PST ---
(In reply to comment #3)

> You mean some kind of special character like those found in ff, right? 

Yup, FF and OOo Writer.

> Something like this:
> 
>  In [2]: t.getText(0, -1)
>  Out[2]: "Here's our logo: \xef\xbf\xbc It reminds me of airport security
>           screenings. "

Yup.

> My main question is "how that special character helps to screen readers"? 

It's a placeholder. For instance, in the case of a radio button, we need to know there's an object of ATK_ROLE_RADIO_BUTTON, where it is exactly (and thus where to present it). We also need a means to get that radio button (i.e. the AtkObject representation of that radio button) so we can also tell the user it's state (checked/unchecked, required, etc.)

> I guess the answer is that ORCA would use it to know that it should dive in the object to extract more info (actually I recall you talking to me about this in Seville, not sure if I recall correctly, though :-))

You do. :-)

>but I wonder whether it shouldn't be better to provide a textual representation for them.

Well, it's up to the screen reader to handle how to present the state, allow users to have 'brief' and 'verbose' output, represent embedded objects in braille (often as symbols < > and <x>, rather than text), etc., etc., etc. That something WebKitGtk should take on?? ;-) (rhetorical question)

> Of course, I'm talking from my vast ignorance on the issue :-), and I realize that then we'd need to agree on a specific text representation for each kind of object (e.g. 'checked/unchecked' for check boxes, 'selected/unselected' for radio buttons...) but asking is not harmful either.

And you'd also have to get all those strings localized into all the languages gnome is localized into, and figure out brief braille symbols, and verbose braille symbols. In a way, I'd love to be able to say, "Yeah, you're right, this isn't Orca's job; it's WebKitGtk's." :-) But right now, I'm pretty sure we're stuck with it Orca-side. Feel free to keep trying to convince me I'm wrong, as I might let you win. ;-)

It's never, ever harmful to ask questions. I hope I've answered them. If not, ask again and I shall try again.

> > 2. Each embedded object should implement AtkHyperlink.
> 
> Is this really always needed for each embedded object of any kind? 

What we really need is:

* atk_hyperlink_get_start_index()
* atk_hyperlink_get_end_index()
* atk_hyperlink_get_object()

> I can see it for the image, but don't know how this interface would be implemented for other objects, such as the check boxes or the radio buttons (e.g. what should they return in the atk_hyperlink_get_uri() method?).

Since the return type is a string, and since these objects would not have an associated uri, I would think it would return an empty string.

What we really care about is where is the thing w.r.t. the text (start, end indices) and to be able to say "give me that object" for the purpose of presenting its role, states, coming up with its braille representation, etc., etc.

HTH. Thanks!!

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.