Meeting minutes
<Ralph> https://
<zheng_xu> wendyreid: We will hold digital publishing salon to gather use cases and ideas about what comes next for digital publishing
<zheng_xu> ... goal is to gather people in digital publishing and expose ideas. Everyone is welcome to attend.
<zheng_xu> ... Will talk about future digital publishing on web
<zheng_xu> liisamk: next introduction about EAA
<zheng_xu> cristina: about EAA there is still discussion ongoing
<zheng_xu> ... even though supposed to be done by june 2022 but still under discussion
<zheng_xu> ... in Italy it's approved by government
<zheng_xu> ... in Italy there will be organization to involve deeply into a11y related web activity
<zheng_xu> ... the other is about penalty
<zheng_xu> ... could be 5000 Euro or so
<zheng_xu> ... in case was requested to compliance but failed to do in Italy
<zheng_xu> ... items in backlist is supposed to applied by 2025
<zheng_xu> ... in France there is discussion that to achieve compliance might introduce cost
<zheng_xu> ... many factors are needed to be considered hope we can have some number around about impact of compliance
<zheng_xu> ... From Danish gov, the commission is asking if a11y is considered as responsible of retailer and it's considered as responsibility of publishers
<zheng_xu> ... About metadata Italy is doing experiment about a11y metadata with some large publisher and projects
<zheng_xu> ... will be sharable next month
<zheng_xu> ... next week we will send out some update about bookfair
<zheng_xu> ... Germany is still under discussion about reading system but we will have more information soon
<zheng_xu> Bill_Kasdorf: How about a11y in other countries in EU?
<zheng_xu> cristina: There are also other movement happening right now such as Poland and Danmark. The deadline for EU might be postponed.
<zheng_xu> liisamk: in Italy the fine could be between 5K to 40K Euro is it for a single incident?
<zheng_xu> cristina: this could be for a bank, or other cases depends on the level of the problem.
<zheng_xu> ... I don't think when you have one book is not accessible then you will be applied to the fine
<zheng_xu> ... the fine will likely to be applied to the case systematically not accessible
<zheng_xu> liisamk: is there any data being shared cross Europe about which violation is happening and fine?
<zheng_xu> cristina: it depends on. It is usually happening when there is a complaining.
<zheng_xu> ... and the fine rate could be applied differently according to region
<zheng_xu> laurent_: about situation for France I don't have any legal update yet. But the current work is store and readers are trying to be aligned with a11y meta data
<zheng_xu> ... we are sending out survey and got some result.
<zheng_xu> ... now we have some label for bookstore for vision impairment
<zheng_xu> ... we are still gathering feedback
<zheng_xu> ... about fine we are still asking
<zheng_xu> ... but publisher should be careful about that
<zheng_xu> wendyreid: It seems in Germany it's prompted by consumer complaining which is similar as Canada
<zheng_xu> ... needed to be able to demostrate publisher and stores are improving a11y to avoid fine
<zheng_xu> cristina: Yes in Europe it also depends on each legislation
<zheng_xu> Daihei: How will be monitoring a11y compliance in EU?
<zheng_xu> cristina: the nation level will be done by each country instead of EU. The commission will organize some monitor activity in EU level working with each country
<zheng_xu> ... The commission might intervene but the implementation is left to each country
<zheng_xu> ... there will be a checking of status and problems happen once in a period from the commission
<zheng_xu> liisamk: There is some concern from publisher that it might be easier to retrieve book from public than compliance with a11y.
<zheng_xu> cristina: the whole service needs to be accessible. If there is some reason it is difficult to be accessible then need to explain.
<zheng_xu> ... such as just less sales vs cost of being accessible
<zheng_xu> ... Also the timeline is not just for digital publisher but also public service wide
<zheng_xu> wendyreid: Audio books might fail in one perspect regarding transcription. Will transcription be required in EU?
<zheng_xu> cristina: The audiobook itself is not included unless it's speech track inside one ebook.
<zheng_xu> ... as far as I know in EU the audiobook case is still very small
<zheng_xu> liisamk: next agenda item - talk about how we think about a11y in Penguin Random House
<zheng_xu> ... we think all our books should be accessible. But we can not do it all at once.
<zheng_xu> ... we are doing ACE check with existing books. And check / validate about how we can improve
<zheng_xu> ... we wanted to achieve is not need to check a11y for each individual books later but to build a framework
<zheng_xu> ... we are going through a lot of upfront testing.
<zheng_xu> ... we are continue involving a11y improvement
<zheng_xu> ... we are also considering how reading system can support as well as how many quality complains about books
<zheng_xu> ... we need to do things in bite size chunk
<zheng_xu> ... it's hard to put amount on how to make books accessible. We understand that EAA is focusing on reflow book right now.
<zheng_xu> ... We are trying to achieve these items at first to make it in a managable segment.
<zheng_xu> ... we have tested a few design practice to make ebook more accessible such as figures with captions, use proper font and other validations
<zheng_xu> ... we are also looking at color contrast as well as color palette as well. Also trying to make book easy to navigate.
<zheng_xu> ... we are also trying to write good best practice to make book accessible
<zheng_xu> ... question is how far we can do. For example indesign does not support a11y well. Also sometimes publisher might create a book in a certain way.
<zheng_xu> ... we sit down with people and list out all images of the book. We have our survey document but we need a way to share to publishers and vendors.
<zheng_xu> cristina: if any comments on image description which is one of the major issue about digital book accessibility?
<zheng_xu> ... would consider also converting from PDF?
<zheng_xu> ... how about the work in e-commerce website
<zheng_xu> liisamk: we are keeping expanding our discovery. For example more story telling books are using emoji.
<zheng_xu> ... for converting we are converting epub2 to accessible way too
<zheng_xu> ... we don't have much PDF and we don't sell them.
<zheng_xu> ... we are also working on e-commerce website as well as reading system to offer accessible books
<zheng_xu> Adam: How about editorial books
<zheng_xu> liisamk: we are encouging editorial teams to provide accessible book as well.
<zheng_xu> ... For buy in of editorial team it still needs more steps
<zheng_xu> Bill_Kasdorf: Can you show how you improving a11y such as index to the industry
<zheng_xu> liisamk: we are happy to share
<zheng_xu> Bill_Kasdorf: this might need vendors support as well
zheng_xu: CG and A11Y task force
… the task force is working on metadata for how bookstores know that books are accessible,
… how publishers describe the a11y features,
… how readers will know what features the books have for them
Our github repo to submit issues to the PCG so that we can discuss and people can refer to
… a go to place to find more accessible data and best practices
… link to the use cases: https?//github.com/w3c/publishingcg/
… there is guidance for how to write use cases
… maybe you have questions for fixed layout books too
… how do you make them more accessible?
… these are very useful inputs for the a11y TF and our meetings every 2 weeks
… build up the community so that people can ask questions
… so people can get more answers and it does not need to be very formal
… anything that can help your real problems
… myth is that accessibility is difficult
… from my experience, we are only targeting one problem for an accessible book or a website
… WCAG AA is not that difficult
… mythi #2 is only for visual impairment and it is not
… it can be really hard to touch and minimal size for a clickable area is important for people
… myth #3 is about text to speech and whether that is mission accomplished
… in reality there are way more requirements to make a book accessible
… the reading order and accuracy of read out items is important
… reading speed and pitch need to be customizable for screen readers
<Bill_Kasdorf> that's the correct link
wendyreid: the question of best practices
… the link is http://
… there is a question of whether there are standards with retailers
… there really aren't at this point for what the retailers should display
… task force is testing to see what recommendations could work for the whole industry
Date: 30/31 August 2022
<shiestyle> Sorry, I will connect via zoom 30 min later.
<Murata> Publishing Salon in September
<Murata> Some will attend remotely, while others will, in person.
link to the Publishing Salon information: ttps://
<Murata> In JST Sep 14, 02:00
<jyoshii> PRSENT+
<Murata> Oops, 00:00 JST.
<jyoshii> EAA：クりスティーナ理事長の発言 国ごとに検討がされている現状だがイタリアでは2025年までにアクセシビリティ対応がどこまで進んでいるのかモニタリングが行われている。
<jyoshii> 罰則金額はマックス600万円近くになるといった報告がされた、
<jyoshii> イタリアの先行事例は
<jyoshii> 注視する必要がある。既刊分も含んで対応が求められることが明らかになってきている。
<jyoshii> コンテンツそのものの対応は出版社が主な当事者になる。書店はRSでの対応をするだけだから。
<jyoshii> 電子書籍サービス全体を捉えた場合、内容は出版社に帰属するという判断が強まっている。
<MURATA3> +present
<MURATA3> 欧州出版社が送ったオープンレターへの回答は？
<MURATA3> 分からない
<MURATA3> クリスチ０なに塩浜さんが質問する
<MURATA3> Certification organizationは各国では？
<MURATA3> これはEPUB Accessibility仕様に従っているかどうか
<MURATA3> Benetech?
<MURATA3> EAAは、European Accessibility仕様だけに限定しているわけではなく、そこに絞った認証機関の検討はまだない
<MURATA3> Benetechが、認証のサービスを行っている。
<MURATA3> とZhengが指摘
<MURATA3> 村田が、Benetechは認証の仕方を出版社にトレーニングしているだけだという理解
<MURATA3> LisaがPRHのアプローチについて資料を用いて説明
<MURATA3> CertificationについてはRPHではいまのところ行っていない
<MURATA3> 新刊での対応から始め、既存出版物についても対応していく
<MURATA3> 既存のものについては、EPUB2からEPUB3に変換したうえでアクセシブルにする。品質を向上させる。
<MURATA3> OCRの品質の悪さなど、初期にあった問題に対応する。
<MURATA3> 再変換も考慮する（マイナーアップデートだけではない）
<MURATA3> 既存のものは簡単なものから複雑なものへ
<MURATA3> 対応は社内、社外、プログラムによる自動化、手作業などいろいろありえる
<MURATA3> MM: You care everything!
<MURATA3> 新刊は5000 books a year. 50はアクセシブルに
<MURATA3> ハイプロファイルなものを優先する。
<MURATA3> MM: 普通に作ると注は、盲人には読みに行くと戻ってこられないものになります。
<MURATA3> Zhengが日本語で説明
link to PCG github repo: https://
<MURATA3> MMコメント: Zhengは、アクセシビリティは視覚障害者のためだけでなく、読み上げがすべてなわけでもないという重要な指摘を行っています。日本では誤解がとてもとても多い。
<MURATA3> ところで
<MURATA3> きょうのミーティングは何時までですか？
<MURATA3> When will we close this meeting?
<shiestyle> I think it will be until 10:30 JST.
<MURATA3> MMコメント: 国会図書館の最近の調査が、日本において必要なアクセシビリティ機能について包括的な調査をしています。
<MURATA3> 鎌田さんの質問: 意味のある
<MURATA3> alt textとは何で、ないalt textとは何か？
<MURATA3> Lisa: alt textは大変だが、圧倒されないように、ちゃんと分類して対処する必要がある。
<MURATA3> チャートなどは難しい。ガイドラインがあれば、それを参考にする。
<MURATA3> この件についての85ページのガイドラインが社内にある。
<MURATA3> あまりに大変なものは後回しにする
<MURATA3> 木達さんが、この件についてのW3Cのガイドラインがあることを指摘。Lisaが、それを参考にはしているが、書籍には当てはまらない部分もある。
<MURATA3> MM: 障害者権利条約対日審査が情報アクセシビリティについても含んでいます。二年後には、またあります。
<MURATA3> MM: 二年後にはジュネーブで、日本の電子書籍アクセシビリティについても審査されるでしょう。
<MURATA3> MM: EPUB Accessibilty 1.1には、1.0ですぐ始めるべきと書かれています。
<MURATA3> MM: Aceの日本語化はすでに行われています。
<MURATA3> MM: JDCは、日本語アクセシビリティメタデータの登録をW3Cで始めます。皆さんのご意見は歓迎します。