Summary: | AX: text-transform: full-size-kana must not affect AT/speech output | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | fantasai <fantasai.bugs> | ||||
Component: | Accessibility | Assignee: | Joshua Hoffman <jhoffman23> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | andresg_22, jcraig, webkit-bug-importer | ||||
Priority: | P2 | Keywords: | InRadar | ||||
Version: | Safari Technology Preview | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
URL: | https://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A%3Cstrong%20style%3D%22text-transform%3A%20full-size-kana%22%3Eじゅう%3C%2Fstrong%3E%20must%20read%20the%20same%20as%20じゅう%20not%20じゆう%20(but%20look%20like%20じゆう%20not%20じゅう)%20.%3Cbr%3E%0A%3Cstrong%20style%3D%22text-transform%3A%20full-size-kana%22%3E%20カップ%20%3C%2Fstrong%3E%20must%20read%20the%20same%20as%20カップ%20not%20カツプ%20(but%20look%20like%20カツプ%20not%20カップ)%20.%0A | ||||||
Bug Depends on: | |||||||
Bug Blocks: | 245557 | ||||||
Attachments: |
|
Description
fantasai
2023-09-14 10:56:06 PDT
From some discussion with Elika, this might need to be limited to ruby, or at a minimum, we’d need test cases to make sure the other values (like text-transform: uppercase) were not affected by the change. Note that I’m still unclear as to why text-transform would be used in a way that affects the core meaning of the text, so perhaps we should discuss or require addition information before the change. > Note that I’m still unclear as to why text-transform would be used in a way that affects the core meaning of the text, so perhaps we should discuss or require addition information before the change.
This is explained in detail in the spec (linked above).
`full-width` should also get the same treatment (use underlying untransformed text for AT), fwiw. I disagree about `full-width`... That's mostly likely an AT bug in automatic language detection; the characters are unambiguous, but the AT is choosing the wrong voice language. Filed <rdar://133412477> for that. I'll also file a CSS spec issue for the "casing for accessibility" note, because it doesn't take into account the spacing context we discussed for AT like HoverText where rendered `full-width` chars would be expected. Created attachment 472124 [details]
testcase
FYI fantasai: https://github.com/w3c/csswg-drafts/issues/10732 Pull request: https://github.com/WebKit/WebKit/pull/32125 Committed 282258@main (00c8f4758364): <https://commits.webkit.org/282258@main> Reviewed commits have been landed. Closing PR #32125 and removing active labels. |