Sådan fungerer udbedring af tilgængelighed, trin for trin

Accessibility fixes from Validiscan

This pull request fixes 3 accessibility problems that Validiscan found on Nordlicht Outdoor (https://nordlicht-outdoor.example). Every change is an ordinary edit to your theme source: no scripts, no overlays, nothing extra that runs in your visitors’ browsers. Each fix is a separate commit, so you can review, keep or revert them one by one.

Nothing was changed on your live site Validiscan only created this branch and this pull request. Nothing was pushed to your default branch and nothing was deployed to your live site; merging and deploying stay entirely under your control.

Summary

Tabellen kan rulles vandret.

What changed and why

1. <html> element must have a lang attribute

• WCAG criterion: 3.1.1 Language of Page (A)
• Impact: Serious
• Files: layout/theme.liquid (modified, +1 -1)
• Open this finding in Validiscan (screenshots and all affected pages; login required)

Adds lang="{{ request.locale.iso_code }}" to the <html> element so screen readers pronounce the page in the right language (WCAG 3.1.1).

2. Images must have alternative text

• WCAG criterion: 1.1.1 Non-text Content (A)
• Impact: Critical
• Files: sections/header.liquid (modified, +1 -1)
• Open this finding in Validiscan (screenshots and all affected pages; login required)

The logo image is the only content of the home link, so it gets the shop name as its alternative text (WCAG 1.1.1).

3. Buttons must have discernible text

• WCAG criterion: 4.1.2 Name, Role, Value (A)
• Impact: Critical
• Files: sections/header.liquid (modified, +1 -1)
• Open this finding in Validiscan (screenshots and all affected pages; login required)

The icon-only search button gets an accessible name from the theme’s locale file (WCAG 4.1.2).

Not included

One approved fix could not be applied: the affected code has changed since it was prepared, or another fix in this delivery changes the same lines. Validiscan will prepare it again and deliver it separately.

• Links must have discernible text

Review checklist

• Read the diff of each commit; the changes are small and limited to the files listed above.
• Deploy this branch to a preview or staging environment (not to your live shop).
• Open the affected pages and check that they look and work as before.
• Operate the changed elements with the keyboard only (Tab, Shift+Tab, Enter, Space, Esc): everything must be reachable and the focus visible.
• If you can, check the changed elements with a screen reader (for example NVDA or VoiceOver).
• Merge when you are satisfied. Validiscan then checks the affected pages with a verification scan.

_{Prepared by Validiscan (validiscan.com) on 24 September 2026 · delivery 9f8e7d6c}

Accessibility fixes for Nordlicht Outdoor

Prepared by Validiscan on 24 September 2026 for https://nordlicht-outdoor.example. This document describes 3 source code changes that fix accessibility problems found on Nordlicht Outdoor, with the exact code change for each finding and instructions for applying them.

Nothing was changed on your live site. You or your developer apply the changes, test them and publish them. They are ordinary edits to your theme source: no scripts, no overlays.

Summary

Tabellen kan rulles vandret.

How to apply

With git

Unpack this archive, then run these commands in the root folder of your theme (the folder that contains the paths shown below), replacing path/to/bundle with the folder you unpacked the archive to. The first command only checks that the changes apply; the second applies all of them.

git apply --check path/to/bundle/validiscan-a11y.patch
git apply path/to/bundle/validiscan-a11y.patch

To apply the fixes one at a time instead, apply the files in diffs/ in numeric order with git apply.

Without git

The folder files/ contains the complete modified files, based on the theme export you uploaded. Make a backup of your theme, then copy each file over the file with the same path.

Alternatively, make each change by hand in a code editor, following the sections below.

How to read a change: lines starting with - are removed, lines starting with + are added, and all other lines are unchanged context that helps you find the right place. The line numbers after @@ are approximate if the file has changed in the meantime.

Changes

1. <html> element must have a lang attribute

• WCAG criterion: 3.1.1 Language of Page (A)
• Impact: Serious
• Files: layout/theme.liquid (modified, +1 -1)
• Patch file: diffs/01-a1b2c3d4.patch
• Open this finding in Validiscan (screenshots and all affected pages; login required)

Adds lang="{{ request.locale.iso_code }}" to the <html> element so screen readers pronounce the page in the right language (WCAG 3.1.1).

diff --git a/layout/theme.liquid b/layout/theme.liquid
--- a/layout/theme.liquid
+++ b/layout/theme.liquid
@@ -1,5 +1,5 @@
 <!doctype html>
-<html class="no-js">
+<html class="no-js" lang="{{ request.locale.iso_code }}">
   <head>
     <title>{{ page_title }}</title>
   </head>

2. Images must have alternative text

• WCAG criterion: 1.1.1 Non-text Content (A)
• Impact: Critical
• Files: sections/header.liquid (modified, +1 -1)
• Patch file: diffs/02-b2c3d4e5.patch
• Open this finding in Validiscan (screenshots and all affected pages; login required)

The logo image is the only content of the home link, so it gets the shop name as its alternative text (WCAG 1.1.1).

diff --git a/sections/header.liquid b/sections/header.liquid
--- a/sections/header.liquid
+++ b/sections/header.liquid
@@ -1,6 +1,6 @@
 <header class="header">
   <a href="/" class="header__heading-link">
-    <img src="{{ 'logo.svg' | asset_url }}" width="120" height="40">
+    <img src="{{ 'logo.svg' | asset_url }}" width="120" height="40" alt="{{ shop.name }}">
   </a>
   <button type="button" class="header__icon header__icon--search">
     <svg class="icon icon-search" aria-hidden="true"></svg>

3. Buttons must have discernible text

• WCAG criterion: 4.1.2 Name, Role, Value (A)
• Impact: Critical
• Files: sections/header.liquid (modified, +1 -1)
• Patch file: diffs/03-c3d4e5f6.patch
• Open this finding in Validiscan (screenshots and all affected pages; login required)

The icon-only search button gets an accessible name from the theme’s locale file (WCAG 4.1.2).

diff --git a/sections/header.liquid b/sections/header.liquid
--- a/sections/header.liquid
+++ b/sections/header.liquid
@@ -2,7 +2,7 @@
   <a href="/" class="header__heading-link">
     <img src="{{ 'logo.svg' | asset_url }}" width="120" height="40">
   </a>
-  <button type="button" class="header__icon header__icon--search">
+  <button type="button" class="header__icon header__icon--search" aria-label="{{ 'general.search.search' | t }}">
     <svg class="icon icon-search" aria-hidden="true"></svg>
   </button>
 </header>

Not included

These approved fixes could not be applied to your theme export: the affected code differs from the version they were prepared for, or another fix in this bundle changes the same lines. They are not part of this bundle; Validiscan will prepare them again.

• Links must have discernible text (sections/header.liquid)

After applying

1. Test the affected pages in a preview or staging environment before publishing.
2. Operate the changed elements with the keyboard only: everything must be reachable and the focus visible.
3. Publish the changes and let us know: Validiscan then checks the affected pages with a verification scan.

Prepared by Validiscan (validiscan.com) on 24 September 2026 · delivery 9f8e7d6c

Questions? Write to info@validiscan.com and mention delivery 9f8e7d6c.

Validiscan accessibility fixes for Nordlicht Outdoor

This archive contains 3 accessibility fixes for your theme, prepared by Validiscan on 24 September 2026. Start with PATCH.md: it explains every change and how to apply it.

Contents

• PATCH.md: what changed and why, per finding, with the exact code change and instructions
• validiscan-a11y.patch: every change of this bundle in one patch (unified diff; applies with git apply)
• diffs/: the same changes as one patch file per fix, to apply one at a time in numeric order
• files/: the complete modified files, based on your theme export
• README.md: this file

Quick start

1. Make a backup of your theme, or work on a copy or a preview theme.
2. Apply the patches with git apply (see PATCH.md) or copy the files from files/ over your theme.
3. Test the affected pages, then publish.

Nothing in this archive runs on your site by itself: there are no scripts, widgets or overlays. Every fix is a change to your own theme source.

Prepared by Validiscan (validiscan.com) on 24 September 2026 · delivery 9f8e7d6c

Questions? Write to info@validiscan.com and mention delivery 9f8e7d6c.