29 Jun 2006


See also: IRC log


[IBM], JR, Jim_Allan, DPoehlman
Jim Allan




<scribe> Scribe: JR

JA: Came up with techs that seemed pretty simple, but didn't get comments...

<jallan> CP 2.3 Render conditional content

<jallan> example technique:

<jallan> Use onscreen text (linked to the long description) indicating presence of a

<jallan> long description.

JA: HPR actually does this now
... PP does your browser do this?

PP: Yes we can get long desc if the browser passes it through

JA: JAWS does it somehow - maybe walking DOM...
... So your screen reader isn't walking the DOM...it's waiting for the browser to pass through the stuff

PP: Right?


<parente> yes, right :)

JA: Brings DP up to date on discussion.

DP: If I'm navving will it show up?

JA: Yes - we are just documenting something that does already exist.

DP: What does Safari do?

JA: Don't know?

DP: Firefox?

PP: On windows, don't know.

JA: Question is: should we right a technique for this? - e.g. if long desc is available expose this through the right API

DP: Hope so

These are the current "Sufficient Techs":

To satisfy provision one of this checkpoint, the configuration may be a switch that, for all content, turns on or off the access mechanisms described in provision two.

To satisfy provision two of this checkpoint, the user agent may provide access on a per-element basis (e.g., by allowing the user to query individual elements) or for all elements (e.g., by offering a configuration to render conditional content all the time).

To satisfy the requirement of provision two of this checkpoint to allow the user to view the content associated with each placeholder, the user agent may either render the associated content in a separate viewport or in place of the placeholder.

JA: HPR does the third.

DP: Are you saying typically the info is meta info?

JA: Sometimes...longdesc is tricky - browsers aren't sure what to do.
... IE ignores, and other browsers to a variety of things.

<jallan> antother technique: user agent to send/expose information to the platform accessibility API for use by assistive technology that would make the information available to the user.

<jallan> add note: this technique is for user agent with assistive technology.

JR: Spirit of 2.3 may be "Render" - a tech to punt to AT may not be enough...
... Communication of things via API is covered in guideline 6

JA, JR: Maybe under 6.1 or 6.10.

PP: Just as good if browser handles it natively.

<parente> http://gnome.org/~billh/at-spi-new-idl/html/html/interfaceAccessibility_1_1Image.html

JA: So maybe we'll add to 6.1

<parente> http://gnome.org/~billh/at-spi-new-idl/html/html/index.html

PP: That's a link to case with long desc
... May not be the most stable URL's

<jallan> CP 2.4 allow time independent interaction

<jallan> The techniques for this checkpoint seem to be narrowly focused on

<jallan> multimedia. I think is should be broadened to address meta refresh, AJAX

<jallan> refresh, security timeouts, etc.

CP 2.4

JA: Right now it seems Multimedia centric...

JR: Should prob put in some rebognition that some typres of situations are out of ua control

PP: In Linux SR case DOM won't be exposed, but system does allow browser to pass along meta information etc

<scribe> ACTION: JA to Craft a few more points specifically for checkpoint 2.4. [recorded in http://www.w3.org/2006/06/29-ua-minutes.html#action01]

JA: So IBM is doing work on AJAX...is screen reader involved?

PP: Approach: Basic stuff where page is acting like an app, the SR just tracks focus events...
... For more complicated stuff like updated status information...there is lots of work on "watching" different areas, with different priorities etc.
... So far on windows, but on Linux side they will throw everything to accessibility platform

<jallan> *jim pf is member private? right?

CP 2.5

CP 2.5 Make captions, transcripts, audio descriptions available

example technique:

Allow configuration for embedded media player objects to be opened in

standalone non-embedded players to allow full access to the complete range

of functionality allowed in a particular player.

JA: Once documents what some browsers already do


JA: Important that UA doesn't know what the object is...
... Prob some kind of "embedded mode" for players like QT...
... Embedded mode versions often don't have the same options as standalone versions

JR: So we are really speaking to players that can embed themselves

<jallan> may add a note: user agent does not know what is in an object element, user only has control that the embedded play allows

<jallan> limited functionality. opening in a full player allows greater user control and functionality

JA: This true for PDF also...but user can say if they want it to open embedded or not

DP: Possible now to have PDF doc inside an HTML doc...with small embedded viewer

JA: Can screen reader get in?

DP: Yes but most screen reader controls don't work.

JA: That's it for the day...

Summary of Action Items

[NEW] ACTION: JA to Craft a few more points specifically for checkpoint 2.4. [recorded in http://www.w3.org/2006/06/29-ua-minutes.html#action01]
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.127 (CVS log)
$Date: 2006/06/29 19:05:08 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.127  of Date: 2005/08/16 15:12:03  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: JR
Inferring ScribeNick: JR
Default Present: [IBM], JR, Jim_Allan, DPoehlman
Present: [IBM] JR Jim_Allan DPoehlman
Agenda: http://lists.w3.org/Archives/Public/w3c-wai-ua/2006AprJun/0075.html
Got date from IRC log name: 29 Jun 2006
Guessing minutes URL: http://www.w3.org/2006/06/29-ua-minutes.html
People with action items: ja

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.

[End of scribe.perl diagnostic output]