Accessibility
Our approach to making Raftika’s website more accessible, understandable, and usable.
Last updated: 18 August 2026
This statement applies to raftika.com and its public pages. It explains the first-party accessibility practices used on the website and how to report an access barrier.
Raftika aims to make raftika.com usable by the broadest possible audience, including people who use assistive technologies, keyboard navigation, zoom, and different devices. We continually review and improve the website as its content and features change.
We aim to align the website with the Web Content Accessibility Guidelines 2.2 at AA level where practical. These guidelines help make web content more understandable and operable for people with visual, hearing, motor, cognitive, and other access needs.
The website includes a first-item skip link, semantic page landmarks, labelled navigation, visible keyboard focus states, descriptive labels for interactive controls, form validation guidance, accessible names for icon-only links, and responsive layouts designed for different screen sizes. We also review colour contrast, image alternative text, heading structure, and touch-target spacing as part of ongoing maintenance.
Visitors can navigate interactive content using standard keyboard controls, including Tab, Shift+Tab, Enter, and Space where supported by the browser. The website uses semantic HTML and ARIA only where needed to improve the information available to screen readers. Compatibility can vary by browser, operating system, assistive technology, and individual settings.
Despite ongoing effort, some content or browser and assistive-technology combinations may not yet provide an ideal experience. We welcome feedback about barriers and use it to prioritise practical improvements. We do not rely on automated accessibility overlays or third-party code injection to replace first-party accessible design and development.
If you experience an accessibility barrier or need information in a different format, email [email protected]. Please include the page URL, a brief description of the issue, and the assistive technology or browser you were using if you are comfortable sharing it.
