Re: Two variants for the redefinition of "accessibility services of software"

very nice 

only one thing I think needs to be fixed.    

You discuss user agents as an example but don't have  non-web documents anywhere in either.   

also 

Below are the same text with NON WEB DOCUMENTS in the correct places

Because both notes contain User agents and virtual machines -- I think it reads better to reverse them (as shown below) (I didn’t fix the note numbering so you can see the switch)


Very nice 

gregg





platform software

The term platform software, as used in WCAG2ICT, has the meaning below:

platform software
collection of software components that run on an underlying software or hardware layer, and that provides a set of software services to applications OR NON-WEB DOCUMENTS that allow them to be isolated from the underlying software or hardware layer

Note 2: Sometimes platform software is also a software application (e.g. a user agent or a virtual machine).

Note 1: Examples of platform software include operating systems, user agents, and virtual machines.





accessibility services of platform software

The term accessibility services of platform software, as used in WCAG2ICT, has the meaning below:

accessibility services of platform software
services provided by platform software that are used by software OR NON-WEB DOCUMENTS to expose information about the user interface to assistive technologies

Note 1: These services are commonly provided in the form of accessibility APIs (application programming interfaces), and they provide two-way communication with assistive technologies, including exposing information about objects and events.

Note 2: Platform software that is also an application may simply expose the accessibility services of the underlying platform layer, rather expose its own set of accessibility services.  Alternately it may translate between the set it exposes and those of the underlying platform layer.


Gregg
--------------------------------------------------------
Gregg Vanderheiden Ph.D.
Director Trace R&D Center
Professor Industrial & Systems Engineering
and Biomedical Engineering University of Wisconsin-Madison
Technical Director - Cloud4all Project - http://Cloud4all.info
Co-Director, Raising the Floor - International - http://Raisingthefloor.org
and the Global Public Inclusive Infrastructure Project -  http://GPII.net

On Jun 4, 2013, at 8:46 PM, Peter Korn <peter.korn@oracle.com> wrote:

> Hi gang,
> 
> Coming out of our last meeting on 31June13, I have taken a whack at redefining "accessibility services of software" to make more central the concept that this is about platform software, and not all software generally.
> 
> Please see Proposal #3 at New glossary term "accessibility services of software and assistive technology"
> 
> In particular, please see both Variant #3a in which I keep our existing definition text, but simply change the title of the term to "accessibility services of platform software"; and then see Variant #3b in which I introduce yet another new term: "platform software", when I then leverage in next text for the retitled term "accessibility services of platform software".
> 
> Fundamentally Variant #3a is the more minimal / less invasive change, while Variant #3b makes fuller use of the "teachable moment" that our Technical Report affords us.  Please also note the section For reference, from ISO 13066-1 at the bottom of that wiki page, from which I draw on (but do not expressly mimic) that ISO text.  While it is somewhat tempting to lift definitions word for word from ISO 13066-1, those definitions leverage terms & concentps that have slightly different existing definitions in WCAG 2.0 (e.g. AT), and I am also unclear on whether such copying is of a copyright ISO standard is OK in a non-ISO document such as our TR.
> 
> Below both variants on the wiki page please see "Edits to other terms common to both Variants #3a and #3b" where I show show how the new term "accessibility services of platform software" would impact our two glossary terms "programmatically set" and "programmatically determined", as well as Principal 4 and Guideline 4.1 (the change is the same under both variants).
> 
> 
> I personally don't have a strong preference between Variant #3a and Variant #3b - different things attract me to each of them.  I solicit comments / feedback on them, ahead of a formal survey (perhaps tomorrow?) ahead of our Friday meeting.  I suggest we survey both approaches (as well as the follow-on edits to those two terms, the principal, and the guideline).
> 
> 
> 
> Peter
> 
> -- 
> <oracle_sig_logo.gif>
> Peter Korn | Accessibility Principal
> Phone: +1 650 5069522 
> 500 Oracle Parkway | Redwood City, CA 94065 
> <green-for-email-sig_0.gif> Oracle is committed to developing practices and products that help protect the environment