Re: Question on A.4.1 SC1

Hi Tim,

Perhaps we could reword A.4.1 SC1 from:

The authoring tool must conform to accessibility platform architectures 
(e.g. MSAA, Java Access, etc.).

to:

The authoring tool must follow the accessibility platform 
architecture(s) relevant to the platform identified in the conformance 
profile (e.g. MSAA, Java Access, etc.).

(And we should perhaps add the JVM to the examples in the confrmance 
profile area)

Thoughts?

Cheers,
Jan


boland@nist.gov wrote:
> A.4.1 SC1 mentions "conformance to accessibility platform architectures (e.g., 
> MSAA, JavaAccess, etc,)".   How can we require conformance to multiple 
> architectures (which may be different) at the same time?  Do we want to say
> "conform to an accessibility platform architecture .." (only one)?   However,
> if different authoring tools conform to different platform architectures,
> that might create interoperability problems..   
> 
> Also, what does it precisely mean for a tool to "conform" to an architecture?
> 
> Thanks and best wishes
> Tim Boland NIST  
> 
> "Quoting Jan Richards <jan.richards@utoronto.ca>:
> 
> 
>>The meeting was canceled today as only BF and JR were on the call by 4:15pm.
>>
>>So....here on the issues I need to settle for the public draft. For each 
>>I will include a default course of action (*) that I will take if people 
>>don't object:
>>
>>Reference:
>>http://www.w3.org/WAI/AU/2005/WD-ATAG20-20051005/WD-ATAG20-20051005.html
>>
>>
>>>- Definition of authoring tool.
>>
>>*=Use the proposed definition since it has been crafted to handle 
>>multi-tool conformance solutions:
>>
>>ATAG 2.0 defines an "authoring tool" as: any software, or collection of 
>>software components, that authors use to create or modify Web content 
>>for publication. A collection of software components are any software 
>>products used together (e.g. base tool and plug-in) or separately (e.g. 
>>markup editor, image editor, and validation tool), regardless of whether 
>>there has been any formal collaboration between the developers of the 
>>products.
>>
>>
>>>- Conformance Claims section
>>
>>*=keep it as shown in the internal draft.
>>
>>
>>>- Tactile, reading level, cognitive? comment in A.1.3
>>
>>*=leave this out.
>>
>>
>>>- undo for Web-based tools (A.2.7)
>>
>>*=Expand A.2.7 note to read:
>>"For all Web-based interface components, meeting checkpoint A.0.1 will 
>>serve to meet this checkpoint. Web-based browsers may rely on the undo 
>>function of the browser to perform the undo function of editing that 
>>does not involve server communication (e.g. typing in a text area). For 
>>this reason, the browser specified in the conformance profile must have 
>>the ability to perform at least one level of text entry undo."
>>
>>
>>>- definition of "technologies" - we decided to go with "content type" at 
>>>the Washington DC F2F.
>>
>>This needs discussion:
>>
>>We started using Content Type, but WCAG uses "Technology". Perhaps it 
>>would be best to return to "Technology" and use the WCAG definition with 
>>our own added examples:
>>
>>Technology
>>Technology means a data format, programming or markup language, protocol 
>>or API. (e.g. HTML, CSS, SVG, PDF, Flash)
>>
>>Cheers,
>>Jan
>>
>>
>>
> 
> 
> 
> 

-- 
Jan Richards, M.Sc.
User Interface Design Specialist
Adaptive Technology Resource Centre (ATRC)
Faculty of Information Studies
University of Toronto

   Email: jan.richards@utoronto.ca
   Web:   http://jan.atrc.utoronto.ca
   Phone: 416-946-7060
   Fax:   416-971-2896

Received on Thursday, 20 October 2005 14:35:25 UTC