Re: [orca-list] Accessible labels in editable fields

[luciano de souza <luchyanus gmail com>]

The label is just placed on the left. In my code, doesn't have any
association between the editable field and its respective label.

In the links you have suggested, I found a possible solution. I really
believe they provide a solution for my case. I need to study much more
because, regarding I have never coded anything using ATK, I am not
acquainted with ATK libraries. So I need to understand it from the
basic.

You have asked about a ossible programatical association between the
editable field and its label. So I presumed that in certain cases an
association like that is sufficient for Orca.

In Linux, IUP is an abstraction of GTK. So if it's possible, using
GTK, to code a accessible labeled editable field, it will so probable
that the same can be done with IUP.

The leader of IUP development team is a very gentle and attentive man.
If I have an example how to do it using GTK, he will be able to say if
the same can be done with IUP. If this is true, even without ATK, the
association could be done.

So, the solutions can be:

1. To identify a way to do it in IUP, regarding a GTK example;
2. To associate the controls with a ATK relationship.

on the second hypothesis, I need to understand better how AtK works.
Is it available in SO libraries? So I can import their functions.
Using any language, an ATK object can be created?

I think this kind of information is available in ATK documentation.
However, navigating in the links, I could find only the ATK reference,
but I need also the ATK manual to undestand its basics.

Well, I talked a lot. Now, let me see a peace of code writing in Lua
using IUP. This is the explanation why I prefer IUP. The syntax is so
simple and a few lines of code, lots of controls can be created.

-- Declaring the Lua module
require('iuplua')

--Creating some editable fields
name = iup.text{expand = 'YES'}
phone = iup.text{expand = 'YES'}
mail = iup.text{expand = 'YES'}
address = iup.text{expand = 'YES'}

-- Creating the respective labels
lbname = iup.label{title = 'Name'}
lbphone = iup.label{title = 'Phone'}
lbmail = iup.label{title = 'E-mail'}
lbaddress = iup.label{title = 'Address'}

-- Packing the created controls in horizontal boxes
row1 = iup.hbox{lbname, name}
row2 = iup.hbox{lbphone, phone}
row3 = iup.hbox{lbmail, mail}
row4 = iup.hbox{lbaddress, address}

-- Packing the horizontal boxes in a vertical box
box = iup.vbox{row1, row2, row3, row4}

-- Starting the dialog
dlg = iup.dialog{box; title = 'Agenda', margin = '10x10', bgcolor =
'240 230 220', gap = 5}
dlg:showxy(iup.CENTER, iup.CENTER)
iup.MainLoop()

As you can see, a small peace of code is required to create a dialog.
As an additional advantage, IUP works with native objects, so dialogs
created with IUP is accessible for screen readers as in Linux, as in
Windows or in MAC-Os. IUP can be used with C or Lua.

IUP doesn't require the specification of coordenates. Controls are
created with automatic layout. the layout abstract definition is
sufficient to place and size everything. It's like GTK, but with a
multiplatform accessibility.




2011/7/3, Luciano de Souza <luchyanus gmail com>:
> Hi listers,
>
> Using Lua and the graphical library IUP, I have created a dialog with
> some buttons and fields. In Linux, IUP is an abstraction of GTK driver,
> so it's entirely compatible with Orca.
>
> Buttons, lists, radio buttons, menus, combos  are all satisfactorily
> read. However, I have some problem with editable fields.
>
> When I focuse on a editable field, Orca says "edit", but it doesn't read
> the respective label placed on the left.
>
> As As far as I know, screen readers, in Linux or in Windows, doesn't
> read automatically the labels when focusing a editable field. The
> solution in Windows seems to be MSAA and in Linux ATK.
>
> Perhaps, the solution for my problem is ATK. I don't know where ATK
> routines are placed. Perhaps, ATK is a set of dynamic libraries and I
> need to call its functions like a DLL in Windows or a SO in Linux.
>
> I don't know. Even the most basic principles of ATK are unknown for me.
> I presume I don't need a deep knowledge of ATK. What I want to do is
> only to become readable a label, when focusing a editable field. So I
> ask when can I get information how to do this specific routine? This is
> the single change I need to do in order to make my dialogs accessible.
>
> Well, the first approach is really ATK. However, depending on Orca
> features, perhaps, ATK is not required. With JAWS, if a label is not
> read, we can open a options dialog and configure a custom label. Having
> saved this label, JAWS is able to interprete correctly the relationship
> between the editable field and its label. Has Orca something like that?
> Can we label fields, storing these definitions in a script file. If the
> answer is "yes", when an application is developed, to make it
> accessible, perhaps, in the pack, a Orca script file can be reliesed,
> assuring the desirable accessiblity.
>
> What do you suggest to whom wants to develop applications in Linux with
> accessible editable fields?
>
> I have never studied something about ATK, but I heard it can be a
> possible way. Regarding I want only to make an editable field
> accessible, I wish the simpler solution.
>
> Regards,
>
> Luciano


-- 
Luciano de Souza