- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Sat, 08 Jun 2019 21:25:17 +0000
- To: public-css-archive@w3.org
This point relates to the comment @tabatkins made in https://github.com/w3c/csswg-drafts/issues/3746#issuecomment-500024465 If we're in situation (1), then this isn't needed, but it is if we're in the others. Personally, my feeling is that the mathml mathvariant attribute should continue to be the main way that such variant letters are selected, and this attribute should be the thing that causes the accessibility tree to carry the transformed variant. In addition, it seems reasonable to also have the text-transform values, but these would not cause the text in the AT to be transformed (although there could/should an annotation in the AT indicating that the text has been transformed, separately from the text itself). These text transforms could certainly be used in the UA stylesheet as the mean by which the visual rendition is achieved though. This way: * alternative views, such as reader mode, would show the correct glyphs despide dropping all author css * alternative uses of these transforms (such as playful use as often seen in social media user names) could still be read as the original text (or be read out as transformed, if the screenreader so desires, using the metadata) If we wish to generalize the ability to character transform that affect the AT (and readermode) outside of mathml, what we should do is generalize the mathvariant attribute and allow it on arbitrary markup. But again, this depends on the answer to https://github.com/w3c/csswg-drafts/issues/3746#issuecomment-500024465 -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3745#issuecomment-500165288 using your GitHub account
Received on Saturday, 8 June 2019 21:25:18 UTC