Liquid Theme A11y

作者 Shopifyae3e4cc3f454無授權條款收錄於 2026年10月8日更新於 2026年10月8日

Implement WCAG 2.2 accessibility patterns in Shopify Liquid themes. Covers e-commerce-specific components including product cards, carousels, cart drawers, price display, forms, filters, and modals. Use when building accessible theme components, fixing accessibility issues, or reviewing ARIA patterns in .liquid files.

AI 產生的概覽

為 Shopify Liquid 主題元件(如商品卡片、輪播、彈出視窗與表單)提供 WCAG 2.2 無障礙實作模式。

功能
此技能提供在 Shopify Liquid 主題中實作無障礙元件的參考指引,涵蓋地標區域、跳轉連結、標題層級、焦點管理、表單、篩選器、輪播、彈出視窗、購物車抽屜、分頁、工具提示與價格顯示。它提供 HTML 與 CSS 程式碼片段,以及 ARIA 規則、對比度要求、減少動態效果處理與漸進增強說明。它也指向兩份隨附的參考文件,分別關於元件模式與焦點/鍵盤行為。它產出的是指引與程式碼範例,而非執行工具。
適用情境
適用於建置或審查 Shopify Liquid 主題元件的無障礙實作、修正 ARIA 或鍵盤操作問題,或檢查商品卡片、篩選器與購物車抽屜等電商介面是否符合 WCAG 2.2。
執行需求
無需指令碼或執行環境,僅包含說明與參考文件。範例假定處於 Shopify Liquid 主題環境,並需了解 HTML、CSS 與 ARIA。

Accessibility for Shopify Liquid Themes

Core Principle

Every interactive component must work with keyboard only, screen readers, and reduced-motion preferences. Start with semantic HTML — add ARIA only when native semantics are insufficient.

Decision Table: Which Pattern?

ComponentHTML ElementARIA PatternReference
Expandable content<details>/<summary>None neededAccordion
Modal/dialog<dialog>aria-modal="true"Modal
Tooltip/popup[popover] attributerole="tooltip" fallbackTooltip
Dropdown menu<nav> + <ul>aria-expanded on triggersNavigation
Tab interface<div>role="tablist/tab/tabpanel"Tabs
Carousel/slider<div>role="region" + aria-roledescriptionCarousel
Product card<article>aria-labelledbyProduct card
Form<form>aria-invalid, aria-describedbyForms
Cart drawer<dialog>Focus trapCart drawer
Price display<span>aria-label for contextPrices
Filters<form> + <fieldset>aria-expanded for disclosuresFilters

Page Structure

Landmarks

html
<body>  <a href="#main-content" class="skip-link">{{ 'accessibility.skip_to_content' | t }}</a>  <header role="banner">    <nav aria-label="{{ 'accessibility.main_navigation' | t }}">...</nav>  </header>  <main id="main-content">    <!-- All page content inside main -->  </main>  <footer role="contentinfo">    <nav aria-label="{{ 'accessibility.footer_navigation' | t }}">...</nav>  </footer></body>
  • Single <header>, <main>, <footer> per page
  • Multiple <nav> elements must have distinct aria-label
  • All content must live inside a landmark

Skip Link

css
.skip-link {  position: absolute;  inset-inline-start: -999px;  z-index: 999;}.skip-link:focus {  position: fixed;  inset-block-start: 0;  inset-inline-start: 0;  padding: 1rem;  background: var(--color-background);  color: var(--color-foreground);}

Headings

  • One <h1> per page, never skip levels (h1 → h3)
  • Use real heading elements, not styled divs
  • Template: <h1> is typically the page/product title

Focus Management

Focus Indicators

css
/* All interactive elements */:focus-visible {  outline: 2px solid rgb(var(--color-focus));  outline-offset: 2px;}
/* High contrast mode */@media (forced-colors: active) {  :focus-visible {    outline: 3px solid LinkText;  }}
  • Minimum 3:1 contrast ratio for focus indicators
  • Use :focus-visible (not :focus) to avoid showing on click
  • Never outline: none without a visible replacement

Focus Trapping (Modals/Drawers)

  • Trap focus inside modals, drawers, and dialogs
  • Return focus to trigger element on close
  • First focusable element gets focus on open
  • Query all focusable elements: a[href], button:not([disabled]), input:not([disabled]), select, textarea, [tabindex]:not([tabindex="-1"])

See focus and keyboard patterns [blocked] for full FocusTrap implementation.

Component Patterns

Product Card

html
<article class="product-card" aria-labelledby="ProductTitle-{{ product.id }}">  <a href="{{ product.url }}" class="product-card__link" aria-labelledby="ProductTitle-{{ product.id }}">    <img      src="{{ product.featured_image | image_url: width: 400 }}"      alt="{{ product.featured_image.alt | escape }}"      loading="lazy"      width="{{ product.featured_image.width }}"      height="{{ product.featured_image.height }}"    >  </a>  <h3 id="ProductTitle-{{ product.id }}">    <a href="{{ product.url }}">{{ product.title }}</a>  </h3>  <div class="product-card__price" aria-label="{{ 'products.price_label' | t: price: product.price | money }}">    {{ product.price | money }}  </div>  <button    class="product-card__quick-add"    tabindex="-1"    aria-label="{{ 'products.quick_add' | t: title: product.title }}"  >    {{ 'products.add_to_cart' | t }}  </button></article>

Rules:

  • Single tab stop per card (the main link)
  • tabindex="-1" on mouse-only shortcuts (quick add)
  • aria-labelledby on <article> pointing to the title
  • Descriptive alt text on images; empty alt="" if decorative

Carousel

html
<div  role="region"  aria-roledescription="carousel"  aria-label="{{ section.settings.heading | escape }}">  <div class="carousel__controls">    <button      aria-label="{{ 'accessibility.previous_slide' | t }}"      aria-controls="CarouselSlides-{{ section.id }}"    >{% render 'icon-chevron-left' %}</button>    <button      aria-label="{{ 'accessibility.next_slide' | t }}"      aria-controls="CarouselSlides-{{ section.id }}"    >{% render 'icon-chevron-right' %}</button>    <button      aria-label="{{ 'accessibility.pause_slideshow' | t }}"      aria-pressed="false"    >{% render 'icon-pause' %}</button>  </div>
  <div id="CarouselSlides-{{ section.id }}" aria-live="polite">    {% for slide in section.blocks %}      <div        role="group"        aria-roledescription="slide"        aria-label="{{ 'accessibility.slide_n_of_total' | t: n: forloop.index, total: forloop.length }}"        {% unless forloop.first %}aria-hidden="true"{% endunless %}      >        {{ slide.settings.content }}      </div>    {% endfor %}  </div></div>

Rules:

  • Auto-rotation minimum 5 seconds, pause on hover/focus
  • Play/pause button required for auto-rotating carousels
  • aria-live="polite" on slide container (set to "off" during auto-rotation)
  • aria-hidden="true" on inactive slides
  • Each slide: role="group" + aria-roledescription="slide"

Modal

html
<dialog  id="Modal-{{ section.id }}"  aria-labelledby="ModalTitle-{{ section.id }}"  aria-modal="true">  <div class="modal__header">    <h2 id="ModalTitle-{{ section.id }}">{{ title }}</h2>    <button      type="button"      aria-label="{{ 'accessibility.close' | t }}"      on:click="/closeModal"    >{% render 'icon-close' %}</button>  </div>  <div class="modal__content">    <!-- Content -->  </div></dialog>

Rules:

  • Prefer native <dialog> element for modal UI when feasible. showModal() provides native modal behavior, Escape-to-close, and backdrop handling, but role="dialog" remains a valid fallback when native <dialog> is not a good fit.
  • aria-labelledby pointing to the title (not aria-label with a string — aria-labelledby stays in sync when the title changes)
  • Close on Escape key (native with <dialog>)
  • Focus first interactive element on open
  • Return focus to trigger on close

Cart Drawer

Same as modal pattern but with additional:

  • Live region for cart count updates: <span aria-live="polite" aria-atomic="true">
  • Clear "remove item" buttons with aria-label="{{ 'cart.remove_item' | t: title: item.title }}"
  • Quantity inputs with associated labels

Forms

html
<form action="{{ routes.cart_url }}" method="post">  <div class="form__field">    <label for="Email-{{ section.id }}">{{ 'forms.email' | t }}</label>    <input      type="email"      id="Email-{{ section.id }}"      name="email"      required      aria-required="true"      autocomplete="email"      aria-describedby="EmailError-{{ section.id }}"    >    <p      id="EmailError-{{ section.id }}"      class="form__error"      role="alert"      hidden    >{{ 'forms.email_required' | t }}</p>  </div></form>

Rules:

  • Every input has a visible <label> with matching for/id
  • Use <fieldset>/<legend> for radio/checkbox groups
  • Error messages: role="alert" + aria-describedby linking to input
  • aria-invalid="true" on invalid inputs
  • autocomplete attributes on common fields
  • Required fields: required + aria-required="true" + visual indicator

Product Filters

html
<form class="facets">  <div class="facets__group">    <button      type="button"      aria-expanded="false"      aria-controls="FilterColor-{{ section.id }}"    >{{ 'filters.color' | t }}</button>    <fieldset id="FilterColor-{{ section.id }}" hidden>      <legend class="visually-hidden">{{ 'filters.filter_by_color' | t }}</legend>      {% for color in colors %}        <label>          <input type="checkbox" name="filter.color" value="{{ color }}">          {{ color }}        </label>      {% endfor %}    </fieldset>  </div>  <div aria-live="polite" aria-atomic="true">    {{ 'filters.results_count' | t: count: results.size }}  </div></form>

Price Display

html
{% if product.compare_at_price > product.price %}  <div class="price" aria-label="{{ 'products.sale_price_label' | t: sale_price: product.price | money, original_price: product.compare_at_price | money }}">    <s aria-hidden="true">{{ product.compare_at_price | money }}</s>    <span>{{ product.price | money }}</span>  </div>{% else %}  <div class="price" aria-label="{{ 'products.price_label' | t: price: product.price | money }}">    {{ product.price | money }}  </div>{% endif %}
  • Use aria-label on both sale and regular price paths — screen readers need context for any price display
  • aria-hidden="true" on the visual strikethrough to avoid duplicate reading

Accordion

html
<details>  <summary>{{ block.settings.heading }}</summary>  <div class="accordion__content">    {{ block.settings.content }}  </div></details>

Native <details>/<summary> provides keyboard and screen reader support automatically.

Tabs

html
<div role="tablist" aria-label="{{ 'accessibility.product_tabs' | t }}">  {% for tab in tabs %}    <button      role="tab"      id="Tab-{{ tab.id }}"      aria-selected="{% if forloop.first %}true{% else %}false{% endif %}"      aria-controls="Panel-{{ tab.id }}"      tabindex="{% if forloop.first %}0{% else %}-1{% endif %}"    >{{ tab.title }}</button>  {% endfor %}</div>{% for tab in tabs %}  <div    role="tabpanel"    id="Panel-{{ tab.id }}"    aria-labelledby="Tab-{{ tab.id }}"    {% unless forloop.first %}hidden{% endunless %}    tabindex="0"  >{{ tab.content }}</div>{% endfor %}
  • Arrow keys navigate between tabs (left/right)
  • Only active tab has tabindex="0", others -1

Dropdown Navigation

html
<nav aria-label="{{ 'accessibility.main_navigation' | t }}">  <ul role="list">    {% for link in linklists.main-menu.links %}      <li>        {% if link.links.size > 0 %}          <button aria-expanded="false" aria-controls="Submenu-{{ forloop.index }}">            {{ link.title }}          </button>          <ul id="Submenu-{{ forloop.index }}" hidden role="list">            {% for child in link.links %}              <li><a href="{{ child.url }}">{{ child.title }}</a></li>            {% endfor %}          </ul>        {% else %}          <a href="{{ link.url }}">{{ link.title }}</a>        {% endif %}      </li>    {% endfor %}  </ul></nav>

Tooltip

html
<button aria-describedby="Tooltip-{{ block.id }}">  {{ 'labels.info' | t }}</button><div id="Tooltip-{{ block.id }}" role="tooltip" popover>  {{ block.settings.tooltip_text }}</div>

Mobile Accessibility

  • Touch targets: minimum 44x44px, 8px spacing between targets
  • No orientation lock: never restrict to portrait/landscape
  • No hover-only content: everything accessible via tap
  • Use dvh instead of vh for mobile viewport units

Animation & Motion

css
/* Always provide reduced motion */@media (prefers-reduced-motion: reduce) {  *, *::before, *::after {    animation-duration: 0.01ms !important;    animation-iteration-count: 1 !important;    transition-duration: 0.01ms !important;    scroll-behavior: auto !important;  }}
  • No flashing above 3 times per second
  • Auto-playing animations need pause/stop controls
  • Meaningful animations only — don't animate for decoration

Visually Hidden Utility

css
.visually-hidden {  position: absolute;  width: 1px;  height: 1px;  padding: 0;  margin: -1px;  overflow: hidden;  clip: rect(0, 0, 0, 0);  white-space: nowrap;  border: 0;}

Use for screen-reader-only content like labels and descriptions.

Progressive Enhancement

Interactive components should work without JavaScript where possible. Provide <noscript> fallbacks for JS-dependent controls:

html
{%- comment -%} Variant picker with noscript fallback {%- endcomment -%}<variant-picker>  <!-- JS-enhanced radio buttons / swatches here --></variant-picker><noscript>  <select name="id" aria-label="{{ 'products.select_variant' | t }}">    {% for variant in product.variants %}      <option value="{{ variant.id }}" {% unless variant.available %}disabled{% endunless %}>        {{ variant.title }} - {{ variant.price | money }}      </option>    {% endfor %}  </select></noscript>

Live Region for Dynamic Updates

When selections change (variants, filters, cart), announce the change to screen readers:

html
<div aria-live="polite" aria-atomic="true" class="visually-hidden">  {{ 'products.variant_selected' | t: variant: selected_variant.title }}</div>

Use the clear-then-set pattern in JS to ensure announcements fire reliably:

javascript
announce(message) {  this.liveRegion.textContent = '';  requestAnimationFrame(() => {    this.liveRegion.textContent = message;  });}

Color Contrast

ElementMinimum Ratio
Normal text (<18px / <14px bold)4.5:1
Large text (≥18px / ≥14px bold)3:1
UI components & graphics3:1
Focus indicators3:1

Never rely solely on color to convey information — always pair with text, icons, or patterns.

References

  • Component accessibility patterns [blocked]
  • Focus and keyboard patterns [blocked]

來源與署名

來源:Shopify/liquid-skills位於plugins/liquid-skills/skills/liquid-theme-a11y提交ae3e4cc

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架