Re: Issue-742: Proposal aria-destination

Hi Alex,

So, if you were reading a link and you ran across a link you would like to
know if it actually went to a glossary definition or a foot note or some
other special destination. If you are a book publisher you would probably
style these differently. So rather that placing a superscript around the
foot note number you might have a span with aria-destination. The book
publisher would then use an attribute selector to style the foot note links
as superscripts with potentially a different color.

I agree the destination is like a subrole in that it provides more detailed
semantics about the link type/role. If you were a screen reader user you
might see the link and determine that it goes to a foot note and you may or
may not be interested in that information. Or you might tailor your screen
reader to find the foot note and expand on "where am I" to state that it is
a foot note and read the footnote to the user.

Rich


Rich Schwerdtfeger



From:	Alexander Surkov <surkov.alexander@gmail.com>
To:	Joseph Scheuhammer <clown@alum.mit.edu>
Cc:	"W3C WAI Protocols & Formats" <public-pfwg@w3.org>
Date:	10/16/2015 11:45 AM
Subject:	Re: Issue-742: Proposal aria-destination





On Thu, Oct 15, 2015 at 4:15 PM, Joseph Scheuhammer <clown@alum.mit.edu>
wrote:
  Hi Alex,

  On 2015-10-15 11:59 AM, Alexander Surkov wrote:
   How is it different from accessible name?

  The values of @aria-destination are a token list.  Accessible names are
  arbitrary strings.

  It can be thought of as a sub-role.  For example, the role is still a
  link, but in some cases it's a link to the home page; in others, to a
  glossary entry, and so on.

I mean that typical example probably will be <span role='link'
aria-destination='home'>Home</span>, i.e. both aria-destination and
accessible name provide same information. So if nobody needs to process
that info programmatically, for example, if AT is going to announce
human-readable part only, then probably there's no need for
aria-destination.

  In that way it's similar to the @rel attribute, as has been pointed out
  in other threads.

Right, it's good point why @rel attribute cannot be reused.


   Can I have an example how assistive technology will use it?

  It's not clear whether it would be used by an assistive technology.
  That's under discussion.  But, as a data point, the ARIA documents all
  have a glossary, and links to the definitions are scattered throughout.
  Those links are styled differently than other links and it's obvious at a
  glance that they are glossary links (well, obvious to an editor).

I see. Perhaps the semantic bit here is link type (aka normal link or
definition link) rather than link target. So I would go with new role for
this example.


  --
  ;;;;joseph.

  'Array(16).join("wat" - 1) + " Batman!"'
             - G. Bernhardt -