Skip to documentation content

Aurelia Theme

Verify accessibility, motion and no-JavaScript behavior

Run Aurelia's WCAG 2.2 AA, reduced-motion, keyboard, zoom and no-JavaScript checks across core booking surfaces.

Aurelia targets WCAG 2.2 AA on the homepage, Rooms, Search Availability, Room Detail, Book Now, Booking Confirmation and customer surfaces. Semantic landmarks, one main landmark, a skip link, visible focus, sufficient contrast, 44px interaction targets and meaningful names are release requirements.

Regression checklist

  1. Navigate with keyboard only. The skip link reaches the main landmark, menus can open and close, date controls expose their labels, and focus never gets trapped in an optional panel.
  2. Use a screen reader to verify names, roles, states, validation messages and live regions supplied by Hotel Booking. Do not hide payment or policy errors.
  3. Set reduced motion. Scroll reveals, Hero depth and gallery transitions must become instant or disappear without changing content order.
  4. Zoom to 200% and 400% and test 320px width. Text reflows without horizontal scrolling, clipped buttons or a datepicker that hides its fields.
  5. Disable JavaScript. Navigation, room catalogue, Room Detail and Pay at hotel booking remain usable. A JavaScript-required gateway fails explicitly and leaves booking and payment state recoverable.

Treat a missing label, invisible focus ring, inaccessible datepicker or incorrect payment announcement as release-blocking. Fix theme markup and CSS through the public contract; do not alter Core validation or gateway logic.

Next: deliver performance and responsive images.

Was this article helpful?

Your feedback helps us improve the documentation.