[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: minutes, partial. First draft. 061026
Attached, html format. My rough notes for updated section 3 of guidelines is below. Hiro ----------- 3.1. Could you describe that the "title" means a visible title text marked as a heading <text:h>? phrasing, needs description. Clarify with Hiro. 3.1.1 The meaning of "style" sounds ambiguous. When I read this section first time, I confused with "styles" and "structure". I thought styles are just visual appearance and not contribute to structurize content. But, in this section styles are recommended to structurize content. Diff styles from font attributes. (xml styles which produce visual changes. ) There are three types of sources for Table of Contents. (Section 7.3 in ODF1.1). - Headers (as defined by the outline structure of the document), up to a selectable level - Table of content index marks - Paragraphs formatted with a set of selectable paragraph styles I feel current description mainly mention third one. So, I recommend adding description about headers and index marks. Especially, headers (<text:h>) is important. +1 Add all 3. 3.1.2. Navigation order in presentations document can be controlled in presentation documents. This is strong point of ODF. So could you add description about draw:nav-order? author should be able to choose logical nav order, the app must provide ui for doing that, and then ODF app must provide a means for navigating beween them. e.g. keyboard convention of tabbing between them. (ODF1.1. 9.1.4)"The draw:nav-order attribute defines a logical navigation sequence for the graphical elements included in the page. ... This attribute should reflect the intentional ordering of graphics as set by the document author." 3.2. Addtional description about <svg:title>, <svg:descripion>, <draw:caption>, and draw:caption-id will help audience to understand this section deeply. title - the brief desciption of the graphical object. desc - a longer more detailed description typically used for help caption - used for a grpahical object 'title' (see odf spec). Normally visible and closly associated via the caption -id. caption-id is the id of the caption. (tbc). ============================= 3.1.3.1 - Should say something about list structure whereas indentation should be clearly represented in the document content and not through the use of presentation styling. An indented child should be in the subtree of the of the parent bullet when parsed. See section 4.2.2. Can indent (instead of sub list). Looks like a sublist but isn't structurally. (see 4.2.2 of guidelines). - Should say something about page breaks Use visual pages to keep pace with sighted users. - Table headings, <table:table-header-rows>, once created should be repeated on each page and be conveyed in the document structure. 1.0 to 1.1. When create a table header, decide if repeated on each page. Edinburgh decided ??? Authors should indicate table header information by structure (not appearance). To ensure that table headers are available across page boundaries no matter what API is used? Rationale is to present this information to a user n pages after the table start. 3.1.3 - Should make a comment about the fact that ODF 1.1 does not support tables in presentations. If the off applicaton wishes to create a table it should may treated as an embedded ODF spreadsheet and saved as such. E.g. use an embedded spreadsheet rather than a visual table presentation in presentations. Guideline is to ensure that presentation tables have an table structure when saved to disk. Saving as an embedded spreadsheet structure meets this need. [import power point issues. ] 3.2 Alternative Text We need to talk about alternative text for image map elements. This must be stored in <svg:title>. svg:title will be used as the hyperlink text. <svg:description> is only used if you want to add lengthy additional help text to describe what the link will do. Use svg:title for link description, for the active areas of an imagemap. Description as a fallback. Alternative text (short and long) may be entered through the use of a dialog. General: Please look at section 4 and see if there are additional discussion points you can bring in to augment section 3. Captions, etc. Add the more general ones. ==================== -- Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.ukTitle: OASIS ODF Accessibility SC Meeting
OASIS ODF Accessibility SC MeetingAttendees
Apologies
AgendaItem. Roll Call Item. Review & approve previous minutes Item. Amendments wanted for section 3. 1 Roll call, Minutes 5 October. approval.DISCUSSION: See attendance list. Approved. RS. 2 Section 3 changes.DISCUSSION: RS. DP.
3 AOBDISCUSSION: PK. Posted document (todays date) Action item: Review new content. PK added 2.3 section. Who? AllDue date: ASAP. Action item: Give the current document to Jon Gunderson and Mac (tech editor) Who? PKDue date: by end of play tomorrow 4 Daisy converter.DISCUSSION: DP will update next week. The Oasis irc server is irc.oasis-open.org, channel &office-accessibility Summary of Actions
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Date: 2006-10-19T15:56:50.0Z
Time: 1600Z
Venue: Telcon
Date: 2006-10-19T15:56:56.0Z
Version: 1