Hi Tzviya,

Do you want to have a table of contents appear like the navigation section
of a web page to an assistive technology. If you will have only one
navigation section in a book that is fine. However, if have more than one
and need to distinguish them then you need to either provide a label (that
requires translating), or you have to define a different role mapping in
which case you would subclass navigation and create a new role to be
mapped. In this scenario you could expose a role of "navigation" with an
ARIA but also provide a string role. ... something along the lines of the

                MSAA + UIA Express Role                 Expose as text string in AriaRole                        
 MSAA + IAccessible2 Role + Other IAccessible2 Features IAccessible2: Object attribute xml-roles:toc             
           UIA Control Type + Other Features            Expose as text string in AriaRole                        
                    ATK/AT-SPI Role                     ROLE_LANDMARK and object attribute xml-roles:toc         
                     AXAPI[Note 1]                      AXRole: AXGroup                                          
                                                        AXSubrole: AXLandmarkNavigation                          
                                                        AXRoleDescription: 'TableofContents'                     

Regarding subclassing abstract roles, you have the role "chapter" subclass
landmark in the aria-dpub spec. but you expose the the role as "chapter"
similar to above. I would also recommend that you require aria-posinset and
aria-setsize as properties of "chapter".

Does that make sense?


Rich Schwerdtfeger

From: "Siegman, Tzviya - Hoboken" <>
To: "DPUB-ARIA (" <>
Date: 08/06/2015 02:46 PM
Subject: FW: DPUB AAM

A question for the brainy lot of you:

I am looking at the DPUB AAM [1, 2] work that Joseph did and hoping to get
to some myself before our DPUB ARIA call this week. This is rather
unfamiliar ground for me, so please be patient.

My method is looking at the work Joseph has done against the DPUB roles [3,
4]. I then looked at the superclasses for the roles and their definitions
in the HTML AAM. These two roles are very different. Chapter is a subclass
of landmark, an abstract role. I see that the HTML AAM says not to make to
abstract roles, but I’m not sure how to handle the roles that subclass
abstract roles. I know Joseph mentioned reading documentation for each API,
but I was kind of hoping to avoid that. Any other way?

TOC is a subclass of navigation, and it just points to HTML AAM navigation
definition [5]. Is this the right method for all non-abstract roles?

I’d appreciate any tips.







Tzviya Siegman
Digital Book Standards & Capabilities Lead

Received on Thursday, 6 August 2015 21:21:30 UTC