Lookup for the theme’s behavior and limits. Practical verification steps are in Check accessibility and performance.
The improvements listed here are available on main after v2.1.0
(v2.1.1-dev), not in the v2.1.0 gem or pinned remote theme. Actual results depend
on content, colors, integrations and local overrides. No theme setting or test
score establishes WCAG compliance for a complete site.
Keyboard navigation
Version: the keyboard/focus improvements below and PhotoSwipe require main
after v2.1.0 (v2.1.1-dev); they are not included in the v2.1.0 gem or pin.
| Component | Expected behavior in the development version |
|---|---|
| Skip link | First Tab stop, bypassing repeated navigation. |
| Floating menu | Enter/Space opens; Escape closes and returns focus to its button. Following a link closes it. Closed links are outside the Tab order. |
| Dropdowns | Native buttons; font inherits the surrounding menu styling. |
| Sidebar TOC | Close control and links are keyboard reachable while open. Escape closes and returns focus; the panel is not a modal focus trap. |
| Active TOC section | Reading-position highlight does not move keyboard focus. |
| PhotoSwipe | Arrow-key browsing and Escape closing; focus returns to the image link. Image links remain usable if the viewer cannot load. |
Without JavaScript, the floating menu exposes ordinary navigation links. Interactive integrations can still depend on JavaScript and network access. Custom layouts/widgets only have the semantics and controls their own markup preserves.
Colors, content and motion
The link/focus improvements here require main after v2.1.0 (v2.1.1-dev), not
the v2.1.0 gem or pin. Article links are underlined and keyboard focus is visible.
Custom colors can
weaken those cues or their contrast. Skin selection does not replace a check of
the actual text, links and backgrounds used by a site.
The carousel motion/control improvements in this paragraph require main after
v2.1.0 (v2.1.1-dev), not the v2.1.0 gem or pin. Automatically cycling multi-image
carousels have a play/pause control with an
action-specific accessible name and a plain-symbol fallback when icon assets
are unavailable. Reduced motion starts them paused. Slide/navigation interaction
stops rotation until explicit restart; hovering pauses temporarily. interval=0
disables cycling. Carousel reference.
Video name supplies a descriptive player name, not captions or transcripts.
Mermaid (available on main after v2.1.0, not in the v2.1.0 gem or pin) uses
accTitle and accDescr to describe a diagram; complex content still
needs a prose equivalent. Gallery snippets use generic image descriptions;
individual informative photographs need descriptive custom image markup.
Media tasks cover adding that content.
Long titles and enlarged text are covered by representative checks, not by a promise about every custom layout or widget.
Resource loading
| Integration or resource | Loading behavior or constraint |
|---|---|
| PhotoSwipe | Available on main after v2.1.0, not in the v2.1.0 gem or pin; viewer loads when an image is opened. |
| Deferred YouTube | Preview first, player on activation; loading reference. |
| MathJax | Page opt-in; unnecessary enabled integrations can add resources. |
| Mermaid | Page opt-in; available on main after v2.1.0, not in the v2.1.0 gem or pin. |
| Cactus | Conditional scripts/styles on show_comments: true pages require main after v2.1.0; v2.1.0 loads those resources more broadly. |
| Analytics | Optional; configuring GA and GoatCounter enables both counters. GoatCounter requires main after v2.1.0 (absent from the v2.1.0 gem/pin) and has production requirements. |
Large images, additional fonts/icons and external services affect requests and loading time. Demo measurements do not predict another site’s performance.
PWA and offline behavior
The theme supplies no service worker, offline cache or YAML switch enabling offline support. A favicon/web app manifest alone establishes neither offline operation nor guaranteed app installability. Site-specific capabilities depend on the site’s hosting and any separate implementation.
Comments, embedded videos and the documentation chatbot need network access. A published site must be tested before offline behavior is promised.
Review coverage
Automated checks exercise keyboard navigation, narrow screens and reduced motion on representative layouts/skins. They do not cover every site’s content, customizations, browser or assistive technology. Passing them is not a WCAG certification or a guarantee of loading-performance metrics.
The review record contains technical results and remaining checks. That maintainer evidence is separate from the site-checking procedure.