Accessibility statement

Effective 5 October 2026. Navlin aims to make editorial information usable across devices, browsers, and assistive technologies. We work toward WCAG 2.2 AA practices while recognising that accessibility is continuous. This statement covers the public website and reader communications.

1. Our commitment

We use semantic headings, readable contrast, keyboard-accessible controls, descriptive alternative text, and responsive layouts. We avoid relying on colour alone to convey meaning. Content is written in clear English. Improvements are prioritised by impact.

2. Navigation

Pages use consistent header and footer navigation. Headings provide a document outline. Links describe their destination rather than relying on vague labels. Mobile navigation exposes the same primary destinations.

3. Images and media

Editorial images include descriptive alternative text when they convey information. Decorative treatment is kept separate from essential meaning. If an image is unclear or inaccessible, contact us with its page address. We will consider a text alternative.

4. Forms

Contact fields have visible labels and required fields are identified by browser validation. A successful submission message is presented on the page. Do not include confidential medical details. We can receive accessibility feedback by phone or postal address.

5. Keyboard and focus

Interactive elements should be reachable without a mouse. Focus indicators must remain visible against the page background. If a browser or assistive technology creates a barrier, tell us the device and steps that caused it. We test common desktop and mobile paths.

6. Contrast and typography

Text uses solid, high-contrast colours and generous line height. Headings create visual hierarchy without requiring colour perception. Users may zoom the page without losing essential content. Very old browsers may render typography differently.

7. Known limitations

Some third-party content, PDFs, or legacy material may not fully meet our target. External sites have their own accessibility responsibilities. We record known issues and replace or revise material when practical. A limitation is not a reason to ignore a reported barrier.

8. Feedback process

Contact Navlin at Jalan Sudirman No. 18, Senayan, South Jakarta 12190, Indonesia or +62 21 7123 8945. Describe the page, task, technology, and preferred contact method. We aim to acknowledge feedback within five working days. Sensitive information should not be included.

9. Alternative formats

For a substantial accessibility barrier, ask whether a plain-text explanation or alternative format is available. We assess requests individually and respect reasonable timeframes. The format may omit interactive features while preserving meaning. We will explain any limitation honestly.

10. Review history

This statement was reviewed on 5 October 2026. The previous review was 12 August 2026. We plan a further review during 2027 or after a significant redesign. Updates will carry a visible date.

Testing and support details

Accessibility work covers the public pages, navigation, forms, headings, links, images, contrast, focus treatment, and the way content responds to different viewport sizes. We consider keyboard-only use, browser zoom, mobile screen readers, reduced-motion preferences, and common desktop assistive technology. No automated checker can identify every barrier, so reports from people using the site are an important part of the review process.

Images that communicate meaning are given concise but specific alternative text, while decorative images are kept from interrupting the reading order. A complex chart, table, or image may need a nearby text explanation rather than a longer alt attribute. Video or audio material, if introduced, should include an accessible description or transcript where practical. If a visual cannot be understood with the available alternative, readers can request a text explanation.

Forms are designed so that a person can identify each field, understand an error, and return to the place that needs attention. The success message should remain visible in the page content rather than relying only on colour, sound, or a temporary animation. A reader should not need to disclose a disability or health condition when reporting a technical barrier. The page address, device, browser, assistive technology, and the step that failed are useful details.

Navlin aims to acknowledge accessibility feedback within 7 calendar days and to provide an initial response or proposed next step within 30 calendar days. A small text or labelling correction may be addressed during the next content update, while a structural issue may require testing and a later release. Where an immediate fix is not possible, we will try to provide an accessible alternative or explain the limitation. Feedback is not treated as a complaint about the person who submitted it.

Third-party embeds, browsers, operating systems, and network conditions can affect accessibility beyond the direct control of Navlin. We assess external components before using them and may remove a component that creates an avoidable barrier. External websites have their own accessibility arrangements and contact channels. Readers may still contact Navlin if a link or embedded resource is difficult to use.

Send accessibility feedback to Navlin at Jalan Sudirman No. 18, Senayan, South Jakarta 12190, Indonesia, or call +62 21 7123 8945. The statement was reviewed on 5 October 2026. Future updates will record the effective date and, where material, the area changed so that readers can understand the development of the site.

The accessibility statement covers Navlin’s public pages and the core journeys needed to read an article, use navigation, send a contact request, and understand a policy notice. It does not control the accessibility of a linked provider, operating system, browser, assistive technology, or user-generated file. When a third-party component is essential to a journey, Navlin considers whether a comparable text route is available. A reader may request that route without explaining a personal diagnosis.

Content is structured with headings, meaningful link text, visible focus, readable contrast, and text alternatives for informative images. Tables should include an understandable heading structure, while long documents should offer a logical reading order. Motion and auto-playing media are avoided or limited where practical, and the site should respect a reduced-motion preference when a browser exposes it. These measures support access but cannot guarantee identical behaviour across every device and software combination.

An accessibility report should include the page address, a short description of the barrier, the browser or device used, and whether keyboard navigation or assistive technology was involved. Do not include passwords, identity documents, medical details, or another person’s private information. A screenshot can help explain a visual issue, but it should be checked for unrelated personal information before it is sent. Reports are stored only as long as needed to investigate and track the correction.

Navlin normally acknowledges a report within 7 calendar days and aims to provide an initial response within 30 calendar days. A high-impact barrier may be prioritised for an earlier workaround, while a complex structural change may require design, testing, and a later publication cycle. If a correction is not immediately possible, the response should explain the limitation and suggest an alternative route where one exists. Readers may follow up if the proposed route does not work.

The statement was reviewed on 5 October 2026, following a review on 15 May 2026 of forms, keyboard focus, responsive layout, image alternatives, and policy-page readability. Material updates will record the new date and the affected area. Feedback may be sent to Navlin, Jalan Sudirman No. 18, Senayan, South Jakarta 12190, Indonesia, or by phone at +62 21 7123 8945.