Guide · reviewed 2026-11-03
How do I check the accessibility of a JavaScript app or a page behind a login?
Run the check on the page as it really appears in your browser, after its JavaScript has run and you have signed in, rather than on the HTML the server sends. Raasta’s free live-page check does this with a bookmarklet, and the axe DevTools extension and Lighthouse in Chrome DevTools work the same way. Then repeat the check in each state that matters (menu open, dialog open, form with errors) and test focus with a keyboard, because no tool sees every state on its own.
Why HTML-only checks miss these pages
Raasta’s quick scan, for example, checks a public page’s HTML with its CSS but without its JavaScript. That is fast and catches a lot on ordinary sites, but it is the wrong tool for the three kinds of page below.
- Single-page apps. Apps built with React, Vue, Angular and similar often send a near-empty HTML page and build the content with JavaScript. A check that reads the HTML without running the scripts sees very little.
- Pages behind a login. A scanner on a server cannot sign in as you, so account pages, dashboards and checkout steps are out of its reach.
- Hidden states. Menus, dialogs, tabs, accordions and error messages only exist in the page once someone opens or triggers them, so a check of the page as it first loads never sees them.
How to check the real page
- Raasta’s live-page check. Add the bookmarklet from raasta.danixsoft.com/scan/live, open your page, sign in and get it into the state you want, then click the bookmarklet. It runs axe-core on the page in your own browser and opens the results in Raasta. If the site’s security settings block bookmarklets, paste the console snippet into DevTools instead. Nothing is stored unless you choose to share the results.
- axe DevTools. Deque’s free browser extension runs the same axe-core rules on the current page from a DevTools panel.
- Chrome DevTools. Lighthouse audits the current page, and the Accessibility pane shows the name and role each element exposes to assistive technology.
Test each state, then test by hand
- Open menus and dialogs. Run the check with the main menu open, with each important dialog open and with tabs or accordions expanded.
- Errors and messages. Submit a form with mistakes and check again. Status messages such as “Added to cart” should be announced without moving focus (WCAG 4.1.3).
- Focus on route changes. When the app changes view without loading a new page, focus should move to the new content or its heading, and the page title should change.
- Dialogs. Focus should move into the dialog, stay inside it while open, close on Escape and return to the button that opened it.
See the common failures and their fixes, the WCAG 2.2 guide or the accessibility statement generator.
Questions
Is it safe to run a bookmarklet on a page with my account data?
Raasta’s live-page check runs in your browser and opens the results in Raasta; nothing is stored unless you choose to share a report. Avoid sharing reports of pages that show personal data.
Can Raasta’s monitoring check pages behind a login?
No. Monitoring loads public pages in headless Chrome, with JavaScript, but never signs in. Use the live-page check for signed-in pages.
Does running JavaScript mean the check finds everything?
No. It sees what is on the page at that moment, and automated rules still miss problems only a person can judge, such as focus order and whether labels make sense.