Re: [office-accessibility] [Fwd: Re: Accessibility concerns (ODF pt 1, publicreview 1)]

[robert_weir@us.ibm.com]

If we think there is any room for confusion, we could add a statement 
along the lines of:

"Click" and "press" refer to abstract user interface actions, regardless 
of input device or interface used to generate such actions.

On the other hand, I see that XForms, which as we know was designed not to 
require a GUI, defines their UI in similar terms.  For example, "4.4.12 
The DOMActivate Event":  "Dispatched in response to: the 'default action 
request' for a core form control, for instance pressing a button or 
hitting enter."

-Rob

Malte.Timmermann@Sun.COM wrote on 04/14/2010 10:44:44 AM:

> 
> Malte.Timmermann@Sun.COM
> 
> Hi Accessibility SC colleagues,
> 
> the last mail on our mailing list was in April - last year - so I
> thought it might be a good time for writing something here ;)
> 
> Alex Brown has some concerns wrt wording in ODF specification and
> accessibility.
> 
> I don't share his concerns, but maybe somebody here has a different
> opinion about this (see below)?
> 
> Best,
> Malte.
> 
> -------- Original Message --------
> Subject: Re: Accessibility concerns (ODF pt 1, public review 1)
> Date: Wed, 14 Apr 2010 16:38:24 +0200
> From: Malte Timmermann <Malte.Timmermann@sun.com>
> To: Alex Brown <alexb@griffinbrown.co.uk>,
> office-comment@lists.oasis-open.org
> 
> Hi Alex,
> 
> I don't see an issue here:
> 
> Except via API access, there are two ways for the user to perform
> actions: via Mouse, or via Keyboard.
> 
> If the user uses some special tools like AT, it results in something
> like keyboard/mouse for the application:
> 
> When operating an onscreen keyboard via mouse, buttons or what ever, for
> the application it's key input (only GOK might result in actions via 
API).
> 
> When using some eye tracking or other mouse replacements, for the
> application it's mouse input.
> 
> But that's just my point of view.
> I will bring this to the accessibility SC, and check if other people
> think differently about this.
> 
> Best,
> Malte.
> 
> Alex Brown wrote:
> > Dear all,
> > 
> > A lot of language in this specification mandates/assumes the use 
> of a screen/keyboard/mouse based computing environment.
> > 
> > For example:
> > 
> > ----
> > 19.267 form:default-button
> > 
> > The form:default-button attribute specifies whether a button is 
> the default button on a form. If a user clicks the default button or
> presses Return while an input control is focused, the implementation
> takes the same action.
> > ----
> > 
> > or
> > 
> > ----
> > 19.276 form:focus-on-click
> > 
> > The form:focus-on-click attribute specifies if a <form:button> 
> element is given the focus in a form when the form button control 
> for that element is clicked with a mouse.
> > ----
> > 
> > A thorough pass should be made of the text, generalising such 
> language to ensure ODF does not privilege certain non-accessible 
> computer environments.
> > 
> > - Alex.
> 
> 
> 
> -- 
> Malte Timmermann <Malte.Timmermann@sun.com>       Sun Microsystems GmbH
> Technical Architect Software Engineering                   Nagelsweg 55
> http://blogs.sun.com/malte                       20097 Hamburg, Germany
> -----------------------------------------------------------------------
> Sitz der Gesellschaft:
> Sun Microsystems GmbH, Sonnenallee 1, 85551 Kirchheim-Heimstetten
> Amtsgericht Muenchen: HRB 161028
> Geschaeftsfuehrer: Juergen Kunz
> 
> 
> ---------------------------------------------------------------------
> 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 
>