Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NVDAObjects should have a way to convey extended/custom states to the user. #236

Closed
nvaccessAuto opened this issue Jan 1, 2010 · 3 comments
Labels

Comments

@nvaccessAuto
Copy link

Reported by mdcurran on 2008-11-24 11:56
APIs such as IAccessible2 and UI Automation may have custom states on their objects. Examples of this could be a contact in an instant messaging program, with a custom state of ''away' or 'online' etc.
NVDAObjects should contain a customStates property which is a list of strings which are the current custom states.

  • IAccessible2: use localizedExtendedStates, or extendedStates.
  • UIAutomation: use itemState
@nvaccessAuto
Copy link
Author

Comment 1 by mdcurran on 2008-11-25 02:18
customStates should be a dictionary, where the keys are the non-localized custom states, and the values are localized states. I.E. for programmatic use you use the keys, for speech and braille you use the values.

@LeonarddeR
Copy link
Collaborator

This is similar to #235 and might be useful at some point

@Adriani90
Copy link
Collaborator

I am closing this in favor of #235 since the discussion goes further there and touches this aspect as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants