RE: article navigation

Agree, AT design out of scope. but my $0.02 is that there is no need for a
special feed nav mode. However, all AT should provide article nav that is
separate from landmark nav.

 

From: Cynthia Shelly [mailto:cyns@microsoft.com] 
Sent: Tuesday, December 1, 2015 10:45 AM
To: Richard Schwerdtfeger <schwer@us.ibm.com>; James Craig
<jcraig@apple.com>
Cc: public-aria@w3.org; PF <public-pfwg@w3.org>
Subject: RE: article navigation

 

Our touch navigation uses modes (headings, items, paragraphs, etc.) with
next/previous gestures. I believe the rotor on iOS is similar. One approach
would be to have a mode for feed navigation.  Adding modes doesn't work
forever, however. When you have too many, switching between them takes too
long and can be confusing. Another would be to leverage an existing mode
like paragraphs, containers or landmarks.

 

This is a question of AT UI design though, which seems out of scope for this
working group.

 

From: Richard Schwerdtfeger [mailto:schwer@us.ibm.com] 
Sent: Tuesday, December 1, 2015 10:01 AM
To: James Craig <jcraig@apple.com <mailto:jcraig@apple.com> >
Cc: public-aria@w3.org <mailto:public-aria@w3.org> ; PF <public-pfwg@w3.org
<mailto:public-pfwg@w3.org> >
Subject: Re: article navigation

 

So, one of the things we have added is a "feed" role that takes a list of
articles. So, at least in this instance you know that articles within a feed
are part of the feed. The user needs to be able jump between articles within
a feed without and still be able to navigate the contents of each article.
Facebook will be implementing for its infinite feeds. They implemented these
"J" and "k" keyboard commands to navigate among the articles (you can try it
on Facebook). This won't fly in a mobile touch device so I was hoping we
could leverage something you were doing for articles. ... however if you
have suggestions about how that could be done on a mobile device that would
be great. 

I have a product team who can already make use of feeds. I am not sure if
you looked at it yet but here it is:

 <http://www.w3.org/TR/wai-aria-1.1/#feed>
http://www.w3.org/TR/wai-aria-1.1/#feed



Rich Schwerdtfeger

James Craig ---11/30/2015 08:56:44 PM---> On Nov 30, 2015, at 11:52 AM,
Richard Schwerdtfeger <schwer@us.ibm.com <mailto:schwer@us.ibm.com> > wrote:
>

From: James Craig <jcraig@apple.com <mailto:jcraig@apple.com> >
To: Richard Schwerdtfeger/Austin/IBM@IBMUS
Cc: PF <public-pfwg@w3.org <mailto:public-pfwg@w3.org> >, public-aria@w3.org
<mailto:public-aria@w3.org> 
Date: 11/30/2015 08:56 PM
Subject: Re: article navigation

  _____  





> On Nov 30, 2015, at 11:52 AM, Richard Schwerdtfeger <schwer@us.ibm.com
<mailto:schwer@us.ibm.com> > wrote:
> 
> Hi James, 
> 
> Does VoiceOver have a gesture navigation capability to move among articles
on iOS?

No. VO has a rotor for landmarks, but article is not a landmark. 

Also, are you referring to ARIA's article role, or HTML's <article> element?
IIRC, there was also some concern that the <article> element was being
overused, and a direct 1:1 mapping to the ARIA article role would result in
false positives. We'd need heuristics in the engines to snuff of the
extraneous articles like we have for layout tables and listitis overuse.

James

PS. "feed" seems a out-of-scope for a 1.1 criteria, does it not? Why is a
list of articles in a feed more or less semantic than a list of article
outside a feed? Does the end user need to know about the difference? If not,
cut it.