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 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.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 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 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 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
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
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
