Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.F404 Error PageActionHTTP 429, custom pageFIX
FFavicon & BrandingActionNo icons detectedFIX
DWeb ManifestActionNot foundFIX
No web manifest found.
DDark Mode SupportActionTheme color onlyFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
BHeading Hierarchy19 headings, 1 skip(s)REVIEW
- H2 Cookie consent
- H1 shop.jorulf.se
- H2 Country/Region
- H2 Language
- H2 Country/Region
- H2 Language
- H2 Your cart is empty
- H2 Your cart is empty
- H3 A View into the Infinite
- H3 When Winter Glows
- H3 The Horizon's Promise
- H3 The Water's Handwriting
- H3 What the Skin Remembers
- H3 Strength at Rest
- H3 The City Beyond Stillness
- H3 Time in Motion
- H1 Fine Art Photography Prints by Anders Jorulf duplicate H1
- H2 Search
- H4 Products skipped
A page should have only one H1. Multiple H1s dilute the document outline.
Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.
Learn more ▾ ▴
HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.
Source: WCAG 2.4.6 / Google Search Central
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
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
BColor Contrast (Screenshot)20 text elements analyzed, 0 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 shop.jorulf.se | 4.04:1 | 3.0:1 | #000000 | #6A6D71 | Pass |
| h1 Fine Art Photography… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Cookie consent | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Country/Region | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Language | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Country/Region | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Language | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Your cart is empty | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Search | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 A View into the Infi… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 When Winter Glows | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 The Horizon's Promis… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 The Water's Handwrit… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 What the Skin Rememb… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Strength at Rest | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 The City Beyond Stil… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Time in Motion | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| title Fine Art Photography… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| p We and our partners,… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Privacy Policy | 4.68:1 | 4.5:1 | #000000 | #6B7982 | 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.
A+Landmark Structure10 landmarksPASS
A+Heading Text QualityAll 19 heading(s) have substantive, well-formed textPASS
AAlt Text Quality1 of 30 images have issuesPASS
| Issue | Count |
|---|---|
| missing | 1 image(s) |
Images without alt text are invisible to screen readers.
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
A+Form AccessibilityAll 6 controls labeledPASS
| Control | Type | Label | Method |
|---|---|---|---|
| #country-filter-input | search | Find country | aria-label |
| #drawerSelect | select | Language | aria-label |
| #country-filter-input | search | Find country | aria-label |
| #dropdownSelect | select | Language | aria-label |
| #EmailInput-AbCtDWU5uSzRKV2VJZ__email_signup_crihX7 | for/id | ||
| #cmdk-input | search | Search | for/id |
ALink & Button Quality137 links, 37 buttons — all OKPASS
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://shop.jorulf.se/policies/privacy-… | Privacy Policy | new tab | Add '(opens in new tab)' to text |
| https://www.shopify.com?utm_campaign=pow… | Powered by Shopify | new tab | Add '(opens in new tab)' to text |
Add '(opens in new tab)' to link text or aria-label.
https://shop.jorulf.se/policies/privacy-policy; https://www.shopify.com?utm_campaign=poweredby&utm_medium=shopify&utm_source=…
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
A+Form Input Types6 form control(s) checked, no type mismatchesPASS
A+Form Input Quality6 form control(s) checked, no input-semantic issuesPASS
A+Mobile Keyboard & AutofillNo autofill-eligible form controlsPASS
A+Document LanguageLang attribute set to "en"PASS
A+Tabindex Anti-Patterns72 explicit tabindex attribute(s) checked, no anti-patternsPASS
A+Iframe AccessibilityNo iframes on this pagePASS
A+Tap Target AdequacyAll tap targets meet WCAG 2.5.5/2.5.8 sizingPASS
A+Mobile-Readable Font SizesAll 12 visible text node(s) render at >= 12 CSS pixelsPASS
A+PWA DepthNo PWA depth issues detectedPASS
A+Mobile UX Depth1 mobile-depth signal(s) detectedPASS
ALighthouse Accessibility AuditsScore 93/100 — 2 failing, 25 passedPASS
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
A View into the Infinite div.product-card__content > a.contents > div.spacing-style > p |
These are opportunities to improve keyboard navigation in your application.
Names and labels
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.hero__container > div.hero__media-grid > div.hero__media-wrapper > img.hero__media div.hero__container > div.hero__media-grid > div.hero__media-wrapper > img.hero__media |
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.