Date: prev next · Thread: first prev next last



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 currently still being worked on.

That's an important step, but once the testing is in place, someone is going to have to find and start fixing the bugs - then maintain the quality of the implementation over time.

Maintaining quality and avoiding regressions is where many accessibility efforts fall apart, whether in the free software world or in the products of large and well resourced corporations. There is also a tendency to implement solutions only partially, but not with good enough quality to satisfy the needs of the users. Being a large corporation with vast financial reasources doesn't necessarily resolve these difficulties. On the other hand, well organized and resourced free software projects can be remarkably successful in this area.

+1

--
To unsubscribe e-mail to: accessibility+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/accessibility/
Privacy Policy: https://www.documentfoundation.org/privacy

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.