Matt Garrish

But this is about intended consequences, not accidental side effects. The vendor will know if the DRM they are applying disables read aloud, for example, as it's their choice. As...

> Reading system limitations is another complicated topic. Yes, but the user does have some control over this through the ability to choose their preferred reading systems - or at...

I disagree. The current advice is underspecified at best. It doesn't even seem to indicate that you have to disclose that there are going to be known issues, or that...

The reading system capability issue I find problematic because that should be information they're providing the user up front rather than when they're buying content. Some offerings could be accessible...

> 1\. Variable definition for `unknown_motion_simulation_hazard` does not exist. > 2\. Variable definition for no_motion_simulation_hazard does not exist. These look like simple typos. Maybe from copying from the epub techniques....

> In the guidelines we have this note Ah, okay, thanks, I had searched on "pagination source" and "page source" and couldn't find anything. I should have kept going to...

Do we also need to flag the pull requests? The issue is marked as class2. (There aren't any other labels that would need to be applied? I don't want to...

This is what the epub techniques do by first setting the epub_version attribute to the latest standard declared in the metadata. I don't know if there are any validation rules...

Yes, this definitely looks like a bug as the "onVisual" access modes are marked as "visual indicators" now in the schema.org metadata. They're describing the nature of the visual content...

> They don't combine but you can [declare several `accessMode` for a publication](https://www.w3.org/TR/epub-a11y-tech-11/#example-metadata-entries-for-textual-and-visual-access-modes). Right, and the test we have now checks that there is only one accessMode declared and that...