[Lazarus] OI Checkboxes

Frederic Da Vitoria davitofrg at gmail.com
Mon Dec 1 19:11:55 CET 2014


2014-11-29 18:23 GMT+01:00 Frederic Da Vitoria <davitofrg at gmail.com>:

>
> 2014-11-29 15:35 GMT+01:00 Juha Manninen <juha.manninen62 at gmail.com>:
>
>> On Thu, Nov 27, 2014 at 3:31 PM, Frederic Da Vitoria
>> <davitofrg at gmail.com> wrote:
>> > That's how it is supposed to work. But I remember that Delphi controls
>> were
>> > based on Windows controls too, but they weren't recognized by at least
>> one
>> > screen reader. But this may be this specific screen reader's fault,
>> which
>> > maybe did not gather information using the Microsoft recommended method.
>>
>> Yes, there may be issues which I do not know about. Felipe knows this
>> topic best.
>> Sometimes lots of glue code is needed between LCL component and the
>> widgetset which makes them partly custom drawn components. I thought a
>> Checkbox is an easy one but maybe not.
>>
>> I plan to commit the new component from Vojtěch Čihák and use it in
>> Object Inspector Boolean editor, but initially enclosed in IFDEFs as
>> an alternative for the current TCheckBox.
>> Frederic Da Vitoria, can you later test accessibility related issues?
>> I think they are important.
>>
>
> I'll try to. It has been a long time since I ran this software, but I have
> a friend who is still using it sometimes, he should be able to help me.
>

Here are my results using NVDA 2014.4 on Windows 7 64 bits

Properties : NVDA doesn't announce the property names in the Object
inspector. This is not related to the new checkboxes, but it may influence
how corrections are prioritized. Because the property names are not told
(sorry, I can't decide how this should be said in English: would one say
something (name, property, label...) is enunciated, told, said,
announced...?)

TCheckBoxThemed :
    design mode : NVDA won't say the control name in the form editor,
whether I select it by clicking on it or by tabulating to it. Same for a
standard TCheckbox. Afterthought; Because the Objecct inspector does not
currently tell the property names, I guess most blind users wouldn't use a
form designer but would edit directly the lfm file with a text editor. But
this is only my guess, I don't know any blind developer who uses a IDE,
although I am sure there are lots of them.
    run mode : NVDA tells the control name, but it won't say if it is
checked or not. When pressing the space bar, NVDA says only "space", and
does not react at all when clicking on the TCheckboxThemed. This works
perfectly with a TCheckBox. I am sorry to conclude that TCheckboxThemed is
currently unusable for a blind user.

I looked a little around to try to find how TCheckbox manages to be
properly recognized by NVDA. I am guessing it has something to do with
TLazAccessibleObject. But as I don't see TCheckbox doing anything in order
to make it work, so that I am at a loss to tell why TCheckboxThemed does
not work too. If someone has some more information on how this works, I
could try to fix it.

-- 
Frederic Da Vitoria
(davitof)

Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20141201/7fcbfb08/attachment-0002.html>


More information about the Lazarus mailing list