Title: Re: [office-accessibility] Re: [office] Table Refresh Delay

My argument is that people will always be able to use technologies in annoying ways. We should not, as a standards body, place artificial limits on things like this. For starters, you have no idea what hardware and use cases all people have. Most other technologies allow transitions over milliseconds to add multimedia type effects to documents. A use case might be to fade a numeric value or background from one color to another over 2 seconds. It would look chunky using only 6 transitions.

Give developers and designers control please. You can suggest they do not refresh 1000 cells in a table 1000 times per second but you know someone will do it anyway.

Duane

On 18/07/08 6:26 AM, "Richard Schwerdtfeger" <sch...@us.ibm.com> wrote:

We will need user agent and author guidance. In the case where the author forgets we need a backup that is within user control.

Rich

Rich Schwerdtfeger Distinguished Engineer, SWG Accessibility Architect/Strategist Chair, IBM Accessibility Architecture Review Board blog: http://www.ibm.com/developerworks/blogs/page/schwer Malte Timmermann <Malt...@Sun.COM>

Malte Timmermann <Malt...@Sun.COM> Sent by: Malt...@Sun.COM 07/18/08 04:07 AM

To

Richard Schwerdtfeger/Austin/IBM@IBMUS

cc

Duane Nickull <offi...@lists.oasis-open.org

Subject

[office-accessibility] Re: [office] Table Refresh Delay I don't agree on "require user agents to limit this to no more than 3 times a second".

I must admit that I don't believe a higher frequency would make any sense for anything, but People have different needs, and if someone for what every reason needs a higher frequency, the application should be allowed to support this.

It's something the author should avoid.

Malte.

Richard Schwerdtfeger wrote, On 18.07.08 01:46: > 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 > Inactive hide details for "Duane Nickull" <dnic...@adobe.com>"Duane > Nickull" <dnic...@adobe.com> > > > *"Duane Nickull" <dnic...@adobe.com>* > > 07/14/08 02:23 PM > > > > To > > Richard Schwerdtfeger/Austin/IBM@IBMUS > > cc > > <offi...@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 <sch...@us.ibm.com> > To: Duane Nickull > Cc: off...@lists.oasis-open.org>; > offi...@lists.oasis-open.org > <offi...@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" <dnic...@adobe.com> > > > > > "Duane Nickull" <dnic...@adobe.com> > > 07/12/08 10:29 PM > > > > To > > Richard Schwerdtfeger/Austin/IBM@IBMUS, <off...@lists.oasis-open.org> > > > cc > > <offi...@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 <sch...@us.ibm.com> > To: off...@lists.oasis-open.org> > Cc: offi...@lists.oasis-open.org > <offi...@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 > > >

--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

-- ********************************************************************** Senior Technical Evangelist - Adobe Systems, Inc. Duane's World TV Show - http://www.duanesworldtv.org/