Re: A single URI

At 12:37 AM +0000 12/20/01, Jim Ley wrote:
>I'd asked this before, can you please show me where in the public drafts
>of the CC/PP protocols, examples implementations etc. there exists
>frameworks for describing users accessibiltity needs, I'm obviously
>missing everything, or the working group has published something quite
>different to what it's developing privately.

I'm still confused as to why you can't see the framework for such.
It seems obvious to me from reading the same documents.  I'm amazed
that you continue to insist otherwise.

>  >  This means that problems such as storing a
>>  database of capabilities for future browsers are solved.  CC/PP,
>correctly
>>  applied, should also solve the problem of non-identifcation of assistive
>>  technology (e.g. JAWS), since JAWS' capabilities _should_ be identified
>  > within a CC/PP framework.
>So that doesn't solve the need to have a database of what jaws means in
>Accessibiltiy terms and all others UAs and ATs - and how do I provide site
>developers with the functionality of Snufkin (my own browser, based on my
>own needs.)

Yes it does.  It just means that JAWS needs to provide part of a CC/PP
profile.  (Which means the user agent -- IE probably -- needs to have a
way to add those on, which can be used by AT devices.)

There's no need for a database of what JAWS means, there's just a need
for those user-agents to be made self-identifying under CC/PP as to
what their capabilities are.  (At no time does the CC/PP-enabled
server need to know what "JAWS" is, it just needs a profile which
includes those _capabilities_.)

--Kynn

-- 
Kynn Bartlett <kynn@idyllmtn.com>                 http://kynn.com
Chief Technologist, Idyll Mountain            http://idyllmtn.com
Web Accessibility Expert-for-hire          http://kynn.com/resume
January Web Accessibility eCourse           http://kynn.com/+d201

Received on Thursday, 20 December 2001 00:56:33 UTC