• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: MacOS Accessibility Questions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MacOS Accessibility Questions


  • Subject: Re: MacOS Accessibility Questions
  • From: Mark Thomas <email@hidden>
  • Date: Mon, 30 Jan 2006 18:38:52 +0000
  • Organization: Coderus Ltd

Thanks for the clarity here with the Item Chooser, as I was trying to work
out why I see scrollarea or group text in the "Item Chooser" for no reason
and sometimes I see multiple of them and no highlight shown makes no sense
(and sometimes there is nothing there which looks like should be a
hierarchal).

So this is why I was wondering if it was trying to show a hierarchal of some
fashion ?

Any ideas why I should see multiples ?

Thanks
Mark.

>
> On Jan 27, 2006, at 9:42 AM, Mark Thomas wrote:
>
>> Hi,
>>   Thanks for the answer, this makes a little more sense so
>> continuing this
>> so how should it work if you have items which are embedded in other
>> controls
>> e.g. Large amount of text in a list box, or say options which are
>> grouped
>> within a group box.
>
> The Item Chooser Menu builds a list of all elements, even nested
> elements.  So each individual AXUIElement would be represented by a
> line in the menu.  Large blobs of text in an element, such as an
> AXTextArea, would still be represented as one menu item (you would
> get a one line entry that is basically a truncated version of the
> large blob of text).  But AXLists and AXTables can have many
> children, and the Item Chooser should show each child element.
>
> Was this question still about the item chooser, or general navigation
> with VO?
>
> --E.
>
>
>>
>> Thanks
>> Mark.
>>
>>> The item chooser menu provides a user with a list of all (accessible)
>>> elements in a window.  It is intended to be a supplemental screen
>>> navigation technique.  Sighted folks generally navigate a user
>>> interface by glancing around the screen, quickly identifying an
>>> element of interest, and then moving the mouse to it or tabbing until
>>> the focus loop moves to it.  This technique is generally very
>>> efficient.
>>>
>>> Most VoiceOver users do not use vision to navigate.  Instead they
>>> move from item to item using the VoiceOver cursor, and listen to a
>>> description of each item.  Since moving from item to item can be more
>>> tedious, we introduced the Item Chooser Menu as an alternative.  The
>>> user can press control-option-i to open the Item Chooser Menu.  They
>>> can then arrow through each element, or more typically, they can type
>>> a few characters to narrow the list.  Once the list is narrowed, they
>>> can arrow over one or two items that are similarly spelled to find
>>> what they are looking for.  With practice, a user can significantly
>>> reduce the number of keystrokes necessary to move around.
>>>
>>> To navigate elements based on their screen location, simply use
>>> control+option+arrows.
>>>
>>> --E.
>>>
>>
>>  _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Accessibility-dev mailing list      (Accessibility-
>> email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>> 40apple.com
>>
>> This email sent to email@hidden
>
>
>

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Re: MacOS Accessibility Questions (From: "Eric T. Seymour" <email@hidden>)

  • Prev by Date: Re: MacOS Accessibility Questions
  • Next by Date: Lack of AX support in Pages 2 and Keynote 3
  • Previous by thread: Re: MacOS Accessibility Questions
  • Next by thread: Lack of AX support in Pages 2 and Keynote 3
  • Index(es):
    • Date
    • Thread