Please see this post in the Mac Support forum, with a possible fix/workaround involving Accessibility settings: