Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Posting on Qlik Community is temporarily paused for some users. Thank you for patience and we'll update you soon!
cancel
Showing results for 
Search instead for 
Did you mean: 
ol_dev
Creator
Creator

Qliksense 'Skip to Content' Button not behaving as expected

Hi,

For Qliksense accessibility mode, there is a 'Skip to Content' when the tab key is pressed, as the screenshot below. We expect that upon pressing 'Enter' or 'Space' key, it will lead us to the first visualization in the current sheet (eg. My Filterpane in the screenshot).

 

ol_dev_0-1789420249149.png

However, this is not how Qliksense behaves. What actually happens instead, is that it opens up the Asset panel and the focus shifted towards the Sheets button at the left panel. 

ol_dev_1-1789420341916.png

I do not understand, is this the intended behavior of Qliksense? If so, is there a way to bypass this default and instead force 'Skip to Content' button to lead to the first visualization in current sheet? I find this behavior extremely confusing, and our UX/UI designers are not fond of this either. I've seen this button on some websites and they all behave correctly that if you press such a button, it takes you to the first item in the body of the page. 

Can someone help? 

Labels (2)
2 Replies
gene22dony
Contributor
Contributor

Hello,


Pressing Enter or Space on the "Skip to Content" link should immediately shift keyboard focus to the first visualization on the sheet to comply with standard web accessibility guidelines (WCAG) and ensure smooth screen reader/keyboard navigation.       www metropcsbytmobile com


Best Regards

ol_dev
Creator
Creator
Author

Unfortunately this is not how Qliksense behaves. If you saw from my screenshots, you'd see that I explained this clearly that pressing enter or space will open up the Asset panel and move the focus to the Sheets button instead. I've tested this both locally from Qlik Desktop and in server environment Qlik Windows Enterprise, this behavior is consistent albeit strange and unintuitive.