W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 2007

Re: Minutes from User Agent Teleconference for February 15 2007

From: Jan Richards <jan.richards@utoronto.ca>
Date: Tue, 20 Feb 2007 13:57:37 -0500
Message-ID: <45DB44A1.4050001@utoronto.ca>
To: WAI-UA list <w3c-wai-ua@w3.org>

My action items:

(1) ACTION: JR to will do 3e

3e. Improve statement of configuration requirements for resolving 
settings/preference negotiations (e.g. between platform, browser, 
javascript, and author created preferences - accesskeys, ajax stuff)

REWORDED AS:

3e. Better address the interaction of preferences that are set by 
various levels of technology (i.e. platform, browser, content) and by 
different actors (e.g. authors setting accesskeys and creating custom 
controls, browser-users setting keyboard preferences).


(2) ACTION: JA JR Work 3 points at bottom into section 2

1. flash/media-player/PDF - own ui, implements accessibilty api (part of 
infrastructure), provides content , both a model and the view, not part 
of the HTML DOM , embedded object (in HTML), may have own DOM/API, may 
expose public API so others can get at the information

COVERED BY 3 a i.


2. UIUC accessibility extension - extension to view (using api to get 
information), consumer of existing model, extents the browser ui to 
provide information to end user. using the DOM

COVERED BY 3 f.


3. web application - own ui (provided by the author, not the model), 
repurposes functioning of standard controls and creates custom controls 
[author must use WEB-ARIA to be accessible], doesn't implement 
native/platform API.

ADD AS 3 a iv.: Web applications using custom controls, not recognized 
by browsers (ARIA will be relevant).


(3) ACTION: JR,JA will do 2a, 2b

2a. Investigate modularizing the document to focus on "base" browsers 
while also addressing voice browsers, speech input, etc. when this is 
relevant.

2b. Ensure "base" browsers include "core" browser features for people 
needing some accessibility support but who do not use AT (especially 
keyboard access to tooltips, mouseovers, etc.)

COMBINED AND REWORDED AS:

2a. Consider modularizing the UAAG 2.0 document. One module would 
address "core" browser capabilities (i.e. features for people needing 
some accessibility support, but who do not use assistive technologies) 
Other modules might address voice browsers, speech input, etc. that, 
while important, are not as relevant to "basic" browsers.




Cheers,
Jan



Jan Richards wrote:
> 
> http://www.w3.org/2007/02/15-ua-minutes.html
> 
> Action Items:
> 
> Refers to numbering in: 
> http://www.tsbvi.edu/technology/uawg/UA_requirements-14feb07.html
> 
> ACTION: KF to 3f
> ACTION: CL to will do 3a,b,c,d
> ACTION: JR to will do 3e
> ACTION: JA to will do 3h
> ACTION: PP to will do 1d
> ACTION: JA to will do 1c
> ACTION: JA to will do 1e
> ACTION: KF to will do 1f
> ACTION: JA to Will do 2c
> ACTION: JA JR Work 3 points at bottom into section 2
> ACTION: JR,JA will do 2a, 2b
> ACTION: JA to Clarify thoughts about use cases.
> 
> 
> Cheers,
> Jan
> 
> Jim Allan wrote:
>> W3C User Agent Teleconference for February 15 2007
>> -------------------------------------------------------------
>> Chair: Jim Allan
>> Date: Thursday, February 15 2007
>> Time: 2:00-3:00 pm Boston Local Time, USA (19:00-20:00 UTC/GMT)
>> Call-in: Zakim bridge at: +1-617-761-6200, code 8294#
>> IRC: sever: irc.w3.org, port: 6665, channel: #ua.
>> -------------------------------------------------------------
>>
>> Please send RSVP or additional agenda items to the list.
>>
>> Agenda Items
>>     1. Review and Revise "Requirements Document"
>>         www.tsbvi.edu/technology/uawg/UA_requirements-14feb07.html
>>
>>     2. Issues
>>         a. Should we include use cases to help define user agents?
>>             Examples: Multimodal Use Cases
>> http://www.w3.org/TR/2002/NOTE-mmi-use-cases-20021204/
>>             Compound Documents 
>> http://www.w3.org/TR/2005/WD-CDFReqs-20051219/
>>
>>         b. Consider expansion/explanation of individual items (see 
>> WCAG 2.0
>> Requirements)
>>             http://www.w3.org/TR/2006/NOTE-wcag2-req-20060425/
>>         c. ???
>>
>>     3. Calendar for meetings in March.
>>
>>
>> Jim Allan, Webmaster & Statewide Technical Support Specialist
>> Texas School for the Blind and Visually Impaired
>> 1100 W. 45th St., Austin, Texas 78756
>> voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
>> "We shape our tools and thereafter our tools shape us." McLuhan, 1964
>>
>>
> 

-- 
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 Tuesday, 20 February 2007 18:58:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:51:39 GMT