- From: Krzysztof Maczyński via GitHub <sysbot+gh@w3.org>
- Date: Sun, 05 Apr 2020 02:08:35 +0000
- To: public-css-archive@w3.org
I think that AT are actually doing two thing which conceptually (and would it be practical to give users the choice actually?) are very different modes of operation. It's mixing them that causes confusion. 1. Rendering a document in speech media. 2. Representing aurally what's visible (or would be) on the screen. CSS only specifies requirements for 1 and they entail ignoring properties which are for visual media only (though not `display: none` or structural pseudoelements). For 2 those tools could do anything, including consulting `text-transform`, `display: block` and other CSS properties. -- GitHub Notification of comment by ByteEater-pl Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3775#issuecomment-609117538 using your GitHub account
Received on Sunday, 5 April 2020 02:08:37 UTC