From: Brendan McKeon
To: Kiran Raj (Exchange); Rob Sinclair
Cc: Mark Carroll (Exchange); Carla Sornson
Subject: RE: RCML Requirements for MSAA

Two main categories of Accessibility-related wishlist items:

(1) General accessibility features

Note that CarlaSo is our contact for this [non-MSAA specific] area.

- Respecting high contrast, keyboard, font preference flags
- (eg. using the system colors instead of the specified styles if the high contrast flag is set.)
- Other cool things (eg. auto generating hotkeys on the fly where not already present)

(2) MSAA-related features

Basic idea is that we want the ability to attach arbitrary property-name=property-value pairs to controls. Some of the values may be localizable, others not. Some will be strings, others may be references to other control IDs.

ACC_NAME = "Name:" // ACC_LABELEDBY = "3" // the label for this control is the one with an ID of 3.

Some of these properties will correspond to fields in the existing IAccessible interface: Name, Value, Description, Help, HelpTopic, KeyboardShortcut

Some of these properties will have no corresponding IAccessible equivalent (but may be used behind the scenes to generate one of those properties - for example, LABELEDBY could indicate a control whose text would make a suitable name for this control.)

This list of properties will be open-ended - we'll define an initial set to cover most requirements, but more may be added later on as needed. (What's the best way of getting this type of open-ended flexibility out of RCML?)

Typically you would not need to specify many of these - eg. Name, value, state etc. would usually come from the control itself anyway - but having this facility to attach these to specify or override accessibility-related properties as needed