Hi everyone, I'm withdrawing this intent.
With a discussion with the accessibility team, we found this approach (based on alternative text) problematic. We'll try a different approach via CSS AAM <https://w3c.github.io/css-aam/>. This will allow us to pass the original marker text + accessibility attributes (to be specified) to the platform AT and let them decide how to interpret it. On Thu, Sep 30, 2021 at 1:36 AM Yoav Weiss <yoavwe...@chromium.org> wrote: > Hey Xiaocheng! Should we consider this intent on hold until Tab's points > are addressed? > > On Friday, September 17, 2021 at 11:57:28 PM UTC+2 Xiaocheng Hu wrote: > >> On Fri, Sep 17, 2021 at 2:31 PM Tab Atkins Jr. <jackalm...@gmail.com> >> wrote: >> >>> On Fri, Sep 17, 2021 at 1:36 PM Mike Taylor <miketa...@chromium.org> >>> wrote: >>> > On Friday, September 17, 2021 at 4:16:26 PM UTC-4 Xiaocheng Hu wrote: >>> >> Update since I2P: The 'spell-out' value is not implemented because it >>> is currently unimplementable (crbug.com/1247764). As the spec requires >>> alphabetic counter styles with 'speak-as: auto' to use the 'spell-out' >>> value, we use 'words' instead. This aligns with what Firefox currently does. >>> > >>> > With 2 engines shipping (as soon as this ships, anyways) speak-as: >>> auto => speak-as: words, have you passed that feedback to the spec editors, >>> as the de-facto interoperable (and implementable) behavior? >>> >>> This feedback was provided in >>> <https://github.com/w3c/csswg-drafts/issues/6040#issuecomment-799868468 >>> >, >>> but I answered it in >>> <https://github.com/w3c/csswg-drafts/issues/6040#issuecomment-840874164> >>> with what should be an acceptable interim solution. There wasn't a >>> further reply from Xiaocheng, so I figured my suggestion was >>> acceptable; I guess that wasn't the case? >>> >> >> I somehow missed that... Let me discuss with our accessibility team to >> see how it works. >> >> >>> "words" will give a *broken* behavior to alphabetic lists; it would >>> mean that the 27th list item in an alphabetic list (with counter "aa") >>> would be pronounced as a single long a sound (as you can hear in >>> `speechSynthesis.speak(new SpeechSynthesisUtterance("aa"))`; the 28th >>> would be the word "ab", etc. I don't think this is acceptable for >>> screen-reader users. The interim solution I gave would read them out >>> correctly, as you can hear in `speechSynthesis.speak(new >>> SpeechSynthesisUtterance("a a"))`. >>> >>> ~TJ >>> >> -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFqEGhaBHX63HMYuCFzLaOfR41MR5xs5rBEDQmKuK4Bsw0exBA%40mail.gmail.com.
