UPDATE with new phone numbers - OASIS ODF a11y SC meeting Thursday,2Aug07 8am PT / 11am ET / 3pm GMT / 5pm CET / 12 midnight Japan

[Peter Korn <Peter.Korn@Sun.COM>]

Hello everyone,

In order to allow global participation in these phone calls without 
requiring long-distance/toll calls (especially for individual members 
who don't reside in the U.S. or Canada), we're going to try a new set of 
phone numbers.  These are the same numbers that the Open A11y 
teleconference meetings use (chaired by our own Janina Sajka).

So, for tomorrow, please use one of the following numbers to dial in:

Vo/IP Using SIP or IAX: telecon@a11y.org

USA 877-421-0030; 770-615-1247
Austria +43 179576264
Belgium 0800-7-3026; +32 22006114
Denmark 80-888377; +45 38323070
Finland 0800-914-630; +358 972519061
France 0800-902366; +33 157323040; +33 157323041
Germany 0800-181-6323; +49 6951709081
Ireland 1800-558728; +353 16569209
Italy 800-788634; +39 0269430413
Netherlands 0800-022-8558; +31 202008077
Norway 800-18373; +47 24159528
Spain 900-95-1089; +34 912754171
Sweden 020-799414; +46 850163259
Switzerland 0800-564-331; +41 446545620
United Kingdom 0808-234-1969; +44 2070260533


I will separately send each ODF Accessibility SC member the passcode to 
enter once you have made the phone connection.  We have been asked to 
NOT share the passcode or transmit it any form that is archived on the 
Internet.  If you did not receive it, please contact me (or Janina, who 
also knows the passcode).  Please look for a message in your inbox 
titled "PASSCODE for OASIS ODF a11y SC meeting"

I believe, in addition to thanking Janina, we also owe thanks to IBM who 
is ultimately providing this calling system.


Regards,

Peter Korn
Accessibility Architect,
Sun Microsystems, Inc.

> Greetings,
>
> It has been a few weeks since we last met.  Florian Reuter of the main 
> ODF TC asked us a question (attached), and also shared with us some 
> thoughts about subtables (see attached e-mails).  I'd like to use our 
> meeting time to discuss the question & topic he raised.
>
> I had hoped to have toll-free numbers to use in each of the countries 
> we live in by now, but I not (yet) have them.  If I manage to assemble 
> a set prior to Thursday, I'll send out details of them to supersede 
> the U.S. based numbers below.
>
> Connection info:
>
> Thursday, 2Aug07 8am PT / 11am ET /  3pm GMT / 5pm CET / 12 midnight 
> Japan
> 1-866-839-8145 (US toll free)
> 1-865-524-6352 (Intl)
> code: 6560654#
>
> IRC: http://irc.oasis-open.org
> channel: "&office-accessibility"
>
> Suggested agenda:
>
> 1) Approve minutes for last ODF Accessibility SC Meeting - assuming I 
> manage to find them (Mike - did you take these?)
>
> 2) Last call for comments on Subcommittee Draft #2 of the 
> Accessibility Guidelines document (see 
> http://www.oasis-open.org/committees/download.php/24778/ODF_Accessibility_Guidelines_scd2_25July2007.odt) 
> and use display of change notification to see what changes I made.
>
> 3) Discussion of issues Florian has raised
>
> ------------------------------------------------------------------------
>
> Subject:
> [office-accessibility] question regarding style:next-style-name
> From:
> Florian Reuter <freuter@novell.com>
> Date:
> Mon, 23 Jul 2007 18:10:23 +0100
> To:
> office-accessibility@lists.oasis-open.org
>
> To:
> office-accessibility@lists.oasis-open.org
>
>
> Dear SC,
>
> I was just wondering whether the "style:next-style-name" attribute of a "style:master-page" migth also be an accessibility issue.
> The general idea of this concept is that a master page style also defines the next master page style used during the layout process.
>
> So you can a build chain of page styles like:
> PageStyle0 -> PageStyle1 -> PageStyle2 -> PageStyle1 -> PageStyle2 -> PageStyle1 -> ...
> by using the following declarations:
> PageStyle0.next-style-name = PageStyle1
> PageStyle1.next-style-name = PageStyle2
> PageStyle2.next-style-name = PageStyle1
> or even more complex.
>
> So whenever an implicit or explicit page break appears the next page style in the chain is chosed. This means that the page style (including headers, footers, etc.) are changed by an implcicit or explicit page break as a side-effect.  I'm wondering whether this "side-effect" of a page break might be an issue wrt. accessibility?
>
> FYI Word does not use the concept of next-page-style and side-effects. Instead Word has three page styles per section: FirstPage, LeftPage and RightPage. So its very clear what the purpose of the page style is.
>
> Best regards,
>
> ~Florian
>
>   
>
> ------------------------------------------------------------------------
>
> Subject:
> [office-accessibility] subtables and sudoku
> From:
> Florian Reuter <freuter@novell.com>
> Date:
> Mon, 23 Jul 2007 18:13:04 +0100
> To:
> office-accessibility@lists.oasis-open.org
>
> To:
> office-accessibility@lists.oasis-open.org
>
>
> Dear SC,
>
> I've seen arguments that Sudoku is a good use-case for the special "isSubTable" attribute. I don't think Sudoku is a good example. Let me explain why:
>
> Consider for example you have a complete Sudoku board where the initial numbers are printed in bold. When using subtables the lines of the Sudoku board not will be aligned since bold letters have a different height than normal letters (This gets even worse when using different fonts or different font heights). The only way you can achieve this alignment is using colSpans and rowSpans.
>
> Additionally interop with HTML ans WW is not possible.
>
> Just my two cents. Best regards,
>
> ~Florian 
>