Best practice for aria-disabled and keyboard focus management

The aria spec seems a little vague where disabled controls should be focusable.

Is the best practice to make the container widget focusable (the widget in tab order) and disable focus moving to children of the  parent widget.

The coding pattern being proposed is that the disabled control is discoverable through the tab order, but more complex keyboard interaction is disabled until the form control is enabled.

Jon