E-mail List Archives
Re: soft hyphens hard coded
From: wolfgang.berndorfer@zweiterblick.at
Date: Jan 12, 2021 11:48AM
- Next message: Brooks Newton: "Known accessibility hurdles with popular JavaScript frameworks"
- Previous message:
: "Capturing the screenreader events to a text file" - Next message in Thread: None
- Previous message in Thread: Patrick H. Lauke: "Re: soft hyphens hard coded"
- View all messages in this Thread
For me all perspectives are interesting: Browser implementation, WCAG requirements, usability for SR and easy to read.
-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Patrick H. Lauke
Sent: Tuesday, January 12, 2021 5:36 PM
To: <EMAIL REMOVED>
Subject: Re: [WebAIM] soft hyphens hard coded
On 12/01/2021 16:27, <EMAIL REMOVED> wrote:
> I completely agree to your objections on a triple-A level. (3.1.5
> Reading Level and 3.1.6 Pronunciation are AAA)
>
> Seems, ­ won't serve as a sufficient technique for 3.1.6., since it doesn't provide techniques for any reading level.
Also, just to be clear...we're talking about UAAG here. Which is aimed at what user agent should do/provide. Not what authors marking up content should or shouldn't do.
P
--
Patrick H. Lauke
https://www.splintered.co.uk/ | https://github.com/patrickhlauke
https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
twitter: @patrick_h_lauke | skype: patrick_h_lauke
- Next message: Brooks Newton: "Known accessibility hurdles with popular JavaScript frameworks"
- Previous message:
: "Capturing the screenreader events to a text file" - Next message in Thread: None
- Previous message in Thread: Patrick H. Lauke: "Re: soft hyphens hard coded"
- View all messages in this Thread