Need tab support
See original GitHub issueDescription
As mentioned here https://docs.cypress.io/v1.0/docs/type#section-typing-tab-key-does-not-work. For accessibility testing I need to be able to tell the keyboard to press tab. If cy.tab
is not currently supported is there some way to work around this?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1271
- Comments:68 (14 by maintainers)
Top Results From Across the Web
Tab Service Company
Need a business process outsourcing company (BPO) in Chicago, IL? Contact Tab Service Company. Click to learn more about our outsourcing services.
Read more >Ultimate Guitar Support
Ultimate Guitar Customer Support. Here you can find answers to frequently asked questions ... I'm a contributor and have free access to Tab...
Read more >Set up and use iCloud Tabs - Apple Support
Complete these steps on all of the devices where you want to share tabs. On your iPhone, iPad, or iPod touch. Go to...
Read more >10 Things Your Help & Support Tab Should Do - Medium
Many websites and apps have a “help”, “support” or “feedback” tab somewhere on the side of the window. And often the user experience...
Read more >ARIA: tab role - Accessibility - MDN Web Docs - Mozilla
Elements with the role tab must either be a child of an element with the tablist role, or have their id as part...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
thanks for the response
The tab key is one of the primary ways a keyboard user moves around the page so it’s difficult to write a high confidence accessibility test without it. In my case I’m building custom components that comply with the aria authoring practices guide. The first thing I would like to do on every page is press tab to focus the element. I can fake this by calling click() but it’s not really the same. A non-sighted user will never use the mouse so calling click() feels a bit like cheating and you could imagine a situation where an element has one behavior when clicked and a different behavior when focused via the tab key.
Currently working on this, however it may introduce breaking changes around
cy.type()
, so I’ve set the milestone for4.0.0