This specification, in conjunction with the Events Module, is intended address the problem of device-, OS-, and localization-independent control of web content. See the introduction for background and usage examples.

Interface UserPreferences

The preferences attribute of the Window interface MUST return an instance of the UserPreferences interface. The same object must be returned each time.

DOMstring? valueForKey()

Description TBD (esp re: privacy and fingerprinting, and prompt access for certain parameters on a per-domain basis, similar to location sharing)

Need an additional "silent fail" parameter when keys are nice-to-have but not important enough to prompt if the user or platform specifies "prompt for access" to a particular key.

An undefined or empty value for the taxonomy parameter indicates the key matches a preference defined in Preference Keys section of this document. Standard vendor prefixes (ie, moz, o, webkit) are reserved for the taxonomy parameter, and any additional implementation or external taxonomy identifiers will be defined in a supplemental, informative document.

						// example of a preference defined within the IndieUI User Context specification.
						window.preferences.valueForKey('fontSize');
						
						// example of an vendor-proposed preference, intended for standardization.
						window.preferences.valueForKey('foo', 'moz');
						
						// example of an implementation-specific preference that does not apply to other user agents.
						window.preferences.valueForKey('focusAllControls', 'webkit');
					

DOMString key

Identifying key for the preference value to be returned.

optional DOMString? taxonony

A unique string identifier for external taxonomy in which the key is defined, such as a vendor-prefix ('webkit') for vendor-proposed or implementation-specific keys, or another external taxonomy.

Assistive Technology Identification and Notification

Most of this section is out-of-date. Please don't put too much effort into change requests yet.

In certain cases, it is beneficial for web authors to be aware of the assistive technology in use. This section defines a collection of attributes that can be used to determine, from script, the kind of assistive technology in use, in order to be aware of considerations for a particular assistive technology, including the need to support the UI Change Request Events or Accessibility Events defined in previous sections. Web authors should always limit client detection to detecting known versions. Web authors should always assume future versions and unknown versions to be fully compliant.

The accessibility attribute of the Navigator interface must return an instance of the Accessibility interface, which represents the identity and state of the assistive technology, and allows web pages to optionally notify assistive technology of certain interface events that cannot be indicated through declarative markup such as WAI-ARIA roles, states, and properties.

interface Accessibility {
  readonly attribute InterfaceObject accessibility; // Editorial Note: Is it necessary to define this attribute in the IDL?
  // objects implementing the Accessibility interface also implement the ScreenReader and AccessibilityNotifications interfaces
};
Accessibility implements AccessibilityNotifications;
Accessibility implements ScreenReader;
Accessibility implements Magnifier;
Accessibility implements Speech;

[Supplemental, NoInterfaceObject]
interface AccessibilityNotifications {
	
	const unsigned short    screenChanged   = 1;
	const unsigned short    elementChanged  = 2;
	
  void postNotification(required String notification, optional HTMLElement element);
};

Methods for Interface Accessibility

Interface ScreenReader

The screenreader attribute of the Accessibility interface must return an instance of the ScreenReader interface:

interface ScreenReader {
  readonly attribute InterfaceObject screenreader; // Editorial Note: Is it necessary to define this attribute in the IDL?
  // objects implementing the ScreenReader interface also implement the interfaces given below
};
ScreenReader implements ScreenReaderID;
ScreenReader implements ScreenReaderStatus;

[Supplemental, NoInterfaceObject]
interface ScreenReaderID {
  readonly attribute DOMString name;
  readonly attribute DOMString version;
};

[Supplemental, NoInterfaceObject]
interface ScreenReaderStatus {
  readonly attribute boolean active;
};

Properties for Interface ScreenReader

Note: The authors recommend that user agents adopt a domain-level security policy for the ScreenReader interface that is similar to the security policy for location data or cookies. A user should be able to explicitly disallow sharing of this information altogether, or on a per-domain basis.

Interface Magnifier

The magnifier attribute of the Accessibility interface must return an instance of the Magnifier interface:

interface Magnifier {
  readonly attribute InterfaceObject magnifier; // Editorial Note: Is it necessary to define this attribute in the IDL?
  // objects implementing the Magnifier interface also implement the interfaces given below
};
Magnifier implements MagnifierID;
Magnifier implements MagnifierStatus;
Magnifier implements MagnifierNotifications;

[Supplemental, NoInterfaceObject]
interface MagnifierID {
  readonly attribute DOMString name;
  readonly attribute DOMString version;
};

[Supplemental, NoInterfaceObject]
interface MagnifierStatus {
  readonly attribute boolean active;
};

[Supplemental, NoInterfaceObject]
interface MagnifierNotifications {
  // Editorial Note: I'm not partial to the method name focusPosition. Any other suggestions?
  void focusPosition(
         in DOMElement element,
         in optional array cursorRect,
         in optional array selectionPolygon
       );
};

Properties for Interface Magnifier

Methods for Interface Magnifier

Accessibility Events