Accessibility statement
Reviewed 1 January 2026. Nectar wants its editorial information to be usable by people with different access needs and devices.
1. Our aim
We work toward clear structure, readable contrast, keyboard access and meaningful alternative text for editorial images.
2. Content structure
Pages use headings, landmarks, lists and tables to help readers navigate with assistive technology.
3. Keyboard access
Links, buttons and form controls are designed to be reachable through keyboard navigation. Focus should remain visible.
4. Images
Images include descriptive alternative text when they communicate information. Decorative choices are kept limited.
5. Colour
Our palette uses strong contrast between deep indigo, white and teal. Information is not intended to rely on colour alone.
6. Motion
The site uses restrained interaction and does not require animation to understand an article. Browser preferences are respected where supported.
7. Forms
Contact fields have visible labels and required states. If a form is difficult to use, email [email protected] instead.
8. Documents
We prefer accessible HTML. If a downloadable document is introduced, we will review its headings, reading order and text alternatives.
9. Known limits
Third-party content, older browsers and some unusual combinations of assistive technology may not behave identically.
10. Feedback
Tell us the page, device, browser and barrier. We will acknowledge accessibility reports and assess practical improvements.
11. Review
The next scheduled review is 31 December 2026, with earlier review after a significant template or technology change.
12. History
1 January 2026, initial statement. 1 June 2026, clarified contact alternatives and downloadable-content commitments.
These practices apply to the public pages, navigation, article content, contact forms and event information published by Nectar. We aim to follow the principles reflected in WCAG 2.2, while recognising that conformance can vary by browser, operating system, content format and assistive technology. A page that is technically structured can still present a practical barrier, so reports from readers are important.
When a problem is reported, include the page address, the action you were trying to complete, the device and browser, and whether you use a screen reader, keyboard navigation, magnification or another tool. Do not include medical information or other sensitive details. We aim to acknowledge a report within 10 business days, assess a straightforward content issue within 30 calendar days and provide an update when a technical fix requires more time.
Priority is given to barriers that prevent access to core information, form submission or navigation. Temporary alternatives may include a plain-text response by email or a differently formatted copy of a specific article. Accessibility requests are handled by the editorial team and are not used for marketing. Correspondence is retained under the privacy policy and normally removed after 24 months from the last meaningful exchange.
The statement was reviewed on 1 January 2026 and remains scheduled for review on 31 December 2026, with an earlier review after a major template, browser or content-system change. Feedback may be sent to [email protected] or to Jalan Pangeran Diponegoro No. 88, Menteng, Jakarta Pusat 10310, Indonesia.
These practices apply to public pages, navigation, forms, article images, event details and the way information is presented on common browsers and devices. We use WCAG 2.2 principles as a practical reference, while recognising that results can vary across operating systems, browser versions and assistive technologies. A technically structured page can still create a real barrier, so reader reports are part of the review process.
When reporting a problem, provide the page address, the action you attempted, device and browser, and the assistive technology involved if relevant. Do not include medical or other unnecessary sensitive information. We aim to acknowledge a report within 10 business days, assess a straightforward content problem within 30 calendar days and provide a progress update where a technical correction needs more time.
Priority is given to barriers that prevent access to core articles, navigation or contact submission. A temporary alternative may include a plain-text response, a corrected description or a differently formatted copy of a specific page. Accessibility correspondence is handled by the editorial team and normally retained for up to 24 months after the last meaningful exchange.
The statement was reviewed on 1 January 2026 and is scheduled for review on 31 December 2026, or sooner after a significant template or content-system change. Feedback may be sent to [email protected] or Jalan Pangeran Diponegoro No. 88, Menteng, Jakarta Pusat 10310, Indonesia. We record practical improvements without publishing personal details about the person who reported them.