On 22/06/2022 14.44, Jason White wrote:
Note also that GTK 4 implements its own accessibility API, which, under
Linux, connects directly to the running AT-SPI 2 demon. This approach
may be an option in the future when the GTK 4 accessibility support
matures. In other words, GTK is migrating
...@lists.freedesktop.org
Subject: Re: [libreoffice-accessibility] Re: ESC meeting minutes: 2022-05-26
[IAccessible2 support in JAWS]
On 09.06.22 11:21, Michael Weghorn wrote:
> I suppose that supporting new UIA concepts/features in addition would
> probably require more fundamental changes than "just&qu
Hi Marco, all,
On 09/06/2022 09.39, Marco Zehe wrote:
AFAIK, QT exposes accessibility information to UIA on Windows. They switched
over from an MSAA implementation to UIA some time in the QT5 time frame:
https://www.qt.io/blog/2018/02/20/qt-5-11-brings-new-accessibility-backend-windows.
@global.libreoffice.org
Cc: libreoffice...@lists.freedesktop.org; libreoff...@lists.freedesktop.org
Subject: Re: [libreoffice-accessibility] Re: ESC meeting minutes: 2022-05-26
[IAccessible2 support in JAWS]
Hi Marco,
On 08/06/2022 13.09, Marco Zehe wrote:
> JAWS does support IAccessible2, but o
ne I think. And getting Vispero on board for
JAWS support is an even bigger fish to fry.
Marco
-Original Message-
From: Jason White
Sent: Tuesday, June 7, 2022 9:34 PM
To: accessibility@global.libreoffice.org
Subject: Re: [libreoffice-accessibility] Re: ESC meeting minutes: 2022-05-26
On
Hi Marco,
On 08/06/2022 13.09, Marco Zehe wrote:
JAWS does support IAccessible2, but only if it needs to, like in Firefox, and
some parts of Chromium-based browsers. However, with the UI Automation
implementation for the latter becoming stronger, there might be a time when
JAWS moves to UIA
...@lists.freedesktop.org
Subject: Re: [libreoffice-accessibility] Re: ESC meeting minutes: 2022-05-26
[IAccessible2 support in JAWS]
Hi Christophe,
On 07/06/2022 12.14, Christophe Strobbe wrote:
> After some online searching, it seems that JAWS at least used to support
> IAccessible2, originally
essibility@global.libreoffice.org
Subject: Re: [libreoffice-accessibility] Re: ESC meeting minutes: 2022-05-26
On 7/6/22 06:07, Michael Weghorn wrote:
> I tried again with just a single screen instead of two, and then NVDA
> announces "Slide 1", then reads out the slide content, and when
On 07/06/2022 21.34, Jason White wrote:
Yes. If I recall correctly, under MS-Windows/PowerPoint, NVDA and JAWS
both support arrow key navigation in the slide contents when the slides
are being presented (i.e., after F5 is used to start a presentation).
Ideally, one should be able to do the
Hi Christophe,
On 07/06/2022 12.14, Christophe Strobbe wrote:
After some online searching, it seems that JAWS at least used to support
IAccessible2, originally mainly for IBM Lotus Symphony.
According to a tweet by Marco Zehe from December last year, JAWS handles
Chromium and Edge via
Hi Michael, All,
(Apologies if this message has too many addressees; I'm not sure which ones I
should drop.)
After some online searching, it seems that JAWS at least used to support
IAccessible2, originally mainly for IBM Lotus Symphony.
According to a tweet by Marco Zehe from December last
On 07/06/2022 11.54, Michael Weghorn wrote:
Could you please explain what the expected (and actual) behavior would
be when showing an Impress presentation?
I think it makes sense to create a bug report to keep track of this (and
I'd be happy to do so, but don't know what to write).
(In a
On 31/05/2022 22.13, Jason White wrote:
On 31/5/22 14:11, David P Á wrote:
Other problem with accessibility is comments and tracked changes on
Writer. The issues with these systems make using Writer problematic in
professional settings.
I agree, and in particular, the screen
On 31/05/2022 14.20, Jason White wrote:
It seems to be very much a matter of unaddressed bugs and regressions.
The Document Foundation advertised a contract (presumably fulfilled by
now) to rewrite the accessibility regression testing infrastructure in
C++.
FWIW, that conversion to C++ is
On 31/05/2022 16.24, Christophe Strobbe wrote:
I don't have a comprehensive overview of LibreOffice UI accessibility either, unfortunately. However, if you are looking for ways to prioritise issues, one way may be based on the accessibility requirements in the ETSI standard EN 301 549, which
On 31/05/2022 12.36, Caolán McNamara wrote:
If the overview is there are a thousand little things and not a small
set of large scale specific projects then that's still a useful
overview. We could still sweep them into some general themes.
Indeed. Thanks for adding the subtopics that came up
On 31/05/2022 12.01, Colomban Wendling wrote:
* Only on-screen elements of the document are exposed to ATs. This is
on purpose probably for performance (not sure if we have any numbers to
base it on?) so elements are lazy-loaded and destroyed, but it has
non-trivial impact on various AT
On Tue, 2022-05-31 at 16:24 +0200, Christophe Strobbe wrote:
> Hi Michael, Caolán, all,
> ...
> (2) With regard to document formats, continue improving PDF/UA
> conformance for exported PDF documents. ... (Institutions that have
> been established to monitor compliance with the EU's Web
>
On Tue, 2022-05-31 at 09:41 -0500, Devin Prater wrote:
> A lot of toolbar widgets in Writer don't seem to be accessible, like
> the ones to create forms and such.
I created a sub category to capture the theme that various widgets have
accessibility failings, your toolbar case, the extension
Le 31/05/2022 à 01:57, Michael Weghorn a écrit :
On 30/05/2022 11.08, Caolán McNamara wrote:
For a11y I don't know what is seen as the major problems, is there some
fundamentally missing pieces (like in the past not having direct
windows IAccessible2 support and needing a java access bridge).
A lot of toolbar widgets in Writer don't seem to be accessible, like the
ones to create forms and such.
Devin Prater
r.d.t.pra...@gmail.com
On Tue, May 31, 2022 at 9:31 AM Christophe Strobbe
wrote:
> Hi Michael, Caolán, all,
>
> I don't have a comprehensive overview of LibreOffice UI
Hi Michael, Caolán, all,
I don't have a comprehensive overview of LibreOffice UI accessibility either,
unfortunately. However, if you are looking for ways to prioritise issues, one
way may be based on the accessibility requirements in the ETSI standard EN 301
549, which defines the
On Mon, 2022-05-30 at 23:57 +, Michael Weghorn wrote:
> On 30/05/2022 11.08, Caolán McNamara wrote:
> > For a11y I don't know what is seen as the major problems, is there
> > some fundamentally missing pieces (like in the past not having
> > direct windows IAccessible2 support and needing a
On 30/05/2022 11.08, Caolán McNamara wrote:
For a11y I don't know what is seen as the major problems, is there some
fundamentally missing pieces (like in the past not having direct
windows IAccessible2 support and needing a java access bridge). Or are
the fundamentals ok and its a matter of a
24 matches
Mail list logo
