Black Friday
Skip to documentation content

Aurelia Theme

Verify accessibility, motion and no-JavaScript behavior

Aurelia includes progressive presentation and reduced-motion/no-JavaScript handling, but source support is not a blanket accessibility-conformance claim. Test the actual theme, content, Core/Pro pair and payment provider used by the hotel.

Aurelia includes progressive presentation and reduced-motion/no-JavaScript handling, but source support is not a blanket accessibility-conformance claim. Test the actual theme, content, Core/Pro pair and payment provider used by the hotel.

Inspect core interactions

Use keyboard navigation to review skip links, header/menu controls, language links, room cards, date inputs, Book Now errors and result actions. Check visible focus, meaningful labels, heading order and zoom/long translated text without losing the primary task.

Datepicker and gallery behavior need their own keyboard/focus checks. A visually centered popup is not proof of usable screen-reader output or focus return. Keep native date/form semantics and owner validation fields intact.

Respect motion preferences

Check the operating system/browser reduced-motion setting and verify content is visible without scroll-reveal animation. Parallax/reveals must not be necessary to read a section or reach a booking control. Avoid adding child-theme motion that ignores the parent’s progressive fallback.

Test with JavaScript unavailable

Homepage/secondary content should remain readable and native form submission should preserve validation and the owner’s safe review fallback. Enhanced live quote behavior can differ without scripts; do not suppress server errors to make it appear identical.

Native Stripe and other online-provider payment widgets can require JavaScript. Do not promise a no-JavaScript card checkout from a theme’s fallback. Use the appropriate available flow, such as configured Pay at hotel, when verifying native offline booking.

Print-only controls can be hidden without scripts; ensure the remaining document still communicates the supported booking/payment state. Missing ledger facts are unknown, not zero.

Record bounded evidence

Capture browser/assistive technology, viewport, zoom, input method, exact package versions and the tested surface. Keep contrast, real screen-reader, mobile keyboard and cross-browser checks separate from static markup/CSS inspection.

Historical RC accessibility targets remain historical goals/evidence, not automatic certification of Aurelia 1.3.7 with every extension. See surface regression.

Was this article helpful?

Your feedback helps us improve the documentation.