• 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: AXRoleDiscription and AXTitle
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AXRoleDiscription and AXTitle


  • Subject: Re: AXRoleDiscription and AXTitle
  • From: Mike Engber <email@hidden>
  • Date: Fri, 23 Apr 2004 15:08:01 -0700

I mostly know about accessorizing Cocoa apps, but your q's are pretty general.

On Apr 23, 2004, at 1:58 PM, David Weiss wrote:
If I send the AXRoleDiscription to be simply the tool tip I have already for my app (Carbon) is that too short?
How descriptive should these descriptions be?

The role descriptions are fixed, based on the role. Unless you're inventing roles, there should be no need to be inventing role descriptions. If you're widgets inherit from standard ones, then you should be inheriting the role and role descriptions anyway - no need to do any work.

But, to answer your q - role descriptions are a human readable (localized) description of the kind of widget whereas the tool tip is instance specific. E.g. "button" vs "print button". By default, we use the tooltip as the AXHelp attribute (in Cocoa).

What are the consequences for leaving the description blank? Does a screen reader combine the AXRole and AXRoleDiscription and AXTitle to describe an element?

That depends on the assistive app. In general, combining strings isn't a very localizable thing to do and should be avoided, but folks may do it anyway.

If I have a UI element that is has no visible title (just a graphic, or a scroll button for example) Can I leave these blank, or do I need to add a title to these objects? Does the title for these objects need to be localized?

Titles are for text that is actually visible. So a graphic button wouldn't have a title, but it would have an AXDescription. AXDescription is actually a new attribute we're moving towards - so you may see some AXTitles around that will become AXDescriptions.

From how I see things the AXTitle and AXRoleDiscription will end up being equal in many many cases, is that generally true?

It will almost never be true. E.g. "Print" vs "button"

-ME
_______________________________________________
accessibility-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/accessibility-dev
Do not post admin requests to the list. They will be ignored.


References: 
 >AXRoleDiscription and AXTitle (From: David Weiss <email@hidden>)

  • Prev by Date: Re: AXMenu stuff
  • Next by Date: Re: AXRoleDiscription and AXTitle
  • Previous by thread: AXRoleDiscription and AXTitle
  • Next by thread: Re: AXRoleDiscription and AXTitle
  • Index(es):
    • Date
    • Thread