Hi. HTML 5 provides two new elements figure and figcaption that seems
to don't have a good way for ATK mapping.
The proposal is:
1) introduce new ATK role for figure element like ROLE_FIGURE
2) use ROLE_CAPTION for figcaption element
3) make figure and figcaption accessible objects related by labe
to introduce a sort of new level of abstraction so
that the user goes into it when he's interested in details. For
example:
Alhambra
Thanks.
Alex.
On Wed, Nov 9, 2011 at 11:43 PM, Piñeiro wrote:
> On 11/09/2011 11:07 AM, Alexander Surkov wrote:
>> Hi. HTML 5 provide
/html5/spec/grouping-content.html#the-figure-element.
Thank you.
Alex.
On Fri, Nov 11, 2011 at 3:53 AM, Piñeiro wrote:
> On 11/10/2011 05:25 AM, Alexander Surkov wrote:
>> Hi. Figure element is supposed to contain or group illustrations,
>> diagrams and etc so role_image is inside a
Doesn't UI provide a tooltip in this case which is usually mapped to
accessible name if name is not provided? At least that happens on the
web.
But technically it's sort of weird that application creates a widget
but it can't control the properties of widget accessible object.
Thanks.
Alex.
On
Hi. There's interesting discussion about editable vs unavailable state
happening at Mozilla bug -
https://bugzilla.mozilla.org/show_bug.cgi?id=733382. I put here some
summary of it.
The ATK spec says: "Indicates the user can change the contents of this
object" -
http://www.pygtk.org/docs/pygtk/at
ress.
Thank you.
Alex.
On Wed, Mar 7, 2012 at 11:40 PM, Piñeiro wrote:
> On 03/07/2012 07:45 AM, Alexander Surkov wrote:
>> Hi. There's interesting discussion about editable vs unavailable state
>> happening at Mozilla bug -
>> https://bugzilla.mozilla.org/show_bug.cgi?id=733
Cc'ing Ginn and Trevor.
On Tue, Sep 25, 2012 at 12:54 AM, Jonathan Nadeau
wrote:
> Hello list,
>
> I know this is the gnome accessibility list. i have a question about the
> accessibility of firefox and thunderbird. under Gnome these are very
> accessible. But I've managed to get SFCE 4.10 to b
Hi. For Gecko it's much easier if TEXT_BOUNDARY_FOO constants were the same
with IAccessible2 constants since it allows to have shared implementation.
I should notice however that IAccessible2 says to return no word for
TEXT_BOUNDARY_WORD if the given offset is outside a word. It seems it makes
the
Hey, Joanie.
Interesting. Personally I think it's nicer if a given chunk of text can
> be chopped up neatly into the various TEXT_BOUNDARY_FOO units with no
> scraps left over. Even for words.
>
I share this thinking but I don't know background of these constants.
> It seems it makes
> > the pre
Hi. The idea of text_update event is a substitution of
text_removed/text_inserted events pair. It's about less events and
describes better what the user does. So if the user selected the text
and typed new text then it's a case for text_update event. We never
implemented it in Firefox because AT di
Hey. Answering inline.
On Tue, Aug 13, 2013 at 7:31 AM, Piñeiro wrote:
> On 08/12/2013 08:13 PM, Alexander Surkov wrote:
>> Hi. The idea of text_update event is a substitution of
>> text_removed/text_inserted events pair.
> Are you sure about this?
>
> Reading the or
I think I'm fine if we had text-inserted/removed only. At least it
seems I don't have an objection to keep it alive.
Alex.
On Wed, Aug 14, 2013 at 10:27 AM, Piñeiro wrote:
> On 08/13/2013 08:10 PM, Alexander Surkov wrote:
>>
>>> In the same way, not sure if update-tex
Hi.
HTML5 introduces inert subtrees [1] which are supposed to make a
portion of the document inactive (not interactive for the user):
"When a node or one of its ancestors is inert, then the user agent
must act as if the element was absent for the purposes of targeting
user interaction events, may
play.
Probably the spec should be clarified before a11y mapping is made but
possibly a11y mapping can be flexible.
Please take your time, I bet nobody is in hurry and thank you for feedback.
Alexander.
On Fri, Sep 27, 2013 at 12:23 PM, Piñeiro wrote:
> On 09/27/2013 06:03 PM, Alexander Surk
> On 09/27/2013 12:03 PM, Alexander Surkov wrote:
>> Hi.
>>
>> HTML5 introduces inert subtrees [1] which are supposed to make a
>> portion of the document inactive (not interactive for the user):
>>
>> "When a node or one of its ancestors is inert, the
Yep, STATE_ACTIVE as you describe it might do a trick. Basically if AT
are ok that STATE_INACTIVE window contains STATE_ACTIVE dialog then it
should be working.
Alex.
On Fri, Sep 27, 2013 at 2:45 PM, Joanmarie Diggs wrote:
> On 09/27/2013 01:54 PM, Alexander Surkov wrote:
>
>> A prim
Hi.
HTML5 introduced meter element [1], which is basically a progressbar role
but can be in special states:
1) optimal state when value is in optimal rage (for example, if low <
optimum < high then value should be in [low, high], if optimum > high then
value should be greater than high.
2) sub
the AtkValue
> > interface. It already exposes current, minimum and maximum. So the idea
> > would be to expose low, high and optimum as well. On a related note, we
> > are also currently discussing the addition of string description of
> > numerical values to address the issues
Hi, Joanie. Answering inline.
On Fri, Dec 13, 2013 at 11:41 AM, Joanmarie Diggs wrote:
> On 12/12/2013 04:12 PM, Alexander Surkov wrote:
>
> > I'm ok with AtkValue extension, it makes sense if Orca wants complete
> > information about the control.
>
> Exactly how
arie Diggs wrote:
> Hey Alexander, all.
>
> On 12/13/2013 07:41 PM, Alexander Surkov wrote:
>
> > Said above can be applied to wrong value which is exposed as invalid
> > state but nevertheless it's a state. So I don't see a semantical
> > contradiction here. If
I'd say ARIA extension makes sense but I have a feeling that standard ways
can be used here like changing the accessible description or using the live
regions.
Thanks.
Alex.
On Fri, Dec 20, 2013 at 12:29 PM, Piñeiro wrote:
>
> On 12/19/2013 11:15 PM, Jason White wrote:
> > Mario Sanchez Prada
Accessible events are just describe the change within accessible tree. They
are not really about user action, i.e. single user action may result in
several of accessible events. What is your use case?
On Thu, Dec 4, 2014 at 8:43 PM, Michael Pozhidaev wrote:
> Hello all,
>
> I got a question rega
t? The announcement to the user depends on the _*entire*_
> set of events but currently I don't know any way to be clearly sure what
> kind of user action I should announce.
>
> Thank you! :))
>
> Alexander Surkov writes:
>
> > Accessible events are just describe the
Hi. ATK as IAccessible2 both have bunch of roles for specialized dialogs
like color chooser dialog [1], [2]. I'm curious if there's any application
on Linux today for these roles. In case of IAccessible2 we never used those
in Firefox following IA2 spec. However Chrome uses those roles for control
Ok, so we have to figure something else. I would avoid to introduce more
discrepancy between IA2 and ATK.
On Fri, Dec 12, 2014 at 10:34 AM, Joseph Scheuhammer
wrote:
> On 2014-12-12 3:27 AM, Alejandro Piñeiro wrote:
>
>> I know that gtk is using that role. The best example is this widget:
>>
>>
Isn't it accessible name computation issue? Usually it is author's
responsibility to make a proper label for a control, and thus AT don't need
to know any who's first and who is next.
I have no LibreOffice at hands, so could you think of HTML like example to
demo the issue?
On Mon, Mar 5, 2018 at
On Thu, Apr 5, 2018 at 5:18 PM, Samuel Thibault <
samuel.thiba...@ens-lyon.org> wrote:
> Hello,
>
> Alexander Surkov, le jeu. 05 avril 2018 14:41:42 -0400, a ecrit:
> > Isn't it accessible name computation issue?
>
> It's not simple for an Entry widget, see th
, and LibreOffice may be the only one who will expose
them. So LibreOffice-only solution has to exists, that makes developer's
life easier, and doesn't require any standards changes.
On Fri, Apr 6, 2018 at 2:40 PM, Samuel Thibault <
samuel.thiba...@ens-lyon.org> wrote:
> Hello,
>
>
28 matches
Mail list logo
