How to avoid the keyboard trap?

Currently I'm improving accessibility taking into account the WCAG, 2.1.2 No Keyboard Trap in particular. Keyboard operation within the application works perfectly due to Tab index, but the focus is trapped there. When pressing the Tab key, the focus starts within the web application, but after it has visited all the focus points, it goes back to the first focus point within the application, instead of going to the URL bar in the browser header. How can I get out of this keyboard trap? 
1 answers

Hi Zoey, 

I think that is perfectly acceptable behavior. Focusing the address bar in a browser can be done with standard browser shortcut (ctrl + L). So I don't think this should be a problem. 

If it is, I'm sorry but I'm not sure how to solve that 😇