Accessibility statement

Reviewed 5 October 2026. Halcyon aims to make its English-language editorial content usable across common browsers, screen readers, keyboards, and mobile devices.

This statement covers the public Halcyon website, article pages, forms, navigation, images, and policy pages. It describes our current approach rather than claiming that every page is free of barriers. Third-party websites linked from Halcyon may follow different accessibility practices and are outside our direct control.

Accessibility feedback is reviewed by the editorial and technical teams, with urgent reading barriers assessed first and routine improvements recorded for later maintenance. We aim to acknowledge a report within 10 business days and provide a practical alternative or status update within 30 days where the issue requires investigation. Requests may be made by phone at +62 857 2341 9876 or by post to Jalan Mawar No. 45, Kebayoran Baru, Jakarta Selatan, Jakarta 12160, Indonesia. Readers may describe a preferred format, and no medical or identity information is needed to report a barrier.

1. Access and feedback

We use semantic headings, visible links, meaningful form labels, responsive layouts, descriptive image alternatives, and high-contrast text. We avoid using colour alone to communicate meaning and provide a clear focus style for keyboard users. Some older content, embedded services, or third-party pages may not meet every expectation immediately. We review reported barriers in the context of their effect on reading and navigation.

Examples include keeping heading levels in a logical order, providing text alternatives that describe the purpose of an informative image, allowing links to be reached without a mouse, and avoiding instructions that depend only on colour. Tables should retain headers and a meaningful reading order. Where a visual feature cannot be made equivalent quickly, we consider a text explanation or alternate route to the same information.

To report a problem, contact Halcyon at Jalan Mawar No. 45, Kebayoran Baru, Jakarta Selatan, Jakarta 12160, Indonesia, or call +62 857 2341 9876. Include the page address, the task you were attempting, and your preferred response format if you can. We aim to acknowledge requests within 10 business days and provide an accessible alternative while a technical fix is considered. No reader is required to disclose a diagnosis to request help.

• Useful reports identify the device, browser, assistive technology, and exact page where possible.
• A screenshot is optional; do not include personal medical information in an attachment.
• We prioritize barriers that prevent reading, navigation, form completion, or understanding of essential notices.
• Requests for plain text, a different file format, or a more direct explanation can be made without a formal complaint.

Accessibility feedback is logged with the page, date, issue description, and action taken. We normally keep the operational record for up to 24 months, then remove unnecessary personal details. Technical logs created while investigating a problem are normally retained for up to 90 days. We share a report only with the people needed to reproduce or address the barrier.

Halcyon reviews new templates before publication and samples older pages during routine maintenance. A correction may be released immediately for a severe reading or navigation barrier, while a larger structural change may be scheduled with a target date. We explain the available interim route rather than asking a reader to wait without an alternative.

2. Access and feedback

We use semantic headings, visible links, meaningful form labels, responsive layouts, descriptive image alternatives, and high-contrast text. We avoid using colour alone to communicate meaning and provide a clear focus style for keyboard users. Some older content, embedded services, or third-party pages may not meet every expectation immediately. We review reported barriers in the context of their effect on reading and navigation.

Examples include keeping heading levels in a logical order, providing text alternatives that describe the purpose of an informative image, allowing links to be reached without a mouse, and avoiding instructions that depend only on colour. Tables should retain headers and a meaningful reading order. Where a visual feature cannot be made equivalent quickly, we consider a text explanation or alternate route to the same information.

To report a problem, contact Halcyon at Jalan Mawar No. 45, Kebayoran Baru, Jakarta Selatan, Jakarta 12160, Indonesia, or call +62 857 2341 9876. Include the page address, the task you were attempting, and your preferred response format if you can. We aim to acknowledge requests within 10 business days and provide an accessible alternative while a technical fix is considered. No reader is required to disclose a diagnosis to request help.

• Useful reports identify the device, browser, assistive technology, and exact page where possible.
• A screenshot is optional; do not include personal medical information in an attachment.
• We prioritize barriers that prevent reading, navigation, form completion, or understanding of essential notices.
• Requests for plain text, a different file format, or a more direct explanation can be made without a formal complaint.

Accessibility feedback is logged with the page, date, issue description, and action taken. We normally keep the operational record for up to 24 months, then remove unnecessary personal details. Technical logs created while investigating a problem are normally retained for up to 90 days. We share a report only with the people needed to reproduce or address the barrier.

Halcyon reviews new templates before publication and samples older pages during routine maintenance. A correction may be released immediately for a severe reading or navigation barrier, while a larger structural change may be scheduled with a target date. We explain the available interim route rather than asking a reader to wait without an alternative.

3. Access and feedback

We use semantic headings, visible links, meaningful form labels, responsive layouts, descriptive image alternatives, and high-contrast text. We avoid using colour alone to communicate meaning and provide a clear focus style for keyboard users. Some older content, embedded services, or third-party pages may not meet every expectation immediately. We review reported barriers in the context of their effect on reading and navigation.

Examples include keeping heading levels in a logical order, providing text alternatives that describe the purpose of an informative image, allowing links to be reached without a mouse, and avoiding instructions that depend only on colour. Tables should retain headers and a meaningful reading order. Where a visual feature cannot be made equivalent quickly, we consider a text explanation or alternate route to the same information.

To report a problem, contact Halcyon at Jalan Mawar No. 45, Kebayoran Baru, Jakarta Selatan, Jakarta 12160, Indonesia, or call +62 857 2341 9876. Include the page address, the task you were attempting, and your preferred response format if you can. We aim to acknowledge requests within 10 business days and provide an accessible alternative while a technical fix is considered. No reader is required to disclose a diagnosis to request help.

• Useful reports identify the device, browser, assistive technology, and exact page where possible.
• A screenshot is optional; do not include personal medical information in an attachment.
• We prioritize barriers that prevent reading, navigation, form completion, or understanding of essential notices.
• Requests for plain text, a different file format, or a more direct explanation can be made without a formal complaint.

Accessibility feedback is logged with the page, date, issue description, and action taken. We normally keep the operational record for up to 24 months, then remove unnecessary personal details. Technical logs created while investigating a problem are normally retained for up to 90 days. We share a report only with the people needed to reproduce or address the barrier.

Halcyon reviews new templates before publication and samples older pages during routine maintenance. A correction may be released immediately for a severe reading or navigation barrier, while a larger structural change may be scheduled with a target date. We explain the available interim route rather than asking a reader to wait without an alternative.

4. Access and feedback

We use semantic headings, visible links, meaningful form labels, responsive layouts, descriptive image alternatives, and high-contrast text. We avoid using colour alone to communicate meaning and provide a clear focus style for keyboard users. Some older content, embedded services, or third-party pages may not meet every expectation immediately. We review reported barriers in the context of their effect on reading and navigation.

Examples include keeping heading levels in a logical order, providing text alternatives that describe the purpose of an informative image, allowing links to be reached without a mouse, and avoiding instructions that depend only on colour. Tables should retain headers and a meaningful reading order. Where a visual feature cannot be made equivalent quickly, we consider a text explanation or alternate route to the same information.

To report a problem, contact Halcyon at Jalan Mawar No. 45, Kebayoran Baru, Jakarta Selatan, Jakarta 12160, Indonesia, or call +62 857 2341 9876. Include the page address, the task you were attempting, and your preferred response format if you can. We aim to acknowledge requests within 10 business days and provide an accessible alternative while a technical fix is considered. No reader is required to disclose a diagnosis to request help.

• Useful reports identify the device, browser, assistive technology, and exact page where possible.
• A screenshot is optional; do not include personal medical information in an attachment.
• We prioritize barriers that prevent reading, navigation, form completion, or understanding of essential notices.
• Requests for plain text, a different file format, or a more direct explanation can be made without a formal complaint.

Accessibility feedback is logged with the page, date, issue description, and action taken. We normally keep the operational record for up to 24 months, then remove unnecessary personal details. Technical logs created while investigating a problem are normally retained for up to 90 days. We share a report only with the people needed to reproduce or address the barrier.

Halcyon reviews new templates before publication and samples older pages during routine maintenance. A correction may be released immediately for a severe reading or navigation barrier, while a larger structural change may be scheduled with a target date. We explain the available interim route rather than asking a reader to wait without an alternative.

5. Access and feedback

We use semantic headings, visible links, meaningful form labels, responsive layouts, descriptive image alternatives, and high-contrast text. We avoid using colour alone to communicate meaning and provide a clear focus style for keyboard users. Some older content, embedded services, or third-party pages may not meet every expectation immediately. We review reported barriers in the context of their effect on reading and navigation.

Examples include keeping heading levels in a logical order, providing text alternatives that describe the purpose of an informative image, allowing links to be reached without a mouse, and avoiding instructions that depend only on colour. Tables should retain headers and a meaningful reading order. Where a visual feature cannot be made equivalent quickly, we consider a text explanation or alternate route to the same information.

To report a problem, contact Halcyon at Jalan Mawar No. 45, Kebayoran Baru, Jakarta Selatan, Jakarta 12160, Indonesia, or call +62 857 2341 9876. Include the page address, the task you were attempting, and your preferred response format if you can. We aim to acknowledge requests within 10 business days and provide an accessible alternative while a technical fix is considered. No reader is required to disclose a diagnosis to request help.

• Useful reports identify the device, browser, assistive technology, and exact page where possible.
• A screenshot is optional; do not include personal medical information in an attachment.
• We prioritize barriers that prevent reading, navigation, form completion, or understanding of essential notices.
• Requests for plain text, a different file format, or a more direct explanation can be made without a formal complaint.

Accessibility feedback is logged with the page, date, issue description, and action taken. We normally keep the operational record for up to 24 months, then remove unnecessary personal details. Technical logs created while investigating a problem are normally retained for up to 90 days. We share a report only with the people needed to reproduce or address the barrier.

Halcyon reviews new templates before publication and samples older pages during routine maintenance. A correction may be released immediately for a severe reading or navigation barrier, while a larger structural change may be scheduled with a target date. We explain the available interim route rather than asking a reader to wait without an alternative.

6. Access and feedback

We use semantic headings, visible links, meaningful form labels, responsive layouts, descriptive image alternatives, and high-contrast text. We avoid using colour alone to communicate meaning and provide a clear focus style for keyboard users. Some older content, embedded services, or third-party pages may not meet every expectation immediately. We review reported barriers in the context of their effect on reading and navigation.

Examples include keeping heading levels in a logical order, providing text alternatives that describe the purpose of an informative image, allowing links to be reached without a mouse, and avoiding instructions that depend only on colour. Tables should retain headers and a meaningful reading order. Where a visual feature cannot be made equivalent quickly, we consider a text explanation or alternate route to the same information.

To report a problem, contact Halcyon at Jalan Mawar No. 45, Kebayoran Baru, Jakarta Selatan, Jakarta 12160, Indonesia, or call +62 857 2341 9876. Include the page address, the task you were attempting, and your preferred response format if you can. We aim to acknowledge requests within 10 business days and provide an accessible alternative while a technical fix is considered. No reader is required to disclose a diagnosis to request help.

• Useful reports identify the device, browser, assistive technology, and exact page where possible.
• A screenshot is optional; do not include personal medical information in an attachment.
• We prioritize barriers that prevent reading, navigation, form completion, or understanding of essential notices.
• Requests for plain text, a different file format, or a more direct explanation can be made without a formal complaint.

Accessibility feedback is logged with the page, date, issue description, and action taken. We normally keep the operational record for up to 24 months, then remove unnecessary personal details. Technical logs created while investigating a problem are normally retained for up to 90 days. We share a report only with the people needed to reproduce or address the barrier.

Halcyon reviews new templates before publication and samples older pages during routine maintenance. A correction may be released immediately for a severe reading or navigation barrier, while a larger structural change may be scheduled with a target date. We explain the available interim route rather than asking a reader to wait without an alternative.

7. Access and feedback

We use semantic headings, visible links, meaningful form labels, responsive layouts, descriptive image alternatives, and high-contrast text. We avoid using colour alone to communicate meaning and provide a clear focus style for keyboard users. Some older content, embedded services, or third-party pages may not meet every expectation immediately. We review reported barriers in the context of their effect on reading and navigation.

Examples include keeping heading levels in a logical order, providing text alternatives that describe the purpose of an informative image, allowing links to be reached without a mouse, and avoiding instructions that depend only on colour. Tables should retain headers and a meaningful reading order. Where a visual feature cannot be made equivalent quickly, we consider a text explanation or alternate route to the same information.

To report a problem, contact Halcyon at Jalan Mawar No. 45, Kebayoran Baru, Jakarta Selatan, Jakarta 12160, Indonesia, or call +62 857 2341 9876. Include the page address, the task you were attempting, and your preferred response format if you can. We aim to acknowledge requests within 10 business days and provide an accessible alternative while a technical fix is considered. No reader is required to disclose a diagnosis to request help.

• Useful reports identify the device, browser, assistive technology, and exact page where possible.
• A screenshot is optional; do not include personal medical information in an attachment.
• We prioritize barriers that prevent reading, navigation, form completion, or understanding of essential notices.
• Requests for plain text, a different file format, or a more direct explanation can be made without a formal complaint.

Accessibility feedback is logged with the page, date, issue description, and action taken. We normally keep the operational record for up to 24 months, then remove unnecessary personal details. Technical logs created while investigating a problem are normally retained for up to 90 days. We share a report only with the people needed to reproduce or address the barrier.

Halcyon reviews new templates before publication and samples older pages during routine maintenance. A correction may be released immediately for a severe reading or navigation barrier, while a larger structural change may be scheduled with a target date. We explain the available interim route rather than asking a reader to wait without an alternative.

8. Access and feedback

We use semantic headings, visible links, meaningful form labels, responsive layouts, descriptive image alternatives, and high-contrast text. We avoid using colour alone to communicate meaning and provide a clear focus style for keyboard users. Some older content, embedded services, or third-party pages may not meet every expectation immediately. We review reported barriers in the context of their effect on reading and navigation.

Examples include keeping heading levels in a logical order, providing text alternatives that describe the purpose of an informative image, allowing links to be reached without a mouse, and avoiding instructions that depend only on colour. Tables should retain headers and a meaningful reading order. Where a visual feature cannot be made equivalent quickly, we consider a text explanation or alternate route to the same information.

To report a problem, contact Halcyon at Jalan Mawar No. 45, Kebayoran Baru, Jakarta Selatan, Jakarta 12160, Indonesia, or call +62 857 2341 9876. Include the page address, the task you were attempting, and your preferred response format if you can. We aim to acknowledge requests within 10 business days and provide an accessible alternative while a technical fix is considered. No reader is required to disclose a diagnosis to request help.

• Useful reports identify the device, browser, assistive technology, and exact page where possible.
• A screenshot is optional; do not include personal medical information in an attachment.
• We prioritize barriers that prevent reading, navigation, form completion, or understanding of essential notices.
• Requests for plain text, a different file format, or a more direct explanation can be made without a formal complaint.

Accessibility feedback is logged with the page, date, issue description, and action taken. We normally keep the operational record for up to 24 months, then remove unnecessary personal details. Technical logs created while investigating a problem are normally retained for up to 90 days. We share a report only with the people needed to reproduce or address the barrier.

Halcyon reviews new templates before publication and samples older pages during routine maintenance. A correction may be released immediately for a severe reading or navigation barrier, while a larger structural change may be scheduled with a target date. We explain the available interim route rather than asking a reader to wait without an alternative.

9. Access and feedback

We use semantic headings, visible links, meaningful form labels, responsive layouts, descriptive image alternatives, and high-contrast text. We avoid using colour alone to communicate meaning and provide a clear focus style for keyboard users. Some older content, embedded services, or third-party pages may not meet every expectation immediately. We review reported barriers in the context of their effect on reading and navigation.

Examples include keeping heading levels in a logical order, providing text alternatives that describe the purpose of an informative image, allowing links to be reached without a mouse, and avoiding instructions that depend only on colour. Tables should retain headers and a meaningful reading order. Where a visual feature cannot be made equivalent quickly, we consider a text explanation or alternate route to the same information.

To report a problem, contact Halcyon at Jalan Mawar No. 45, Kebayoran Baru, Jakarta Selatan, Jakarta 12160, Indonesia, or call +62 857 2341 9876. Include the page address, the task you were attempting, and your preferred response format if you can. We aim to acknowledge requests within 10 business days and provide an accessible alternative while a technical fix is considered. No reader is required to disclose a diagnosis to request help.

• Useful reports identify the device, browser, assistive technology, and exact page where possible.
• A screenshot is optional; do not include personal medical information in an attachment.
• We prioritize barriers that prevent reading, navigation, form completion, or understanding of essential notices.
• Requests for plain text, a different file format, or a more direct explanation can be made without a formal complaint.

Accessibility feedback is logged with the page, date, issue description, and action taken. We normally keep the operational record for up to 24 months, then remove unnecessary personal details. Technical logs created while investigating a problem are normally retained for up to 90 days. We share a report only with the people needed to reproduce or address the barrier.

Halcyon reviews new templates before publication and samples older pages during routine maintenance. A correction may be released immediately for a severe reading or navigation barrier, while a larger structural change may be scheduled with a target date. We explain the available interim route rather than asking a reader to wait without an alternative.

10. Access and feedback

We use semantic headings, visible links, meaningful form labels, responsive layouts, descriptive image alternatives, and high-contrast text. We avoid using colour alone to communicate meaning and provide a clear focus style for keyboard users. Some older content, embedded services, or third-party pages may not meet every expectation immediately. We review reported barriers in the context of their effect on reading and navigation.

Examples include keeping heading levels in a logical order, providing text alternatives that describe the purpose of an informative image, allowing links to be reached without a mouse, and avoiding instructions that depend only on colour. Tables should retain headers and a meaningful reading order. Where a visual feature cannot be made equivalent quickly, we consider a text explanation or alternate route to the same information.

To report a problem, contact Halcyon at Jalan Mawar No. 45, Kebayoran Baru, Jakarta Selatan, Jakarta 12160, Indonesia, or call +62 857 2341 9876. Include the page address, the task you were attempting, and your preferred response format if you can. We aim to acknowledge requests within 10 business days and provide an accessible alternative while a technical fix is considered. No reader is required to disclose a diagnosis to request help.

• Useful reports identify the device, browser, assistive technology, and exact page where possible.
• A screenshot is optional; do not include personal medical information in an attachment.
• We prioritize barriers that prevent reading, navigation, form completion, or understanding of essential notices.
• Requests for plain text, a different file format, or a more direct explanation can be made without a formal complaint.

Accessibility feedback is logged with the page, date, issue description, and action taken. We normally keep the operational record for up to 24 months, then remove unnecessary personal details. Technical logs created while investigating a problem are normally retained for up to 90 days. We share a report only with the people needed to reproduce or address the barrier.

Halcyon reviews new templates before publication and samples older pages during routine maintenance. A correction may be released immediately for a severe reading or navigation barrier, while a larger structural change may be scheduled with a target date. We explain the available interim route rather than asking a reader to wait without an alternative.

Review date

This statement was updated on 5 October 2026 and will be revisited as the site changes.

The October 2026 update clarifies coverage, reporting details, privacy limits, and review priorities. A future change log will record the date, affected area, and whether the change concerns content, navigation, contrast, forms, or third-party material. The next planned review is October 2027, or sooner if a significant site feature is introduced.