UserAgent: Mozilla/5.0 (X11; CrOS x86_64 7834.60.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.95 Safari/537.36
Platform: 7834.60.0 (Official Build) stable-channel parrot

Steps to reproduce the problem:
Like normal use, open your browser tabs, and type the URL at the searchbox, and press enter. Go to a desired website to read content. Open the another browser with a different site.
Listen to Chromevox reading the headings correctly, it will say the heading name,--follow by the heading level It will say for example: "Search, Heading 1".
If the heading level is announced first, and then the title; most likely Chromevox isn't rendering elements correctly.
Try going to the links while the object navigation is enabled. Be sure to turn off sticky mode, otherwise it will not work.
Go through each element to varify if Chromevox is rendering elements correctly.
If you closed the window, and you're at the address bar, or bookmarks bar, and you pressed tab, most likely Chromevox didn't jump to the web content. And Chromevox needs to be redesigned.
Close all windows and try opening them again, and varify if Chromevox is doing it's job. If you're typing at the address bar, be sure to turn off sticky mode first. Since the last version of Chrome OS it was working correctly.
If you can manage your sites well while you're blind, such as a self-hosted website, try to use Chromevox by using the normal Search+Shift keys on your Chromebook.

What is the expected behavior?
It was working like normal. You can't enable/disable sticky mode while you're in the search box on a browser. But you can jump to the content area to turn off sticky mode, and use common keyboard shortcuts to access controls on the browser. The elements were rendering with Chromevox just fine.

What went wrong?
Chromevox is not doing it's job right. The screen-reader itself hasn't been rewritten for a long time. It didn't perform normally since the previous version of Chrome OS. That can render Chromevox itself too difficult to use.
When the browsers were closed. Chromevox didn't prompt the user to open the new window for the Chromevox commands to be effective. By default; Chromevox is able to navigate on the inside of a browser tab. When disabling flags to get this problem resolved, Chromevox still works the wrong way.

Did this work before? Yes 1 day ago since previous version of Chrome OS

Chrome version: 49.0.2623.95  Channel: stable
OS Version: 7834.60.0
Flash Version: Shockwave Flash 21.0 r0

Not sure what's going on with Chromevox, it was working great since the previous version. And I really like the way how Chromevox do it's job. On this current update; It was navigating well, but what I dislike about Chromevox, it takes too much memory. I've suspected there's a memory leak when Chromevox is running, and it also took alot of resources.
Also, parts of Chromevox appears to be broken, and the code needs to be reviewed.