Accessibility statement
Reviewed 12 October 2026. Helian aims to make its editorial information usable by people with different abilities, devices, languages and reading preferences.
This statement covers the public pages, navigation, images, forms and policy content available from the Helian website. We use the Web Content Accessibility Guidelines as a practical reference, while recognizing that conformance can vary by browser, assistive technology and future content.
1. Our commitment
We work toward clear structure, sufficient contrast, descriptive image alternatives, readable type and keyboard access. Accessibility is treated as an ongoing editorial and technical responsibility rather than a one-time badge.
Editors consider accessibility before publishing a page and during routine review. We aim to fix barriers in a reasonable order, beginning with problems that prevent access to navigation, essential information or contact routes. A technical limitation is not a reason to dismiss a useful report from a visitor.
2. Page structure
Pages use headings, landmarks, lists and tables where those patterns help comprehension. Headings are chosen for meaning rather than visual size. We review long articles for logical order and avoid using color as the only way to communicate information.
Links are written to indicate their destination, sections follow a predictable order and tables are reserved for relationships that benefit from rows and columns. We aim to keep repeated navigation consistent. Readers can report a heading, label or reading-order problem with the page title and a short description.
3. Images and alternatives
Editorial images include descriptive alternative text when they convey information. Decorative visuals are kept out of the reading path where appropriate. If an image is unclear or an alternative is missing, tell us the page title and what information you need.
Alternative text describes relevant subject, setting and action without adding claims that the image cannot establish. A complex chart may need a nearby text summary rather than a long attribute alone. We do not place essential instructions only inside an image.
4. Keyboard use
Links and form controls are intended to be reachable with a keyboard and to show a visible focus state. We test common navigation paths, although browser extensions, assistive technologies and future updates can produce differences.
Users should be able to move through the header, content and footer without a pointer. A form should expose labels, instructions and a clear confirmation after submission. If focus becomes trapped or disappears, include the browser, device and page when reporting it.
5. Contrast and text
Our palette uses dark text on light paper and high-contrast text on dark bands. Text can be resized through browser tools. We avoid dense all-caps presentation and aim for comfortable line lengths across mobile and desktop screens.
Some pages contain photographs, tables or shaded callouts, so we review text against its immediate background rather than relying on a general palette. Zooming should not remove meaningful content. We welcome reports of low contrast, clipped text or overlapping controls.
6. Motion and interaction
Helian uses minimal motion and does not depend on animation to reveal an article. Cookie controls and contact confirmation are available as ordinary content, not only as a timed visual effect.
Where an interaction is introduced, it should have a usable static state and a clear name. We avoid auto-playing audio and unexpected movement. If a component behaves differently with reduced-motion settings or a screen reader, please tell us what occurred.
7. Feedback and revisions
Send accessibility feedback to Jalan Thamrin No. 88, Menteng, Jakarta Pusat, DKI Jakarta 10310, Indonesia, or call +62 21 7891 035. We normally acknowledge reports within 7 business days and aim to provide an update within 30 calendar days.
Revision history: 12 October 2026, accessibility statement reviewed and published. We will record material updates with a date and brief explanation. Feedback can also identify a preferred accessible format for information that is difficult to use online.
Keyboard users should be able to move through links, form controls and the cookie notice in a visible order. We aim to provide a clear focus indicator and avoid controls that can be used only with a pointer. If a third-party embed or browser feature behaves differently, tell us the page, device, browser and the step where access becomes difficult.
Images that carry editorial meaning receive concise, specific alternative text; decorative imagery is not given a distracting description. Videos or interactive material, if introduced, should include a meaningful title and a text alternative where practical. Readers can request a transcript, accessible document or equivalent explanation when a format creates a barrier.
Accessibility reports may be sent to Jalan Thamrin No. 88, Menteng, Jakarta Pusat, DKI Jakarta 10310, Indonesia, or by phone at +62 21 7891 035. We aim to acknowledge a report within 7 calendar days, assess its priority within 15 calendar days and provide a progress update within 30 calendar days. A report is easier to act on when it includes the page address and does not include unnecessary personal information.
Helian may use hosting, form and analytics providers whose interfaces or infrastructure are outside Indonesia. We ask service providers to support accessible delivery and share only the information necessary to investigate a report. No visitor is required to identify a disability in order to request an adjustment.
Revision record: this statement was reviewed on 12 October 2026. We will record material changes by date and may update the reference standard as browser technology, WCAG guidance and reader needs develop.
Keyboard access is considered for links, form controls, navigation and the cookie notice. Focus should remain visible, headings should follow a meaningful order, and interactive controls should have names that make sense when read without surrounding visual context. If a third-party element behaves differently, readers can report the page address, browser, device and step where the barrier occurs.
Images with editorial meaning use descriptive alternative text, while decorative imagery is not given text that distracts from the article. We aim to keep contrast, spacing and line length readable across common screen sizes. A reader may request a text alternative, transcript or accessible copy when the published format creates a practical barrier.
Accessibility reports can be sent to [email protected], Jalan Thamrin No. 88, Menteng, Jakarta Pusat, DKI Jakarta 10310, Indonesia, or +62 21 7891 035. We aim to acknowledge reports within 7 calendar days, assess priority within 15 calendar days and provide an update within 30 calendar days.
Helian may use hosting, form delivery and measurement services whose infrastructure is outside Indonesia. We share only information needed to investigate a report and do not require a reader to identify a disability. A request for an adjustment is handled as an access request, not as a test of eligibility.
This statement was reviewed on 12 October 2026. Material updates will carry a new date and may refer to changes in browser technology, WCAG guidance or the design of a particular page.