The API basically allows you to get a style sheets for the document. P2 - Several WG participants have requested this be raised to P2. In short, some users with physical disabilities may benefit from this min requirement for the mouse. No change to checkpoint 7.3 based on JG comments about users with physical disabilities. Also add a recommendation that even if the UA doesn't claim conformance for a certain modality, that they should still implement as many functionalities as they can through those devices.
Technique seems reasonable.
No change to the document. These are functional requirements. Add information about the resource being at the same or a different domain. Leave this issue open so that we return to it when we evaluate current support for emulation of device-specific events. Propose a list of things we are expecting UAs to recognize in scripts.