W3C home > Mailing lists > Public > wai-xtech@w3.org > May 2007

Re: [navigation] premise: client software affords context prompting from labels of ancestors.

From: Al Gilman <Alfred.S.Gilman@IEEE.org>
Date: Thu, 17 May 2007 19:59:57 -0400
Message-Id: <p0611040bc2729a953c16@[192.168.1.100]>
To: wai-xtech@w3.org

>Hi Al,
>
>Can you give examples of 'author' and 'player' with respect to your 
>statement: "What do people think of this allocation of 
>responsibility between the author and the player?"

Let me try synonyms, I think they are clearer.

author:
- content creation segment
- data on the server
- whatever touches the content up until the point where it leaves the webserver

player:
- client side software
- browsers, plugins, OS and AT operating on the user's computer 
guided by user settings
and interactive gestures.

So what I mean by the "division of of responsibility" could be restated as:

author:
- responsibility of the authoring pipleline for what is in the data 
as it comes over the wire.
This includes content contributors, webmasters, QA teams and hired 
external site scrubs,
aided by whatever tools they use.

player:
- responsibility of the client-side software to interpret the data 
received over the wire.

My terms are my personal code, so I don't know in what way they are 
missing you.
Sorry this is so verbose, but does this help?

Al

>cheers,
>David
>
>Al Gilman wrote:
>>
>>
>>In all this discussion, I am assuming one thing.  I think that PFWG is also
>>assuming this.  This post exposes this assumption to see if others think
>>it is sound.
>>
>>This is that labels that appear in the context of (up the ancestor
>>chain from) a current node in the tree (focus point or reading point)
>>are actually used in assistive presentation as relevant to answering
>>the two cardinal accessibility questions:
>>
>>a) Where am I?
>>b) What is _there_?
>>
>>The idea is that the processor with hands on of the final user experience
>>will either a) announce context as the user exercises navigation other
>>than "just play it" reading, or at least b) the user can at any time query
>>the UI and get the context info, as with the 'q' command in Fire Vox.
>>
>>My impression is that such queries are not unique to Fire Vox but a 
>>reasonably
>>common practice in screen readers.  Could it be they are sometimes called
>>'inspect'?
>>
>>What do people think of this allocation of responsibility between the author
>>and the player?
>>
>>Al
Received on Friday, 18 May 2007 00:00:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 13:15:42 GMT