Re: ISSUE-633 Changes ready for final review

Michiel please come to the call today. We were trying to avoid having an
unlimited number of types being fed. First, you don't know what type of
objects that are in a feed when you get into one. For example, if you were
tabbing and you landed on a link in an article in a feed would you know
that it was a link feed or an article feed?

We were trying to limit the scope for ARIA 1.1. It is a new concept.


Rich Schwerdtfeger



From: Michiel Bijl <michiel@agosto.nl>
To: Matt King <a11ythinker@gmail.com>
Cc: PF <public-pfwg@w3.org>, Richard Schwerdtfeger/Austin/IBM@IBMUS
Date: 11/12/2015 07:49 AM
Subject: Re: ISSUE-633 Changes ready for final review



All looks great! I'm not sure about the articlefeed naming. This name makes
it look like it is limited to the article element. Would dropping article
and simply naming it feed be an option? Then it could be anything (feed of
images, list items, links, sections, etc).

—Michiel

On 12 Nov 2015, at 12:18, Matt King <a11ythinker@gmail.com> wrote:

      Here is a High-level summary of the issue 633 changes contained in
      branch mck_issue633[1] that are ready for final review.

      1. Revised grid role description to explain how grid can be used to
      provide arrow key navigation and flexible layout for sets of
      interactive elements, such as links and buttons. The revisions also
      clarify focus management and the purpose of readonly in grids.

      2. Updated treegrid role to include new language about the readonly
      state from the revised grid role.

      3. Added articlefeed role so screen reader users can stay in reading
      mode while reading and scrolling through infinitely scrolling sources
      of information.

      4. Modified article role to support aria-setsize and aria-posinset
      when the article is contained in an articlefeed.

      5. Modified aria-busy to clarify its purpose and add support for the
      articlefeed role.

      The above is a reduced set of the original proposal. It does not
      resolve all aspects of issue 633, but covers all the most pressing
      use cases.

      I will put more detail into tracker in issue 633 and action 1505 when
      I close them.

      [1] http://rawgit.com/w3c/aria/mck_issue633/aria/aria.html


      Matt King