Still, consider that if the spoken feature is exposed to all users, it would raise awareness to more people when articles are not well formated for screen readers… And screen readers are not available in all languages, so the effort put into the speech synthesizer in new languages could benefit a wider userbase.

Best regards,

Bence

Le mer. 27 oct. 2021 à 16:18, Andy Mabbett <andy@pigsonthewing.org.uk> a écrit :

On Wed, 27 Oct 2021 at 13:59, Andreas Kolbe <jayen466@gmail.com> wrote:

>> > Not sure that duplicating the work of a range of screen readers is the
>> > best use of our resources.
>>
>> I agree; such functionality belongs in the user client (screen reader,
>> browser, whatever), not in the subject website.
>
> an excerpt from the marketing text

As a professional web manager (1994-2011), I had companies trying to
sell me such services regularly. And why wouldn't they, given the
number of websites they could sell it to, over, and over, and over,
again?

Equally consistently, people who /needed/ such assistance told us they
wanted it in the client, not the website; and that all they required
of the websites was to be web-standards-complaint (by which they meant
WCAG[1]).

[1] https://en.wikipedia.org/wiki/Web_Content_Accessibility_Guidelines

--
Andy Mabbett
@pigsonthewing
http://pigsonthewing.org.uk
_______________________________________________
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/WGVKKWNRSPQJH63CLV2OAUNFSCUUSQOU/
To unsubscribe send an email to wikimedia-l-leave@lists.wikimedia.org

-- Bence Damokos Sent from Gmail Mobile