Thread Subject: Re: Platform issues - Provision

Note

This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.

From: Peter Wallack
Date: Wed, Jun 27 2007 11:20 AM


I'm also struggling to assess item C in terms of the 'SkipNav'
provision. Does it mean that regardless of how a developer marks up a
page to adhere to 'SkipNav', the platform must expose the same
navigation mechanism to the user? I like that idea, but if I were a user
agent creator I would probably balk.

Peter Wallack
Accessibility Program Director
Oracle Corporation



Hoffman, Allen wrote:
> I must have missed this great provision! Way to go all.
> I think this one addresses all my "remote access" concerns nicely.
>
> Per better language for C, I don't have a clue how that would be done,
> mind is working. I think it is a "nice to have", but not a "have to
> have" item. it is very disconcerting and for some maybe even more
> disconcerting/debilitating to have multiple keyboard and operation
> structures for multiple platofmrs onscreen at the same time, but mostly
> it isn't a show stopper in my experience.
>
>
>
>
> Allen Hoffman -- = EMAIL ADDRESS REMOVED = ; v: 202-447-0303
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andi
> Snow-Weaver
> Sent: Wednesday, June 27, 2007 8:52 AM
> To: = EMAIL ADDRESS REMOVED =
> Subject: Re: [teitac-websoftware] Platform issues - Provision
>
>
> Here's where we have ended up on the platform issue.
>
> We have Peter's proposal for a provision (slightly reworded by me):
>
> <beginning of provision>
>
> Software that is both a 'platform', and an 'application' running on
> another platform shall:
>
> * a. expose the underlying platform's color, contrast, and other
> individual display settings to applications running within its platform,
> so that these applications can meet <reference Display Attributes
> provision [1]>.
>
> * b. define, expose, and translate accessibility service information
> between applications running within its platform and the underlying
> platform - so that those applications can meet <reference AT
> Interoperability provision [2].
>
> * c. mediate any keyboard control and navigation between the
> applications and the underlying platform, to provide for a consistent
> navigation mechanism between user interface elements inside the
> application and those outside of it.
>
> <end of provision>
>
> We're still looking for suggestions on better wording for item c.
> Anybody have any ideas?
>
> The issue is the ability to navigate into and out of an application
> using the keyboard. How about this?
>
> c. provide a consistent mechanism for moving the keyboard focus into and
> out of an application
>
> Please also see my next post on definitions related to platform issues.
>
> [1] Display Attributes: Applications shall utilize user selected
> contrast and color selections and other individual display attributes
> when the availability of those selections are developed and documented
> according to industry standards.
> --- Note that we have an in process action item to reword this to
> resolve the testability issues with "other individual display
> attributes" and "documented according to industry standards".
>
> [2] AT Interoperability:
> http://teitac.org/wiki/EWG:Draft_May_30#A._AT_Interoperability
>
> Andi
>
>


WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University