On Aug 16, 2016, at 3:57 PM, Leonard Rosenthol <lrosenth@adobe.com> wrote: > > For example (and I know this will be contentious), while a PWP _CAN_ be made accessible through the use of the OWP technologies – an author doesn’t have to do that if they don’t wish to do so. And the current text implies that every PWP would be… I don't think I fully understand this statement. I would argue that an author has a moral (and often legal) obligation to create accessible content, and the file format and rendering system should be designed to maximize accessibility. Yes, it's possible to create inaccessible content in HTML and in EPUB. But we should design PWP so making accessible content is easy and natural, and making inaccessible content is difficult. I also think it's within the scope of PWP to investigate ways of ensuring all (or most) content is accessible. To put it another way, are you proposing a use case for making content inaccessible? Your suggested edits change accessibility and privacy "musts" to "shoulds", as well as shifting the obligation from the underlying technologies to the author. Dave
Received on Tuesday, 16 August 2016 20:28:02 UTC