On Thu, Sep 29, 2016 at 1:27 AM, Richard Schwerdtfeger <[email protected]>
wrote:

> 1. I support fidelity between Linux and Windows platforms. So, I don't
> have a problem with IA2_ROLE_SECTION. We really have not used
> IA2_ROLE_SECTION anywhere in the Core mapping spec.
>
That's possibly because browsers currently use section as the role for HTML
divs, which are quite generic. However, I don't think this should preclude
its use for more semantic purposes.

So, we will need to investigate these roles:
>
> feed:
> ROLE_SYSTEM_GROUPING + object attribute xml-roles:feed
>
> figure:
> ROLE_SYSTEM_GROUPING + object attribute xml-roles:figure
>
> I would not change figure, as it aligns with HTML, but would you rather
> feed be an IA2_ROLE_SECTION?
>
No. I think grouping makes sense for feed. I realise this justification is
sketchy at best, but grouping doesn't seem to "fit" an arbitrary section of
text. I think of grouping as a group of some common type of thing; e.g. a
group of form controls or a group of feed items.

5. Regarding doc-pagebreak this will definitely take more discussion. So,
> you want to take the name and expose it as an object attribute? Seems
> redundant as this could be addressed with authoring practices (label or
> title is equivalent to the page number) and you could speak it accordingly.
>
I'm not suggesting that doc-pagebreak be any different as far as the dpub
ARIA module is concerned. The name would still be calculated using the same
rules. I'm just suggesting that this name also be exposed as an object
attribute on all top level objects on that page. The reason is that a user
may wish to query the page number at any given point in the document
(rather than waiting to encounter a page break). (A sighted user can just
glance down at the page number, but this is harder for a screen reader
user.) Without this attribute, we'll have to search the tree for a page
break object to get the number. So, it's just an optimisation at the
platform API level.

Jamie
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2

Reply via email to