- From: MURATA <eb2mmrt@gmail.com>
- Date: Tue, 30 Apr 2024 21:54:23 +0900
- To: public-global-inclusion@w3.org
- Message-ID: <CALvn5EAwC8o12B-w5NY7WsQW4RE0cmNjNH27rNRwG95wUYf61A@mail.gmail.com>
1. CSS and XSL-FO in the 20th century Poor internationalization 2. Requirements for Japanese Text Layout Requirements only, no mechanisms Traditional typography for printed materials Working Group Note (2009 June) Working Group Note (2012 April) Working Group Note (2020 August) JLreq has had lots of impacts on CSS, EPUB, Unicode, and so forth No accessibility considerations 3. Lots of **Req Attempts to mimic the success of JLReq https://w3c.github.io/i18n-activity/projects/ https://www.w3.org/TR/typography/ 4. Requirements for Japanese Digital Text Layout Started in 2022 Digital text on screen Accessibility Requirements only, no mechanisms 5. Text to Speech of Electronic Documents Containing Ruby: User Requirements https://w3c.github.io/ruby-t2s-req/ 6. My estimation When can we have good understanding of A11Y requirements on **Req typograpy JLreq: 10 years? Others: 20 years? How can we make our specifications less harmful then? Regards, Makoto
Received on Tuesday, 30 April 2024 12:55:06 UTC