We found 5 issueson montages.coworth fixing.
Watch the inspection.
We navigate your site the way customers would. Idle time is skipped.
Mobile controls fall under the 24px touch target minimum
On the mobile home feed, several controls measure under the WCAG 2.5.8 minimum of 24 by 24 CSS pixels and have no spacing exception to fall back on. The "Seek" slider (role="slider", class z-[673]) is 390px by 22px, and the "Save frame to a montage" button in the first post card is 141.7px by 21px, with safe clickable space of 22px and 21px respectively. Both fail axe-core's target-size rule at serious impact on /.
Try it: Open / on a 390px-wide mobile viewport and inspect the seek slider and the yellow "Add to montage" button: both are about 21 to 22px tall.
The featured montages carousel has an invalid list structure
On the home page, the "Explore featured montages" carousel is marked up as `div[role="list"] class="flex items-start gap-3"` but its children are `section[aria-label]` elements rather than list items. axe-core flags this as aria-required-children at critical impact, mapped to WCAG 2.0 A, 1.3.1. Screen readers announce the container as a list and then find no items in it, so the featured montage cards are not exposed as a countable set.
Try it: Open / and run axe-core (or Lighthouse accessibility) on the page, then inspect the div[role="list"] wrapping the featured montage cards and check the role of its direct children.
Featured montage tiles nest interactive controls
The featured montage tiles on the home page fail the axe-core rule nested-interactive at impact level serious. Each tile is a div with role="button" and tabindex="0", for example div[aria-label="Open Taylor Swift"], and each one contains focusable descendants, which the rule reports as "Element has focusable descendants". The same failure applies to the Bad Bunny and The Weeknd tiles in the "Explore featured montages" row. Nested focusable elements inside a button role leave keyboard and screen reader users with an ambiguous stop and no reliable way to reach the inner controls.
Try it: Open / on desktop and tab into the "Explore featured montages" row, or run axe-core on the page and look for the nested-interactive rule on div[aria-label="Open Taylor Swift"].
Feed cards render as blank black tiles
On the home feed at desktop width, several cards render as solid black rectangles with no thumbnail: the tile in the left column starting around x 91, y 648 shows only a TikTok watermark on black, and the tile beside it is fully black with no watermark or caption. Neighbouring cards in the same row render normal video frames, and other cards fall back to a "Preview unavailable. Open source" label, so these tiles carry no visible content or fallback text at all. The same blank tiles appear on a fresh load of the feed, at the same position in the grid.
Try it: Open the home feed on a desktop viewport and scroll to about 800px; look at the left two columns for cards that are entirely black with no thumbnail, caption, or "Preview unavailable" label.
A gear icon covers the share count on a video card
On the home feed, the share metric on a video card renders a second glyph on top of the number: a small gear icon sits over the digits of "128.9K", so only the leading characters are readable. The like count "319.1K" and comment count "9879" directly above it in the same stack render cleanly, so the overlap is isolated to the share row. The stray glyph also overlaps the bottom of the share arrow icon itself.
Try it: Open the home feed on desktop and scroll to the video card whose like count is 319.1K, then look at the share count below the comment count.
The "moody leopard print" text sits awkwardly
The card caption "moody leopard print" appears twice on the same thumbnail, once as faint low-contrast text over the image and once in the caption chip below.
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.



