I have incorporated your changes as suggested. https://www.linuxfoundation.org/collaborate/workgroups/accessibility/ia2/ia2_implementation_guide
1. Updated wording to fix "prior": [R2] Tab and shift+tab in a table: Move to next or prior cell (required). [/R2] 2. Updated wording to add names of interfaces: For "text-model:a1;" the IAccessibleText should contain the embed characters for each embedded control, and the IAccessibleHypertext and IAccessibleHyperlink interfaces for finding these controls should work. 3. Corrected initial reference to "Iatext-model:A1". Now says: The attribute has the following form: [R2] text-model:a1; Providing the text-model [/R2] attribute as shown above... Regards, Brian Brian Cragun IBM AbilityLab Consultant Human Ability & Accessibility Center www.ibm.com/able & w3.ibm.com/able W:(720)-663-2801 H:(507)288-2437 From: "Brett Lewis" <[email protected]> To: <[email protected]>, "IA2 List" <[email protected]> Date: 07/13/2011 09:38 AM Subject: Re: [Accessibility-ia2] IA2 text attributes - finalize? Sent by: [email protected] Hi, I like and agree with Pete's comments. I don't know if the "1" in "a1" is a version indicator. My guess is that it was intended to be but I have always just thought of the whole string "a1" together rather than as separate parts. Brett From: [email protected] [ mailto:[email protected]] On Behalf Of Pete Brunet Sent: Wednesday, July 13, 2011 7:11 AM To: IA2 List Subject: Re: [Accessibility-ia2] IA2 text attributes - finalize? Thanks Brian, Some comments/questions: >Tab and shift+tab in a table: Move to next or prior cell (prior) Did you mean to have "(prior)" at the end? >the IAccessibleText should contain the embed characters for each embedded control, and the hyperlink method for finding these controls should work. Consider replacing "the hyperlink method" with "the IAccessibleHypertext and IAccessibleHyperlink interfaces" For the object attributes spec how is this... Name: text-model Values: a1 Default: a1 Comments: Indicates a text object with a hierarchical structure. Some examples are rich text, possibly including controls, and tables with editable content. Spec: http://www.linuxfoundation.org/collaborate/workgroups/accessibility/ia2/ia2_implementation_guide Is the 1 in "a1" a version indicator? Pete -- Pete Brunet a11ysoft - Accessibility Architecture and Development (512) 467-4706 (work), (512) 689-4155 (cell) Skype: pete.brunet IM: ptbrunet (AOL, Google), [email protected] (MSN) http://www.a11ysoft.com/about/ Ionosphere: WS4G On 7/12/2011 6:07 PM, Brian Cragun wrote: I have made proposed updates in the IA2 Implementation Guide ( https://www.linuxfoundation.org/collaborate/workgroups/accessibility/ia2/ia2_implementation_guide ) related to this thread and other additions recommended by Brett Lewis and Pete Brunet. These are indicated in the online document surrounded by the markup [R2] [/R2]. Brett and Pete, to clarify the issue of using the embed characters in relation to "text-model:a1;", you will find a paragraph I added which says this: Embeds should be used as described whenever the object attribute "text-model:a1;" is used. For "text-model:a1;" the IAccessibleText should contain the embed characters for each embedded control, and the hyperlink method for finding these controls should work. This would apply to all applications including browsers, and controls with complex content such as multiline text boxes or tables. The actual controls may be an IAccessible and be a child of the document. Please review and let me know if they are correct. Regards, Brian Brian Cragun IBM AbilityLab Consultant Human Ability & Accessibility Center www.ibm.com/able & w3.ibm.com/able W:(720)-663-2801 H:(507)288-2437 From: Pete Brunet <[email protected]> To: Cc: IA2 List <[email protected]> Date: 06/24/2011 04:34 PM Subject: Re: [Accessibility-ia2] IA2 text attributes - finalize? Sent by: [email protected] Thanks Car, Could you send me text describing text-model:a1? What behavior should be expected when it's provided, and when it's not provided? I'll put that text into the object attributes spec. -Pete On 6/24/2011 10:54 AM, Carolyn MacLeod wrote: > 2a) Note that the important object attribute "text-model:a1;" is not described at all. This really needs to be in the object attributes list before that is finalized. > I can add it. Is it as you have indicated or Iatext-model:A1 as documented in Brian's document at > http://www.linuxfoundation.org/collaborate/workgroups/accessibility/ia2/ia2_implementation_guide "text-model:a1;" is the exact spelling currently used in JAWS and Eclipse. It was changed to that at your request, "for consistency with other attributes". If you need the background email discussion, I can forward. Brian, can you make this change to the "IAccessible2 Implementation Guide" document, please? The other related change that was needed (for StyledText to be perfectly "a1") is to add the word "(optional)" to the end of this point in the list of expected a1 keystrokes: Ctrl + up and down arrows: Move between paragraphs StyledText cannot support paragraph navigation in Eclipse because it is typically used for a code editor, and code does not have paragraphs... so this keystroke pair needs to be optional. It was decided that that was better than defining a whole new "a2" model just for one pair of keystrokes. Thanks! Car _______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2 _______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
_______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
