https://showmeyourmumu.com
Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.SCORE
67
GRADE
D
FIX
8
REVIEW
6
PASS
10
INFO
0
Checks
2410 PASS 6 REVIEW 8 FIX
FLink & Button QualityAction61 issue(s) across 939 links and 93 buttonsFIX
Link & Button Quality
Action61 issue(s) across 939 links and 93 buttons
61 issue(s) across 939 links and 93 buttons
Critical::
23 link(s) with no accessible text
Links without text are announced as raw URLs by screen readers.
Got: /; /?view=weddings; /; /?view=weddings; /collections/new-mu; /collections/new-mu; /collections/dresses; /collections/fall-essentials; /collections/mumu-weddings-for-the-guest; /products/self-care-set-blush-blossoms-waffle-knit (+13 more)
Warning::
3 link(s) with generic text
Generic link text like 'click here' doesn't describe the destination.
Got: /pages/privacy-policy ("Learn more"); /pages/rewards ("Learn More"); /pages/rewards ("Learn More")
Warning::
8 link(s) open in new tab without warning
Add '(opens in new tab)' to link text or aria-label.
Got: https://www.instagram.com/showmeyourmumu; https://www.facebook.com/showmeyourmumu; http://www.youtube.com/user/ShowMeYourMutube; https://www.tiktok.com/@showmeyourmumu; https://www.instagram.com/showmeyourmumu; https://www.facebook.com/showmeyourmumu; http://www.youtube.com/user/ShowMeYourMutube; https://www.tiktok.com/@showmeyourmumu
Critical::
35 button(s) with no accessible text
Icon-only buttons need an aria-label so screen readers can announce them.
Got: button.mobile-menu__nav-btn-expand (#4136 on page); button.mobile-menu__nav-btn-expand (#4176 on page); button.mobile-menu__nav-btn-expand (#4225 on page); button.mobile-menu__nav-btn-expand (#4346 on page); button.mobile-menu__nav-btn-expand (#4394 on page); button.mobile-menu__nav-btn-expand (#4451 on page); button.mobile-menu__nav-btn-expand (#4476 on page); button.mobile-menu__nav-btn-expand (#4562 on page); button.mobile-menu__nav-btn-expand (#4598 on page); button.mobile-menu__nav-btn-expand (#4648 on page) (+25 more)
Info::
905 link(s) with descriptive text
939 links
23 empty
3 generic text
8 new tab
35 empty buttons
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| /pages/privacy-policy | Learn more | generic text | Replace with descriptive text |
Before: Learn more Suggested: Privacy Policy | |||
| /pages/rewards | Learn More | generic text | Replace with descriptive text |
Before: Learn More Suggested: Rewards | |||
| / | (empty) | empty | Add link text or aria-label |
| /?view=weddings | (empty) | empty | Add link text or aria-label |
| / | (empty) | empty | Add link text or aria-label |
| /?view=weddings | (empty) | empty | Add link text or aria-label |
| https://www.instagram.com/showmeyourmumu | Show Me Your Mumu Instagram | new tab | Add '(opens in new tab)' to text |
| https://www.facebook.com/showmeyourmumu | Show Me Your Mumu Facebook | new tab | Add '(opens in new tab)' to text |
| http://www.youtube.com/user/ShowMeYourMu… | Show Me Your Mumu YouTube | new tab | Add '(opens in new tab)' to text |
| https://www.tiktok.com/@showmeyourmumu | Show Me Your Mumu TikTok | new tab | Add '(opens in new tab)' to text |
| /collections/new-mu | (empty) | empty | Add link text or aria-label |
| /collections/new-mu | (empty) | empty | Add link text or aria-label |
| /collections/dresses | (empty) | empty | Add link text or aria-label |
| /collections/fall-essentials | (empty) | empty | Add link text or aria-label |
| /collections/mumu-weddings-for-the-guest | (empty) | empty | Add link text or aria-label |
| /products/self-care-set-blush-blossoms-w… | (empty) | empty | Add link text or aria-label |
| /collections/sparkle-shop | (empty) | empty | Add link text or aria-label |
| /collections/gift-shop | (empty) | empty | Add link text or aria-label |
| /collections/dresses | (empty) | empty | Add link text or aria-label |
| /collections/fall-essentials | (empty) | empty | Add link text or aria-label |
| /collections/mumu-weddings-for-the-guest | (empty) | empty | Add link text or aria-label |
| /collections/gift-shop | (empty) | empty | Add link text or aria-label |
| https://showmeyourmumu.com/products/self… | (empty) | empty | Add link text or aria-label |
| /collections/cozy-shop | (empty) | empty | Add link text or aria-label |
| /collections/sparkle-shop | (empty) | empty | Add link text or aria-label |
| https://showmeyourmumu.com/collections/m… | (empty) | empty | Add link text or aria-label |
| https://showmeyourmumu.com/collections/m… | (empty) | empty | Add link text or aria-label |
| /collections/mumu-weddings-new-for-the-b… | (empty) | empty | Add link text or aria-label |
| https://showmeyourmumu.com/collections/m… | (empty) | empty | Add link text or aria-label |
| https://www.instagram.com/showmeyourmumu | Show Me Your Mumu Instagram | new tab | Add '(opens in new tab)' to text |
| https://www.facebook.com/showmeyourmumu | Show Me Your Mumu Facebook | new tab | Add '(opens in new tab)' to text |
| http://www.youtube.com/user/ShowMeYourMu… | Show Me Your Mumu YouTube | new tab | Add '(opens in new tab)' to text |
| https://www.tiktok.com/@showmeyourmumu | Show Me Your Mumu TikTok | new tab | Add '(opens in new tab)' to text |
| /pages/rewards | Learn More | generic text | Replace with descriptive text |
Before: Learn More Suggested: Rewards | |||
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
963 links and buttons have descriptive text
Links without text are announced as raw URLs by screen readers.
/; /?view=weddings; /; /?view=weddings; /collections/new-mu; /collections/new-mu; /collections/dresses; /collections/fall-essentials; /collections/mumu-weddings-for-the-guest; /products/self-care-set-blush-blossoms-waffle-knit (+13 more)
Why this matters
Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.
Source: WCAG 2.1 SC 2.4.4
Generic link text like 'click here' doesn't describe the destination.
/pages/privacy-policy ("Learn more"); /pages/rewards ("Learn More"); /pages/rewards ("Learn More")
Why this matters
Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.
Learn more ▾ ▴
Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.
Source: WCAG 2.4.4 / Google Search Central
Add '(opens in new tab)' to link text or aria-label.
https://www.instagram.com/showmeyourmumu; https://www.facebook.com/showmeyourmumu; http://www.youtube.com/user/ShowMeYourMutube; https://www.tiktok.com/@showmeyourmumu; https://www.instagram.com/showmeyourmumu; https://www.facebook.com/showmeyourmumu; http://www.youtube.com/user/ShowMeYourMutube; https://www.tiktok.com/@showmeyourmumu
Why this matters
Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.
Learn more ▾ ▴
Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.
Source: MDN target / OWASP
Icon-only buttons need an aria-label so screen readers can announce them.
button.mobile-menu__nav-btn-expand (#4136 on page); button.mobile-menu__nav-btn-expand (#4176 on page); button.mobile-menu__nav-btn-expand (#4225 on page); button.mobile-menu__nav-btn-expand (#4346 on page); button.mobile-menu__nav-btn-expand (#4394 on page); button.mobile-menu__nav-btn-expand (#4451 on page); button.mobile-menu__nav-btn-expand (#4476 on page); button.mobile-menu__nav-btn-expand (#4562 on page); button.mobile-menu__nav-btn-expand (#4598 on page); button.mobile-menu__nav-btn-expand (#4648 on page) (+25 more)
Why this matters
Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.
Source: WCAG 2.1 SC 4.1.2
DTabindex Anti-PatternsAction0 positive, 58 -1-on-focusableFIX
Tabindex Anti-Patterns
Action0 positive, 58 -1-on-focusable
0 positive, 58 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <select>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <select>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <select>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <select>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <select>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <select>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <select>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <select>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <select>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <select>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
F404 Error PageActionHTTP 429, custom pageFIX
404 Error Page
ActionHTTP 429, custom page
HTTP 429, custom page
Warning::
Unexpected status code: HTTP 429
Expected HTTP 404 but received 429. This may confuse search engine crawlers.
Got: HTTP 429
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 429 ✗Page Title Verifying your connection... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
FFavicon & BrandingAction1 icon(s) detectedFIX
Favicon & Branding
Action1 icon(s) detected
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
DWeb ManifestActionNot foundFIX
Web Manifest
ActionNot found
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.
No web manifest found.
DDark Mode SupportActionNo dark mode signalsFIX
Dark Mode Support
ActionNo dark mode signals
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
Print Stylesheet
ActionNo print styles
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
BLandmark Structure8 landmarksREVIEW
Landmark Structure
8 landmarks
8 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
Multiple navigations need aria-label to distinguish them for screen readers.
Why this matters
Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.
Learn more ▾ ▴
When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.
Source: WAI-ARIA Authoring Practices
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Why this matters
Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.
Learn more ▾ ▴
WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.
Source: WCAG 2.1 SC 2.4.1
CHeading HierarchyAction45 headings, 1 skip(s)REVIEW
Heading Hierarchy
Action45 headings, 1 skip(s)
45 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
- H3 Almost As Cute As You
- H4 Katelyn Mini Dress
- H5 $168 $168
- H4 Beckett Sweater
- H5 $158 $158
- H4 Olsen Mini Dress
- H5 $178 $178
- H4 Classic PJ Set
- H5 $138 $138
- H4 Lively Jumpsuit
- H5 $238 $238
- H4 Billini Finley Cowboy Boot
- H5 $140 $140
- H4 Sadie Maxi Dress
- H5 $198 $198
- H4 Jeanette Dress
- H5 $188 $188
- H4 Fireside Sweater
- H5 $168 $168
- H4 Stay In PJ Set
- H5 $138 $138
- H4 Studio Halter Jumpsuit
- H5 $238 $238
- H4 Cottage Cardigan
- H5 $148 $148
- H4 Drifter Mini Dress
- H5 $178 $178
- H3 Want $10 Off and Free Shipping?
- H2 Join Club Mumu!
- H5 Want $10 Off & Free Shipping? skipped
- H5 Free Exchanges & Easy Returns
- H5 Shop Our Mobile App!
- H5 Successfully Added to Cart!
- H5 Recommended for you
- H5 Tammi Twofer Maxi Dress ~ Champange Multi | $198.00
- H5 All Night Skort ~ Red Plaid Sequins | $148.00
- H5 Kenza Fringe Mini Dress ~ Petals in Splendor | $178.00
- H5 Olsen Maxi Dress ~ Black Chiffon | $198.00
- H5 Olsen Maxi Dress ~ Chocolate Chiffon | $198.00
- H5 Tammi Twofer Maxi Dress ~ Champange Multi | $198.00
- H5 All Night Skort ~ Red Plaid Sequins | $148.00
- H5 Kenza Fringe Mini Dress ~ Petals in Splendor | $178.00
- H5 Olsen Maxi Dress ~ Black Chiffon | $198.00
- H5 Olsen Maxi Dress ~ Chocolate Chiffon | $198.00
- H5 Tammi Twofer Maxi Dress ~ Champange Multi | $198.00
Every page should have one H1 that describes the page content.
Why this matters
No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.
Learn more ▾ ▴
The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.
Source: WCAG 2.4.6 / Google Search Central
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Why this matters
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
BAlt Text Quality2 of 65 images have issuesREVIEW
Alt Text Quality
2 of 65 images have issues
2 of 65 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
22 decorative image(s) correctly marked
Info::
41 image(s) with good alt text
65 images 41 good alt text 22 decorative 2 missing
| Issue | Count |
|---|---|
| missing | 2 image(s) |
Images without alt text are invisible to screen readers.
Why this matters
Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.
Learn more ▾ ▴
WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.
Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report
CIframe AccessibilityAction4/8 iframe(s) missing title; 0 placeholder(s)REVIEW
Iframe Accessibility
Action4/8 iframe(s) missing title; 0 placeholder(s)
4/8 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://showmeyourmumu.com/web-pixels@264bf420w2e1681cap8d55857fm7d879f9c/app/w…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://showmeyourmumu.com/web-pixels@264bf420w2e1681cap8d55857fm7d879f9c/custo…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://showmeyourmumu.com/web-pixels@264bf420w2e1681cap8d55857fm7d879f9c/custo…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://showmeyourmumu.com/web-pixels@264bf420w2e1681cap8d55857fm7d879f9c/custo…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
BTap Target Adequacy2 tap target(s) too small or too close togetherREVIEW
Tap Target Adequacy
2 tap target(s) too small or too close together
2 tap target(s) too small or too close together
Info::
2 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
CLighthouse Accessibility AuditsActionScore 79/100 — 6 failing, 22 passedREVIEW
Lighthouse Accessibility Audits
ActionScore 79/100 — 6 failing, 22 passed
79
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
ARIA
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
Why this matters
Informational: a Permissions-Policy directive showing feature -> allowed origins.
Source: MDN Permissions-Policy
| Failing Elements |
|---|
This website uses cookies to ensure you get the best experience. Learn more
Pre… body.promo-bar-active > div#pandectes-banner |
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Names and labels
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
ul.mobile-menu__nav > li.mobile-menu__nav-item > a.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand ul.mobile-menu__nav > li.mobile-menu__nav-item > a.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand |
ul.mobile-menu__nav > li.mobile-menu__nav-item > span.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand ul.mobile-menu__nav > li.mobile-menu__nav-item > span.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand |
ul.mobile-menu__nav > li.mobile-menu__nav-item > a.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand ul.mobile-menu__nav > li.mobile-menu__nav-item > a.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand |
ul.mobile-menu__nav > li.mobile-menu__nav-item > a.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand ul.mobile-menu__nav > li.mobile-menu__nav-item > a.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand |
ul.mobile-menu__nav > li.mobile-menu__nav-item > a.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand ul.mobile-menu__nav > li.mobile-menu__nav-item > a.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand |
ul.mobile-menu__nav > li.mobile-menu__nav-item > a.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand ul.mobile-menu__nav > li.mobile-menu__nav-item > a.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand |
ul.mobile-menu__nav > li.mobile-menu__nav-item > a.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand ul.mobile-menu__nav > li.mobile-menu__nav-item > a.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand |
ul.mobile-menu__nav > li.mobile-menu__nav-item > a.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand ul.mobile-menu__nav > li.mobile-menu__nav-item > a.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand |
ul.mobile-menu__nav > li.mobile-menu__nav-item > a.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand ul.mobile-menu__nav > li.mobile-menu__nav-item > a.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand |
ul.mobile-menu__nav > li.mobile-menu__nav-item > span.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand ul.mobile-menu__nav > li.mobile-menu__nav-item > span.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand |
ul.mobile-menu__nav > li.mobile-menu__nav-item > a.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand ul.mobile-menu__nav > li.mobile-menu__nav-item > a.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand |
ul.mobile-menu__nav > li.mobile-menu__nav-item > a.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand ul.mobile-menu__nav > li.mobile-menu__nav-item > a.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand |
ul.mobile-menu__nav > li.mobile-menu__nav-item > a.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand ul.mobile-menu__nav > li.mobile-menu__nav-item > a.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand |
ul.mobile-menu__nav > li.mobile-menu__nav-item > a.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand ul.mobile-menu__nav > li.mobile-menu__nav-item > a.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand |
ul.mobile-menu__nav > li.mobile-menu__nav-item > a.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand ul.mobile-menu__nav > li.mobile-menu__nav-item > a.mobile-menu__nav-btn > button.mobile-menu__nav-btn-expand |
div#nosto-homepage-1 > div.fps-nosto > div.fps-nosto__products > button.slick-prev div#nosto-homepage-1 > div.fps-nosto > div.fps-nosto__products > button.slick-prev |
div#nosto-homepage-1 > div.fps-nosto > div.fps-nosto__products > button.slick-next div#nosto-homepage-1 > div.fps-nosto > div.fps-nosto__products > button.slick-next |
body.promo-bar-active > div#account-modal > div.account-modal__wrapper > button.drop-modal__close body.promo-bar-active > div#account-modal > div.account-modal__wrapper > button.drop-modal__close |
body.promo-bar-active > div.drop-modal > div.account-modal__wrapper > button.drop-modal__close body.promo-bar-active > div.drop-modal > div.account-modal__wrapper > button.drop-modal__close |
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.mobile-menu__main > ul.mobile-menu__nav > div.mobile-menu__logo-links > a div.mobile-menu__main > ul.mobile-menu__nav > div.mobile-menu__logo-links > a |
div.u-hide-above-medlarge > div.ft-grid > div.ft-grid__grid > a.ft-grid__item div.u-hide-above-medlarge > div.ft-grid > div.ft-grid__grid > a.ft-grid__item |
div.u-hide-above-medlarge > div.ft-grid > div.ft-grid__grid > a.ft-grid__item div.u-hide-above-medlarge > div.ft-grid > div.ft-grid__grid > a.ft-grid__item |
div.u-hide-above-medlarge > div.ft-grid > div.ft-grid__grid > a.ft-grid__item div.u-hide-above-medlarge > div.ft-grid > div.ft-grid__grid > a.ft-grid__item |
div.u-hide-above-medlarge > div.ft-grid > div.ft-grid__grid > a.ft-grid__item div.u-hide-above-medlarge > div.ft-grid > div.ft-grid__grid > a.ft-grid__item |
div.u-hide-above-medlarge > div.two-tile-grid > div.two-tile-grid__grid > a.two-tile-grid__item div.u-hide-above-medlarge > div.two-tile-grid > div.two-tile-grid__grid > a.two-tile-grid__item |
div.u-hide-above-medlarge > div.two-tile-grid > div.two-tile-grid__grid > a.two-tile-grid__item div.u-hide-above-medlarge > div.two-tile-grid > div.two-tile-grid__grid > a.two-tile-grid__item |
div.u-hide-above-medlarge > div.ft-grid > div.ft-grid__grid > a.ft-grid__item div.u-hide-above-medlarge > div.ft-grid > div.ft-grid__grid > a.ft-grid__item |
div.u-hide-above-medlarge > div.ft-grid > div.ft-grid__grid > a.ft-grid__item div.u-hide-above-medlarge > div.ft-grid > div.ft-grid__grid > a.ft-grid__item |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Navigation
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Want $10 Off & Free Shipping? section.value-props > div.value-prop__item > div.value-prop__item-text > h5.heading |
These are opportunities to improve keyboard navigation in your application.
Tables and lists
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
New Mu
Featured
Bestsellers
Back in Stock
By Category
Dresses
Rompers
Tops
Deni… section.mobile-menu > div.mobile-menu__inner > div.mobile-menu__main > ul.mobile-menu__nav |
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Best practices
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Terms of Use div.footer__bottom > ul.footer__bottom-links > li > a |
Do Not Sell or Share My Personal Information div.footer__bottom > ul.footer__bottom-links > li > a |
These items highlight common accessibility best practices.
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A+Heading Text QualityAll 45 heading(s) have substantive, well-formed textPASS
Heading Text Quality
All 45 heading(s) have substantive, well-formed text
All 45 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
AForm Accessibility1 of 6 controls have issuesPASS
Form Accessibility
1 of 6 controls have issues
1 of 6 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select>
Info::
5 control(s) properly labeled
6 controls
5 labeled
0 placeholder only
1 unlabeled
| Control | Type | Label | Method |
|---|---|---|---|
| pref_1 | checkbox | none | |
| pref_2 | checkbox | none | |
| pref_4 | checkbox | none | |
| #search-value | search | Search | aria-label |
| #search-value | search | Search | aria-label |
| select | select | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<select>
Why this matters
Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.
Source: WCAG 2.1 SC 3.3.2
A+Form Input Types6 form control(s) checked, no type mismatchesPASS
Form Input Types
6 form control(s) checked, no type mismatches
6 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+Form Input Quality6 form control(s) checked, no input-semantic issuesPASS
Form Input Quality
6 form control(s) checked, no input-semantic issues
6 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+Mobile Keyboard & AutofillNo autofill-eligible form controlsPASS
Mobile Keyboard & Autofill
No autofill-eligible form controls
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+Document LanguageLang attribute set to "en"PASS
Document Language
Lang attribute set to "en"
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+Mobile-Readable Font SizesAll 4 visible text node(s) render at >= 12 CSS pixelsPASS
Mobile-Readable Font Sizes
All 4 visible text node(s) render at >= 12 CSS pixels
All 4 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+PWA DepthNo PWA depth issues detectedPASS
PWA Depth
No PWA depth issues detected
No PWA depth issues detected
Info::
No PWA depth issues detected
A+Mobile UX Depth1 mobile-depth signal(s) detectedPASS
Mobile UX Depth
1 mobile-depth signal(s) detected
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
A+Color Contrast (Screenshot)20 text elements analyzed, 0 fail WCAG AAPASS
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
20 pass
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h2 Join Club Mumu! | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Almost As Cute As Yo… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Want $10 Off and Fre… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| title Women's Clothing & B… | 19.87:1 | 4.5:1 | #000000 | #FFF7F5 | Pass |
| span This website uses co… | 20.29:1 | 4.5:1 | #000000 | #FFFAF9 | Pass |
| a Learn more | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| button Preferences | 19.74:1 | 4.5:1 | #000000 | #FFF6F4 | Pass |
| button Accept | 18.94:1 | 4.5:1 | #000000 | #FFF0ED | Pass |
| button ✕ | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Manage consent prefe… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| button Reject all | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| button Accept all | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| div We use cookies to op… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| div Strictly necessary c… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Always allowed | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| div These cookies are es… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| button Cookies details | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| dt Name | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| dd cart_currency | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| dt Provider | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.