Re: [office] Table Refresh Delay

[Richard Schwerdtfeger <schwer@us.ibm.com>]

That is fine. This will just mean we will require user agents and authors to limit this to no more than 3 times a second which may cause epileptic seizures. If we did not have adequate justification for having this level of granularity we could avoid imposing this other requirement. ok?

Rich



Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist
Chair, IBM Accessibility Architecture Review Board
blog: http://www.ibm.com/developerworks/blogs/page/schwer
"Duane Nickull" <dnickull@adobe.com>

"Duane Nickull" <dnickull@adobe.com>

07/14/08 02:23 PM

To	Richard Schwerdtfeger/Austin/IBM@IBMUS
cc	<office@lists.oasis-open.org>, <office-accessibility@lists.oasis-open.org>
Subject	Re: [office] Table Refresh Delay

Whether or not it is done 1000 times per second is not the issue. Giving developers and document writers the ability to control it via mlsecs would be nice to have for interactive documents.  Transitions of content to highlight or change things (think MS PPT) should probably use a consistent model across all odf content.  Make some sense?
Aus mein Blackberry/from my Blackberry

----- Original Message -----
From: Richard Schwerdtfeger <schwer@us.ibm.com>
To: Duane Nickull
Cc: office@lists.oasis-open.org <office@lists.oasis-open.org>; office-accessibility@lists.oasis-open.org <office-accessibility@lists.oasis-open.org>
Sent: Mon Jul 14 11:32:05 2008
Subject: Re: [office] Table Refresh Delay

Is milliseconds practical? Would a table really update every x milliseconds? I can't imagine network performance making this practical.

The problem area is >= 3 times per second. This will cause seizures. If the update rate were seconds this is not a problem.

If it were this fast I would do a two pronged approach:


* Tell authors to not set this to more than 3 times per second.
* I would require that office agents provide a UI feature that allows the user to limit the refresh rate.



Rich




Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist
Chair, IBM Accessibility Architecture Review Board
blog: http://www.ibm.com/developerworks/blogs/page/schwer
"Duane Nickull" <dnickull@adobe.com>




"Duane Nickull" <dnickull@adobe.com>

07/12/08 10:29 PM



To

Richard Schwerdtfeger/Austin/IBM@IBMUS, <office@lists.oasis-open.org>


cc

<office-accessibility@lists.oasis-open.org>


Subject

Re: [office] Table Refresh Delay


I would highly recommend miliseconds but provide best practives to introdue warnings when use would result in seni-optimal UE's.

Sound logical?

D
Aus mein Blackberry/from my Blackberry

----- Original Message -----
From: Richard Schwerdtfeger <schwer@us.ibm.com>
To: office@lists.oasis-open.org <office@lists.oasis-open.org>
Cc: office-accessibility@lists.oasis-open.org <office-accessibility@lists.oasis-open.org>
Sent: Sat Jul 12 08:52:20 2008
Subject: [office] Table Refresh Delay

Can someone from the TC please tell me the units for: <table:refresh-delay> ?

Is this in seconds? This is very important for accessibility as if it is less than a second then there is a potential to cause seizures.

Whatever the answer, would someone please update the specification to reflect the actual units?

Thank you,
Rich



Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist
Chair, IBM Accessibility Architecture Review Board
blog: http://www.ibm.com/developerworks/blogs/page/schwer