Body: <p>I'm in Wordpress 5.2 and the Civi menus disappeared. I brought up my inspector and isolated the problem to Keyboard Accessible Menus (KAM). The fallout there is that CiviTutorial and Recent Items Menu have dependencies on KAM. There were a handful of minor security related updates that followed WP 5.2. I'm not sure what else might have interacted with KAM, but it's managed to kill about 1/3 of my day. </p>
  
  <p>Other than, am I alone with this problem, am I looking at bigger issue when KAM integrates into core?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-05-09T22:42:16.073Z
Comments.Text: KAM is already integrated into the current release of core.  What version are you using?
Comments.UserDisplayName: Aidan
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-05-10T14:46:15.067Z
Comments.Text: I'm on 5.11.0. Is the extension, which I don't want, installing for these other extensions and creating a conflict?
Comments.UserDisplayName: LyonsDigital
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-05-10T15:48:09.253Z
Comments.Text: It was moved to core in 5.12.0 and enhanced in 5.13.0. Might be worth asking on chat about conflicts with WP5.2, but there's a comment there saying 'working fine'
Comments.UserDisplayName: Aidan
Tags: <wordpress><extension>
Title: Conflict with Accessible Keyboard Menus
ThreadText: # Conflict with Accessible Keyboard Menus
  
  (Asked by: username_0 on 2019-05-09)
  
  I'm in Wordpress 5.2 and the Civi menus disappeared. I brought up my inspector and isolated the problem to Keyboard Accessible Menus (KAM). The fallout there is that CiviTutorial and Recent Items Menu have dependencies on KAM. There were a handful of minor security related updates that followed WP 5.2. I'm not sure what else might have interacted with KAM, but it's managed to kill about 1/3 of my day.
  
  Other than, am I alone with this problem, am I looking at bigger issue when KAM integrates into core?
  
  **Tags:** wordpress, extension
  
  > **Comments:**
  > **username_1**: KAM is already integrated into the current release of core.  What version are you using?  
  > **username_0**: I'm on 5.11.0. Is the extension, which I don't want, installing for these other extensions and creating a conflict?  
  > **username_1**: It was moved to core in 5.12.0 and enhanced in 5.13.0. Might be worth asking on chat about conflicts with WP5.2, but there's a comment there saying 'working fine'  
  
  ---
  
  ## 0 answers
  
  