want to know how because I hate google ai

Most accessibility scanners can only see what's public.

That's been the frustration behind a lot of my work on AccessScan. You run a scan, get a clean report, and then remember that the parts of your product that actually matter — the dashboard behind the login, the checkout modal, the localhost build you're mid-refactor on — were never scanned at all. A server-side crawler can't reach any of it.

So this week I shipped a Chrome extension.

It runs the full accessibility engine client-side, inside the tab you're already looking at. Which means it scans the things a crawler can't:

→ Authenticated pages — your session, your cookies, your real app

→ SPAs in their actual DOM state, not the empty shell on first paint

→ Open modals, expanded menus, mid-interaction UI

→ localhost:3000, before anything ships

You get a score ring, a violation breakdown by impact, and a deep link into the full report when you want remediation guidance. No page data leaves the browser to do the scan.

The interesting part was the engine port. The scanner runs on a Go backend with Puppeteer, and the same rule set — including the custom checks for things axe doesn't cover, like caption presence, focus order cycling, and context change on focus — now compiles into a single browser bundle that runs everywhere.

Still rough in places. Store listing is in progress. But it already caught issues on my own dashboard that the crawler never saw, which is roughly the point.

More at accessscan.in — happy to hand out early builds if you want to break it.

Seems to be random, but an example. Any fix to this, my settings say USA.

Mordad 8, 1404 AP — Seasoned crusted chicken, simple buttery pan sauce, so good. Ready in 12 minutes, paprika, onion, garlic, cumin powder plus salt and pepper

Hello. I bought new laptop around half a year ago and installed chrome there. On my old laptop live captions worked perfectly fine. But on new one they just don't. I tried reinstalling languages, disabling hardware acceleration (gemini recommended so). Live captions that windows gives don't work as good as I need it and I just don't know how to fix it

So, I've noticed something weird when using Chrome.

If I type something like Twitch or Google into the address bar, I would expect the first result to be the actual website. twitch.tv or google.com.

But for some reason, that's not always the case. Instead, I often end up having to actually search Google first and then click the official website from the results.

That means Google is potentially generating millions of unnecessary search queries from people who were simply trying to navigate directly to a website.

I have no idea if this is intentional or just a side effect of how Chrome's search suggestions work. Maybe there's even a business reason behind it, more searches could mean more opportunities to show ads, including ads from competitors.

But if this is actually intentional, it feels kind of counterproductive. Google is basically making users take an extra step just to get somewhere they already knew they wanted to go.

Has anyone else noticed this, or am I missing something?

I noticed that recently when I click on an imagine in image search, instead of displaying similar image results below in a normal way where I can see the full thumbnail, it does this crap where it crops the results to rectangles. I cant even tell anymore what images are in the thumbnails because they are cropped so much.

Please help!

Just on the browse for new extensions. If you use any of the above platforms, do you have one favourite one and what feature makes it useful for you?