Meeting Record

wiki
transition call for XHTML1; don't anticipate problems, but for those of you interested in basic, look at draft of spec for obvious editorial errors; shane & i looked it over yesterday
role and access
accessmodule and targetid
longdesc

14:10:27 <OedipusWrecked> SP: have an action item to ask for a wiki; told that w3c is going to transfer / migrate to mediawiki, which is probably preferable; put action item on hold until migration complete

14:11:30 <OedipusWrecked> topic: transition call for XHTML1; don't anticipate problems, but for those of you interested in basic, look at draft of spec for obvious editorial errors; shane & i looked it over yesterday

14:19:07 <OedipusWrecked> SP: traditional call tomorrow at regular time - link in the agenda, please pass an editorial eye over it; had a comment from within w3c team to exit CR need tests that test optional features -- in particular input mode -- 2 implementations that do input mode

14:24:12 <OedipusWrecked> SP: replied to schema group - posted proposed reply; if anyone knows modularization PLEASE take a look at my comments and make sure that you agree -- looking for help, especially shane and mark and anyone else who knows schemas and modularization

14:28:04 <OedipusWrecked> SP: we have a face2face where can deal with last call issues at face2face; if we suggest a last call that ends on the last day of august, gives SP time to chase down people and collect all comments?

14:33:00 <OedipusWrecked> SP: are we happy with "next id in target area"? more sensible to say, yes, next one of those in order; take list in attribute order, of take list and find first one in document order; need to agree which is best

14:38:23 <OedipusWrecked> ??: understand your arguments, but if have doc with roles a b & c - TargetRole a b c - when activate access key, where does it go -- to all the As and then the Bs or movev onto the Bs

14:39:52 <OedipusWrecked> ??: just wanted consistency -- people have discussed mapping in different fora - can always come back to it; like a flag that says these items qualify for focus, then provide option to go down list of As or tab to next set of Bs

14:41:42 <OedipusWrecked> ??: good example - if have table, can go to any row or column, set an accesskey for SeekTheCell -- knock off the head, just have the cell, should still do in row order or column order

14:46:42 <OedipusWrecked> SP: where the definition should go - module is independent of NextFocus; could have lang with accesskey but not next focus; put in access module what happens when have NextFocus like mechanism, or put into NextFocus module, say this redefines concept of document order; should we use the term "navigation order"? -- perhaps that is the answer

14:47:45 <OedipusWrecked> Rich: should be "navigation order"; have a flowto mechanism in ARIA - if there is one id, go to next id, can skip the order -- this is Assisstive Tech, not UAs; if multiple IDs, user should be given a choice of which to navigate to

14:52:52 <OedipusWrecked> SP: may have seen email to MB; question about multiple ids on single element; XML Schema group has decided to allow multiple IDs on an element; don't know when that behavior will be defined, so can do what we need without breaking rules

14:53:40 <OedipusWrecked> SP: no reason for single ID restriction; nothing really breaks if something has 2 names; sent comment to XML WG answered, yes, this is a bug, needs to be fixed; resolved to change it, so heads up

14:55:59 <OedipusWrecked> SP: discussed endlessly and came up with solution; HTML5 case - allow image to have content - not to be empty element, but element with children; if source fails, image not available, image loading off, can use content of the image element

14:57:19 <OedipusWrecked> Rich: image shows can't navigate content, so where going to get description? ATs can get text for you; description relative to an item on same page -- describedby; objection to longdesc is someone has to create whole new web page and maintain it

15:03:58 <markbirbeck> Steven--if we were to give special status to text used in fallbacks then we could cover all use-cases. We could simply say in XHTML 2 that the UA should make fallback text 'available' regardless of which of the items is actually used. Then it really does become like @longdesc, and it also means that Rich doesn't need to have a separate area for his descriptive text.

Weekly XHTML2 WG Teleconference

Minutes of 11 July 2007

1. wiki

2. transition call for XHTML1; don't anticipate problems, but for those of you interested in basic, look at draft of spec for obvious editorial errors; shane & i looked it over yesterday

3. role and access

4. accessmodule and targetid

5. longdesc