W3C home > Mailing lists > Public > public-css-archive@w3.org > April 2019

Re: [csswg-drafts] [css-text] text-transform's design, intent and reality resolution (#3775)

From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
Date: Thu, 04 Apr 2019 00:52:36 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-479709213-1554339156-sysbot+gh@w3.org>
From the post telcon discussion, a few points which I though were worth recording (other people who were there feel free to correct my interpretation or add other points):

- From @frivoal: Current reality (factoring in assistive tech and other things like reader mode) is that text-transforms of case may or may not be exposed to end users & so we should not create/encourage any situation where the meaning of the content _relies_ on the transformed text always being exposed _or_ never being exposed.

- From @fantasai: Ideally, ATs would get the untransformed text plus information about the transform style applied (similar to how they get information about bold, italic, etc.).

- From @AmeliaBR: Given the compat concerns and the amount of software involved, changing the value that is exposed for the primary text is likely to be problematic.  So, probably need to keep exposing text after case transforms. But it might be possible to add a way to expose the untransformed text as a progressive enhancement.

  @atanassov strongly reiterated the complexity of the software ecosystem (browsers give data to platform specific APIs which are also used for other applications or document types, and the APIs then pass it along to specific tools like screen readers) and how in many environments this software is not well maintained. So changing well-established behavior is very bad, and adding new features is complicated.

- From @frivoal: The compat concern isn't an issue for new transformations, and compat needs might actually require different handling of these transformations.  The current pattern of exposing post-transformation text would create an accessibility _regression_ if browsers started recognizing e.g. the `full-width` transformation and exposing full-width characters to a screen reader (e.g., VoiceOver) that reads them out by reading out the full name of each character instead of reading out the words.

GitHub Notification of comment by AmeliaBR
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3775#issuecomment-479709213 using your GitHub account
Received on Thursday, 4 April 2019 00:52:38 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:46 UTC