JA: We reviewed their spec and
make our comments and cross-referenced the dependencies to our
UAAG 1.0 checkpoints.
... We re-wrote it based on our understanding of the language.
They came back to a higher priority.

JB: It would be a good
cross-group courtesy to work this out before it goes to
LC.
... it could be useful to invite cross-group discussion so that
our priorities can be synchonized. It could be difficult to
coordinate time-wise.

GR: the main editor is not
available for meeting today. They like the idea of "persistent
over session"
... we need to define what we mean by session. It is in the WAI
glossary, which is out-dated.

JA: Can we just put a period
after "persist"?

<AllanJ> old: If no key
attribute is specified, the user agent SHOULD assign a key
and

<AllanJ> alert the user to
the key mapping and the resultant user agent assigned

<AllanJ> key SHOULD persist
across sessions.

GR: That wording leaves it open
for sites that want to give user session options.

<AllanJ> new: If no key
attribute is specified, the user agent SHOULD assign a key
and

<AllanJ> alert the user to
the key mapping and the resultant user agent assigned

<AllanJ> key SHOULD
persist.

KF: In a public environment, you
may not want the key to persist.

JA: Sometime when we go to write
techniques, we can give examples of writing it to a cookie, or
other techniques.

KF: If you have done something
for accessibility, it should be implemented. It is open to
enough interpretation that the user agent development community
should have the flexibility they need.

JB: Wants link to mailing archive
for this discussion from the HTML group.

next week meeting

Jim is away next week. Judy recommends
skipping one week and planning a meeting for the following
week.

F2F

JA: Want to discuss now because
there deadlines coming up.

JB: Tech Plenary and TPAC in
France around October 29. Good opportunity for meeting.

JA: Another option is ATAG is
meeting in Redmond, WA in July 25, 26. Tuesday it was asked:
Could we have a UAAG meeting at same time?

KF: if we have the meeting
scheduled in France, do we need another?

JB: It can be an advantage. With
it scheduled for July, it could be good timing. We don't want
to overwhelm hosting.
... Another possibility would be another host in the same town.
Or meet somewhere else before October.

KF: Could get an official answer
by ...

JA: When KF finds out, he will
send an email.

scribing

JB: Who else is able to
scribe?

Jan, Jim, Gregory (once a month), Jeanne

Kelly is willing, but doesn't know how to do
it.

JB: There are scribing tips we
can distribute. We can set up a scribe rotation.

future directions:

JA: We need to work on these
topics (printing, keyboard access, UA and Video) and work them
out on the email list.

printing

<AllanJ> SC: 3.11.X Print
Scale: If a print from viewport feature is provided,

<AllanJ> the user has the
option of printing using the viewport's scale settings

<AllanJ> such that the user
agent should attempt to *passively reflow* the

<AllanJ> content into the
horizontal dimensions of paper. If passive reflow is

<AllanJ> not possible, more
than one sheet of paper will be required horizontally.

JA: JR proposed removing "pieces
of paper".
... we need a new definition of "passively reflowing"

KF: "print" is too restrictive,
it doesn't include embossing.

JB: propose "printing and
embossing" to keep it from getting too obscure.

JR: Does embossing horizontally
cross two pages?

GR: "Paged media" is too cryptic.
Most user agents don't print directly to an embosser, they use
another AT software to do the embossing.

JB: Does it make sense to say
"printing" and define it elsewhere? Or the first time it is
used also include embossing?

KF: When you send to an embosser,
the embosser software does the reflow. The user agent doesn't
have anything to do with it.
... Leave it as is and include a note that some printing from
user agent may include providng information to other
technologies for production in alternative media."

GR: if you print something and it
is too big for the page, it still needs to go somewhere and not
be lost.

JA: When I print from my browser,
some text is lost off the right of the page.

<AllanJ> jeanne: also an
authoring problem, if css used properly it will reflow, if not
printing breaks