It should not be. A user might want to scroll the window and and scroll back to the caret position with their AT. IA2 has a scrolltopoint function.
http://accessibility.freestandards.org/a11yspecs/ia2/docs/html/interface_i_accessible2.html#e79616f64cacb298b9d24769ad54303d I can see the user wanting to get the caret at the current index, converting that to a pixel position using: http://accessibility.freestandards.org/a11yspecs/ia2/docs/html/interface_i_accessible_text.html#b02c838409659f949a3ca02620ffd77a and then scrolling to it. This is very powerful for magnification. Rich Schwerdtfeger Distinguished Engineer, SWG Accessibility Architect/Strategist Peter Korn <[email protected] OM> To Sent by: [email protected] accessibility-ia2 cc [email protected] IA2 List nuxfoundation.org <[email protected] rds.org> Subject 08/04/2009 02:36 Re: [Accessibility-ia2] Detecting PM that a character is selected Pete, gang, Is it necessary for a visible caret to be used for keyboard navigation in order to make use of the existing "caret-based" selection APIs? Regards, Peter Korn Accessibility Architect & Principal Engineer, Sun Microsystems, Inc. I propose we add a new text attribute as follows: Name: selected Values: true, false Default: false Comments: Indicates whether or not a character is selected. This would allow easier determination of whether or not a character is selected in cases where the caret isn't being used for navigation. Otherwise a virtual cursor offset (with its more global view of offsets) would have to be converted to an object offset and then IAText::selection would have to be used to determine the selection. The conversion gets complicated because lines, paragraphs, etc are typically made up of multiple objects each of which has its own text interface and its own object centric offsets. -- Pete Brunet wrote: >From Mick Curran: NVDA currently doesn't really have to detect between selected and non-selected text. If there is text selected (IAccessibleText::nSelections is greater than 0 etc) it just presents the text that is selected by using IAccessibleText::selection to find out the selected text. Some examples: *The user moves focus to an edit control that has some selected text: NVDA announces the selected text. *The user moves focus to an edit control that does not have selected text: NVDA announces the line of text where the caret is located. *The user uses the shift+arrow keys to select or deselect text: NVDA announces the newly selected or unselected text, though all still based around IAccessibleText::selection and or its previous values. However, I'm also not against a text selected attribute, as it would allow the user to see what is selected and what isn't when navigating away from the selection with the NVDA review cursor (with out moving the actual caret). So in short, we aren't struggling because there isn't a 'selected' attribute, though it may provide something useful if it did exist in the future. Mick -- Pete Brunet wrote: What means are ATs using to detect that a character is selected? I see there is no IA2 text selected attribute. Pete _______________________________________________ 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 _______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
<<inline: graycol.gif>>
<<inline: pic20415.gif>>
<<inline: ecblank.gif>>
_______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
