[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Fw: Dynamic Contents in ODF 1.2 Accessibility Guideline
All,
I will forward Tatsuya's mail for our following action item.
ACTION: Tatsui/Hiro work on improving text of this section to
indicate to the office application as to how to notify the AT when
changes occur. Also, since DDE exchanges happen at load time do we
need to worry about updates. Finally, do we need to mark live areas
as they are occuring in the background and not in response to user
actions.
Regards,
Hiro
---------------------
Hironobu Takagi, PhD.
Accessibility Research
Tokyo Research Laboratory, IBM Research
+81-46-215-4557
E-mail: takagih@jp.ibm.com
----- Forwarded by Hironobu Takagi/Japan/IBM on 2008/06/30 21:35 -----
To:
Hironobu Takagi/Japan/IBM@IBMJP
cc:
Subject:
Dynamic Contents in ODF 1.2 Accessibility Guideline
From:
Tatsuya Ishihara/Japan/IBM - Monday, June 30, 2008,
20:46
Hi Takagi-san,
Could you forward this mail to ODF subcommittee mailing list?
This is updated dynamic content section of ODF 1.2 accessibility guideline.
I added the description about accessibility API for each type of dynamic
change.
ODF spec says DDE connection can be updated automatically or on the user's
request, so I left the item of DDE connections for now.
(See. ODF spec 1.2, 13.6. DDE Connections
A Dynamic Data Exchange (DDE) connection consists of the parameters for the
DDE target application, a file name, and a command string. A DDE connection
also takes a parameter that specifies whether it will be updated
automatically or only on the user's request. Every DDE connection must be
named.)
3.4.3 Special considerations for dynamic ODF content
Some types of assistive technologies, such as screen readers, usually
present only the focused part of a document. That is why updates to other
parts of the document will not be presented to users with assistive
technologies. Therefore, if the content is automatically updated in any
way, automatic updates should be carefully presented to assistive
technologies through accessibility APIs.
Each accessibility API defines "event" mechanism to notify changes to
assistive technologies. It is recommended to appropriately implement those
events in each office editor and viewer. The following ODF features create
dynamic ODF content changes.
(1) scripting
6.7.6 <text:script>
This tag can cause any types of changes.
When the script function updates ODF content, user agent should fire
these events.
When text is removed, fire IA2_EVENT_TEXT_REMOVED(IA2) and
EVENT_OBJECT_VALUECHANGED(MSAA).
When text is inserted, fire IA2_EVENT_TEXT_INSERTED(IA2) and
EVENT_OBJECT_VALUECHANGED(MSAA).
When text is changed, fire IA2_EVENT_TEXT_UPDATED(IA2) and
EVENT_OBJECT_VALUECHANGED(MSAA).).
When the non-text ODF content is removed, fire
IA2_EVENT_DOCUMENT_CONTENT_CHANGED(IA2) and EVENT_OBJECT_DESTROY(MSAA).
When the non-text ODF content is inserted fire
IA2_EVENT_DOCUMENT_CONTENT_CHANGED(IA2) EVENT_OBJECT_SHOW(MSAA).
(2) dynamic content
Dynamic content is defined by these elements.
4.5 <text:section>
6.6 Database Fields
8.4.2 <table:table-source>
8.5.1 <table:cell-range-source>
Dynamic content refers to external data sources that are defined by these
elements.
6.7.9 <text:dde-connection>
8.11 <table:dde-links> (spreadsheet)
11 Database Front-end Document Content
13.6 DDE Connections
When the external date source is updated, the dynamic content referring to
this data is updated automatically. In this case, user agent should fire
IA2_EVENT_TEXT_UPDATED(IA2) and EVENT_OBJECT_VALUECHANGED(MSAA).
Best regards.
Tatsuya
---
Tatsuya Ishihara
IBM Tokyo Research Laboratory (Mail Code: LAB-S77)
E-mail : tisihara@jp.ibm.com
Tel: +81-46(215)4978 Fax: +81-46(274)4282
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]