Re: [Libreoffice] Question about IAccessibility2

2011-11-25 Thread Sophie Gautier
Hi all,

On Thu, Nov 24, 2011 at 10:23 PM, Michael Meeks michael.me...@suse.com wrote:

 On Thu, 2011-11-24 at 21:20 +0100, Christophe Strobbe wrote:
 Those are already strings, which will be localized. I have no
 application to test, whether this is sufficient. But I guess it
 will, because otherwise people would have complained in a lot of
 other places where list boxes are used.

        :-)

 Just in case you would like to test this: there are two free options
 on Windows:

        I would recommend asking a friend to test this on Linux, where the
 accerciser tool will instantly show you whether you've got the new names
 right; and it is native code without any twisted java-ness.

Just for information, I've Accerciser installed on my machine and am
usually testing LibO with Orca, so if you need some tests, don't
hesitate to ping me directly.

Kind regards
Sophie
-- 
Founding member of The Document Foundation
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: [Libreoffice] Question about IAccessibility2

2011-11-24 Thread Regina Henschel

Hi Christophe,

Christophe Strobbe schrieb:

Hi Regina,

At 23:11 21-11-2011, Regina Henschel wrote:

Hi all,

I have started to implement the attribute stroke-linecap.


I assume this refers to svg:stroke-linecap (�20.164 in the ODF 1.2 spec,
which refers to stroke properties in the SVG spec:
http://www.w3.org/TR/SVG11/painting.html#StrokeProperties).


Yes.





I come across IAccessibility2 in files
/core/cui/source/tabpages/tabline.hrc
/core/cui/source/tabpages/tabline.src
There are some string resources defined like
#define STR_END_LENGTH 41
Some are commented out in lines 125 to 134 in tabline.hrc. Such string
resources are used in method SetAccessibleName in
/core/cui/source/tabpages/tpline.cxx


SetAccessibleName is a method that exists in several accessibility APIs,
e.g.
* ATK: atk_object_set_name:
http://developer.gnome.org/atk/stable/AtkObject.html#atk-object-set-name
* Java:
http://download.oracle.com/javase/6/docs/api/javax/accessibility/AccessibleContext.html#setAccessibleName%28java.lang.String%29

* Microsoft: http://msdn.microsoft.com/en-us/library/bb776383.aspx:
IAccessibleObject::SetAccessibleName method


So it is a comprehensive concept.






I see them for some controls but not for all, especially not for
maLBEdgeStyle.

(1) What they are used for?
(2) Why they are set for some controls but not for all?
(3) Do I have to define such a string for my new linecap style list box?



I don't know what the accessible name for a stroke-linecap would be
(i.e. when it is present in ODF content). However, if you are referring
to a list box where an author can choose between different
stroke-linecap styles, I would definitely give those options an
accessible name (e.g. butt cap, round cap and square cap, which I found
in the SVG spec).


Those are already strings, which will be localized. I have no 
application to test, whether this is sufficient. But I guess it will, 
because otherwise people would have complained in a lot of other places 
where list boxes are used.


I think I postpone this special detail until the rest is finished and 
there is a product that can be tested in connection with an 
accessibility application.





I hope this helps.


Yes, I had not been aware, that the concept is not special for LibO/OOo.

Kind regards
Regina
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: [Libreoffice] Question about IAccessibility2

2011-11-24 Thread Christophe Strobbe

Hi Regina,

At 15:31 24-11-2011, Regina Henschel wrote:

Hi Christophe,

Christophe Strobbe schrieb:

(...)


I come across IAccessibility2 (...) Such string
resources are used in method SetAccessibleName in
/core/cui/source/tabpages/tpline.cxx


SetAccessibleName is a method that exists in several accessibility APIs,
e.g.
* ATK: atk_object_set_name:
http://developer.gnome.org/atk/stable/AtkObject.html#atk-object-set-name
* Java:
http://download.oracle.com/javase/6/docs/api/javax/accessibility/AccessibleContext.html#setAccessibleName%28java.lang.String%29

* Microsoft: http://msdn.microsoft.com/en-us/library/bb776383.aspx:
IAccessibleObject::SetAccessibleName method


So it is a comprehensive concept.



(...) if you are referring
to a list box where an author can choose between different
stroke-linecap styles, I would definitely give those options an
accessible name (e.g. butt cap, round cap and square cap, which I found
in the SVG spec).


Those are already strings, which will be localized. I have no 
application to test, whether this is sufficient. But I guess it 
will, because otherwise people would have complained in a lot of 
other places where list boxes are used.


Just in case you would like to test this: there are two free options 
on Windows:


* NVDA: an open-source screen reader: http://www.nvda-project.org/. 
(The portable version can be run from a USB key if you don't want to 
install it.) When testing with a screen reader, you first need to 
installe the Java Access Bridge: 
http://www.oracle.com/technetwork/java/javase/tech/index-jsp-136191.html.


* The Java Accessibility Utilities, which you can (still) find at 
http://java.sun.com/javase/technologies/accessibility/downloads.jsphttp://java.sun.com/javase/technologies/accessibility/downloads.jsp. 
Because LibreOffice on Windows uses the Java Accessibility API, you 
can these inspection tools.
The Java Accessibility Utilities include Java Monitor, Ferret, Monkey 
and AccessibilityMonitor. To use, for example, Java Monitor, one 
should go through the following steps:

1. Add the jar files jaccess.jar and jaccess-examples.jar in the CLASSPATH.
2. Modify the file lib/accessibility.properties in the JDKHOME 
directory to include the following line:

assistive_technologies=JavaMonitor
Note that the README.txt claims that this line should be 
AWT.assistive_technologies=JavaMonitor, but this is not correct.
3. When you start LibreOffice (or a pure Java application), Java 
Monitor will start automatically.
For checking accessible name, description, role, value and state(s) 
in menus, Ferret is the appropriate tool.
(Oh, and alway close LibreOffice if you want to close the 
accessibility utility; if you try to close the accessibility utility 
first, it will also close LibreOffice.)



I think I postpone this special detail until the rest is finished 
and there is a product that can be tested in connection with an 
accessibility application.


OK. And thanks for asking questions about accessibility :-)

Best regards,

Christophe


--
Christophe Strobbe
K.U.Leuven - Dept. of Electrical Engineering - SCD
Research Group on Document Architectures
Kasteelpark Arenberg 10 bus 2442
B-3001 Leuven-Heverlee
BELGIUM
tel: +32 16 32 85 51
http://www.docarch.be/
Twitter: @RabelaisA11y
---
Open source for accessibility: results from the AEGIS project 
www.aegis-project.eu

---
Please don't invite me to Facebook, Quechup or other social 
networks. You may have agreed to their privacy policy, but I haven't.


___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: [Libreoffice] Question about IAccessibility2

2011-11-24 Thread Michael Meeks

On Thu, 2011-11-24 at 21:20 +0100, Christophe Strobbe wrote:
 Those are already strings, which will be localized. I have no 
 application to test, whether this is sufficient. But I guess it 
 will, because otherwise people would have complained in a lot of 
 other places where list boxes are used.

:-)

 Just in case you would like to test this: there are two free options 
 on Windows:

I would recommend asking a friend to test this on Linux, where the
accerciser tool will instantly show you whether you've got the new names
right; and it is native code without any twisted java-ness.

Having said that - simply adding a new accessible name is sufficiently
simple that we can check that at code-review time, I don't think there
is need for detailed testing there.

 OK. And thanks for asking questions about accessibility :-)

Though of course this is cool :-)

All the best,

Michael.

-- 
michael.me...@suse.com  , Pseudo Engineer, itinerant idiot

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: [Libreoffice] Question about IAccessibility2

2011-11-23 Thread Christophe Strobbe

Hi Regina,

At 23:11 21-11-2011, Regina Henschel wrote:

Hi all,

I have started to implement the attribute stroke-linecap.


I assume this refers to svg:stroke-linecap 
(§20.164 in the ODF 1.2 spec, which refers to 
stroke properties in the SVG spec: 
http://www.w3.org/TR/SVG11/painting.html#StrokeProperties).




I come across IAccessibility2 in files
/core/cui/source/tabpages/tabline.hrc
/core/cui/source/tabpages/tabline.src
There are some string resources defined like
#define STR_END_LENGTH  41
Some are commented out in lines 125 to 134 in 
tabline.hrc. Such string resources are used in method SetAccessibleName in

/core/cui/source/tabpages/tpline.cxx


SetAccessibleName is a method that exists in several accessibility APIs, e.g.
* ATK: atk_object_set_name: 
http://developer.gnome.org/atk/stable/AtkObject.html#atk-object-set-name
* Java: 
http://download.oracle.com/javase/6/docs/api/javax/accessibility/AccessibleContext.html#setAccessibleName%28java.lang.String%29
* Microsoft: 
http://msdn.microsoft.com/en-us/library/bb776383.aspx: 
IAccessibleObject::SetAccessibleName method




I see them for some controls but not for all, 
especially not for maLBEdgeStyle.


(1) What they are used for?
(2) Why they are set for some controls but not for all?
(3) Do I have to define such a string for my new linecap style list box?



I don't know what the accessible name for a 
stroke-linecap would be (i.e. when it is present 
in ODF content). However, if you are referring to 
a list box where an author can choose between 
different stroke-linecap styles, I would 
definitely give those options an accessible name 
(e.g. butt cap, round cap and square cap, which I found in the SVG spec).



I hope this helps.

Best regards,

Christophe


--
Christophe Strobbe
K.U.Leuven - Dept. of Electrical Engineering - SCD
Research Group on Document Architectures
Kasteelpark Arenberg 10 bus 2442
B-3001 Leuven-Heverlee
BELGIUM
tel: +32 16 32 85 51
http://www.docarch.be/
Twitter: @RabelaisA11y
---
Open source for accessibility: results from the 
AEGIS project www.aegis-project.eu

---
Please don't invite me to Facebook, Quechup or 
other social networks. You may have agreed to 
their privacy policy, but I haven't.


___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice


Re: [Libreoffice] Question about IAccessibility2

2011-11-22 Thread Caolán McNamara
On Mon, 2011-11-21 at 23:11 +0100, Regina Henschel wrote:
 I see them for some controls but not for all, especially not for 
 maLBEdgeStyle.

 (1) What they are used for?

Well, they're probably intended for accessibility support anyway, e.g.
screenreaders. Not sure however whether they're generic things which
could be explored under Linux with accessibility enabled on your desktop
and Orca, or if they're true IAccessibility things specifically for
windows accessibility.

 (2) Why they are set for some controls but not for all?

The IAccessiblity2 stuff was originally IBM sponsored IIRC. Couple of
announcements a few years ago that it would be integrated into
OpenOffice.org, I think that some of it did get integrated in eventually
before Oracle pulled out of OOo, but quite possibly the a11y stuff
lagged far behind the other code changes over the years and its simply
out of sync. e.g. a11y based on 1.X.y/2.X.Y OOo merged into a 3.X.Y OOo

 (3) Do I have to define such a string for my new linecap style list box?

Not sure, can't hurt anyway :-)

C.

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice


[Libreoffice] Question about IAccessibility2

2011-11-21 Thread Regina Henschel

Hi all,

I have started to implement the attribute stroke-linecap. I come 
across IAccessibility2 in files

/core/cui/source/tabpages/tabline.hrc
/core/cui/source/tabpages/tabline.src
There are some string resources defined like
#define STR_END_LENGTH  41
Some are commented out in lines 125 to 134 in tabline.hrc. Such string 
resources are used in method SetAccessibleName in

/core/cui/source/tabpages/tpline.cxx

I see them for some controls but not for all, especially not for 
maLBEdgeStyle.


(1) What they are used for?
(2) Why they are set for some controls but not for all?
(3) Do I have to define such a string for my new linecap style list box?

Kind regards
Regina
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice