Matt Garrish

I was going to suggest the epub4 repository could just be deleted as we never used it, but then I discovered all the [neat stuff](https://w3c.github.io/epub4/#abstract) it does... No strong opinion...

I also seem to recall we changed from the original "epub-revision" name from the idpf days to "epub-specs" because we added "epub-tests" and didn't want too generic a name. That's...

I wonder if it would be useful to create a w3c/epub repository and use it as a directory to get to all our other repositories? (epub-specs, epub-tests, publishingcg, publ-a11y, etc.)...

> Do you mean a repository with a single readme file pointing at the other repositories? Ya, make it a directory page. You can turn off the issues tab in...

> I presume disallowing issues makes it still possible to commit new versions of the readme file Right, all it does it take away the issues tab so no one...

> I think we should find a solution that works natively with browser rendering engines The closest we have is `aria-flowto`, but it's limited to elements within the current document....

I don't know that the distinction is meaningful to users, though. If it is, why don't we also have graphsOnVisual? We could probably keep diagramOnVisual if we only wanted one....

Could try improving the definitions to say that diagramOnVisual is for visual representations of concepts while chartOnVisual is for visual representation of data? Would that make them distinct enough to...

As I mentioned on the call yesterday, the only case for refines for accessibility metadata is on the certifier information you've noted in the Accessibility 1.1 specification. Looking at the...

> Macmillan Learning has two conformsTo statements Then it should be incorporated into the xpaths. It probably complicates the display a bit, though.