Accessibility

BaliGenie is being built so that trip-planning information can be used by as many people as reasonably possible. Accessibility is a practical quality requirement covering structure, keyboard use, contrast, text alternatives, forms and the behaviour of the theme and plugins.

Accessibility commitment

The project intends to use clear headings, readable text, descriptive link labels and meaningful page structure rather than relying only on visual styling. Images that convey information should have useful alternative text, while decorative images should not create noise for assistive technology.

Interactive features should be usable without requiring precise mouse movement where the underlying theme and plugins allow it. Forms should have understandable labels and errors. Colour should not be the only way important information is communicated.

BaliGenie uses WordPress with theme and plugin components, so some accessibility behaviour depends on templates and third-party components as well as editorial content. That is why rendered front-end testing remains part of production quality assurance.

Known limitations

The site is still in a pre-launch build. The current homepage and navigation are live, while several dynamic directory and account interfaces still require ongoing browser-level review. BaliGenie therefore does not claim full conformance with a specific accessibility standard today.

Maps, sliders, booking or directory widgets, third-party embeds and complex filters can create accessibility problems even when the surrounding page is well structured. Those components should be tested rather than assumed compliant because they come from a commercial theme.

Feedback route

If you encounter a barrier, tell us what page you were using, what you were trying to do, what device or assistive technology you were using if relevant, and what happened. That information makes the issue easier to reproduce and fix.

Use the Contact page for accessibility feedback. A report about a content error can also follow the Corrections Policy.

Contact

BaliGenie will update this statement after the final responsive and accessibility review. Until then, the honest position is that accessibility is an active build requirement with known work still pending, not a finished certification.