We found 4 issueson www.remove.bgworth fixing.
Watch the inspection.
We navigate your site the way customers would. Idle time is skipped.
Sample image buttons trigger a 422 response on /fr
On /fr, clicking one of the sample image buttons in the upload card (button.btn-image inside div.group/image-button) produces a failed request: the server responds with 422 and the console logs "Failed to load resource: the server responded with a status of 422 ()". The sample photos are the fastest path for a visitor to see the background removal work, and the request behind that action does not complete. The same error appeared again on a fresh load of the route.
Try it: Open /fr with the browser console open and click one of the sample photos under "Pas d'image ?", then watch for the 422 in the console and network panel.
Feature images on the home page have no alt text
Content images on the home page ship without any text alternative, failing the axe-core rule image-alt at impact level critical (WCAG 2.0 A, 1.1.1). Two nodes are flagged: the img with class max-w-[66%] loading rbg-feature-pages-batch-1-min.png, and the img inside .order-1 > figure > picture loading bulk-still.png. Neither carries an alt, aria-label, aria-labelledby, or title attribute. The same failure is present on /, /id, /de, /es, and /fr.
Try it: Open / and inspect the img with class max-w-[66%], or run axe-core on the home page and look at the image-alt rule.
The before and after slider has no accessible label
The image comparison slider on the home page is an `<input type="range" name="ImageDragger" class="bg-transparent">` with no associated label, no aria-label, and no aria-labelledby. axe-core flags it under the label rule at impact level critical, mapping to WCAG 2.0 A success criterion 4.1.2. The same control fails on /, /id, /de, /es and /fr. Screen reader and keyboard users reach the slider with no announced purpose, though the comparison it drives is illustrative rather than part of the upload flow.
Try it: Open / and run axe-core, or focus the range input inside the "Stunning quality" comparison and check what a screen reader announces.
Cookie banner link and Close button fail contrast
On the home page, the cookie consent banner renders green text on a light green panel below the WCAG AA contrast threshold. The "Cookie Policy" link and the "Close" button both measure 3.78:1 (foreground #008009, background #c1e7c2), against the required 4.5:1 for text at 16px and bold 14px. axe-core flags this as rule color-contrast at impact level serious, and both nodes are present on a fresh load.
Try it: Open the home page and inspect the cookie banner at the bottom right: sample the green link and Close label against the panel background, contrast is 3.78:1.
The " wraps with the single orphan word " text sits awkwardly
The helper text "Tidak ada gambar? Coba salah satu dari ini:" wraps with the single orphan word "ini:" on its own third line.
Probie fixes this for you.
This report came from one visit. When installed on your project, Probie watches real sessions, reproduces failures, and opens tested fixes as pull requests.
Sign up and get this fixedFree inspection
What should Probie inspect next?
Enter a project URL. There is nothing to install.
Probie checks every issue twice, respects robots.txt, and backs off at bot challenges.

