Hi rich, Following are some concerns regarding the mapping for IA2:
1. doc-abstract is mapped to IA2_ROLE_LANDMARK, but it isn't specified a subclass of landmark, nor is it mapped to ROLE_LANDMARK for ATK. I think it should be mapped to IA2_ROLE_SECTION. 2. doc-colophon, doc-credit, doc-dedication, doc-epigraph, doc-example and doc-qna are all mapped to ROLE_SYSTEM_GROUPING. While this is a bit debatable, I'd argue they should be mapped to IA2_ROLE_SECTION, just as they are mapped to ROLE_SECTION for ATK. 3. I think doc-notice and doc-tip should be mapped to IA2_ROLE_NOTE. 4. This might need some deeper discussion, but I think it could be useful to expose the last value of doc-pagebreak as a page-number object attribute on all block elements until the next doc-pagebreak. This would make it much easier to retrieve the page number at any point, rather than having to search for the page break. Joanie, Alex, I'd appreciate your thoughts on this. I have a couple of comments regarding the module itself (not the mappings): 1. doc-pagebreak says "Name from: content", which precludes the name from being specified by the author. is this intentional, and if so, why? Arguably, the title attribute isn't content (though I haven't checked what the name computation stuff says about that). Even putting that aside, it seems like it might be useful to specify the number with aria-label or similar. 2. This creates a huge number of landmarks. This might be too broad a conversation for now, but one concern I have with regions (and now this) is that we end up with a lot of duplicate information when the landmarks also contain a heading, which they often do. So, for example, with a screen reader, we might get "Chapter 1. Getting Started, Chapter 1. Getting Started heading level 1"; we get it once for the chapter landmark and then once for the heading. We can try to use heuristics to work around this, but it seems like a red flag to me, especially if authors use aria-label instead of aria-labelledby (which makes it harder to heuristically squelch duplication). Thanks! Jamie On Tue, Sep 27, 2016 at 1:56 AM, Richard Schwerdtfeger <[email protected]> wrote: > Jamie, > > Here is the Digital Publishing ARIA module: http://rawgit.com/w3c/aria/ > master/aria/dpub.html > > Please review the IA2 mappings for the digital publishing semantics for > ARIA. http://rawgit.com/w3c/aria/master/dpub-aam/dpub-aam.html > Please let me know if you want to create anything new for any of this in > IA2 or if you see an issue. > > There are no new roles specified other than the use of the landmark role > you added. > > The digital publishing industry is using ARIA as the vehicle by which > publishers will annotate content. The digital publishing ARIA semantics was > derived by work done by DAISY talking books. > > Currently, the mappings have been reviewed and approved by Joanie (ATK) > and James Craig (Apple). > > Thanks, > Rich > > Rich Schwerdtfeger > >
_______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
