Accessibility statement
Reviewed 1 October 2026. Ijanos aims to make English editorial content readable and usable across current phones, tablets and desktop browsers. We use semantic headings, visible focus styles, descriptive image alternatives and responsive layouts. Accessibility is an ongoing practice rather than a claim of perfection.
1. Structure
Pages use headings, navigation, main content and footer landmarks. Links describe their destination and forms identify required fields. Tables are used only when comparison benefits from rows and columns. We review structure during each content update.
2. Visual design
The palette uses dark charcoal text and deep teal accents with strong contrast. Text can reflow on narrow screens and spacing is designed for comfortable reading. Images have language-appropriate descriptions. Users should be able to zoom without losing essential content.
3. Keyboard use
Interactive controls are native links, buttons or form fields. The navigation menu can be reached by keyboard. Focus should remain visible during movement through a page. Report any focus trap or unreachable control to the contact desk.
4. Motion
The publication avoids decorative animation that could distract from reading. The cookie notice can be dismissed directly. No video is required to understand an article. Future interactive features will be reviewed for reduced-motion preferences.
5. Language
The current site language is English. Technical terms are explained in context and the glossary provides additional support. We welcome feedback from readers using assistive technology in Indonesia. Translation suggestions are considered editorially.
6. Documents
We prefer HTML content so it can adapt to user agents. If a downloadable document is introduced, we will identify its format and accessibility status. Readers may request an accessible alternative. Requests are retained only as needed to respond.
7. Feedback
Contact Jalan Merdeka Timur No. 11, Gambir, Central Jakarta 10110, Indonesia, or +62 818 2349 7561. Describe the page, device, browser and barrier without sharing sensitive information. We aim to acknowledge a report within 30 days. Severe barriers are prioritised.
8. Testing
We combine manual review, responsive checks and semantic inspection. Automated tools can miss meaningful problems, so reader reports matter. A change may require further testing after publication. The latest formal review occurred 1 October 2026.
9. Third parties
External websites may not meet the same standard. Their accessibility is outside Ijanos control. We provide context before sending visitors away when practical. Please report broken or inaccessible links.
10. Change record
1 October 2026: statement reviewed and contact route confirmed. Future improvements will be listed with dates. Accessibility remains part of the editorial quality process. Nothing here limits rights available under applicable law.
Ongoing implementation
Accessibility checks include heading order, link purpose, keyboard reachability, focus visibility, text scaling and the relationship between labels and controls. We also check that a page remains understandable when images fail to load or when a visitor uses a narrow screen. These checks are practical quality measures and do not represent a claim that every browser or assistive technology will behave identically.
Images used in editorial content receive concise descriptions of the meaningful visible scene. Decorative elements should not compete with the reading order, and image alternatives are reviewed when a photograph could be misunderstood. A chart or table should include surrounding text that explains its purpose instead of relying on colour alone.
Visitors may encounter a third-party document, embedded player or external page with different accessibility features. We identify that boundary where practical and prefer HTML alternatives for essential information. If an external resource is difficult to use, the contact desk can provide a plain-text summary of the relevant Ijanos material when it is reasonable to do so.
Feedback should include the page address, the barrier encountered, the device or assistive technology involved if known, and a preferred reply route. Do not include medical details or identity documents. We aim to acknowledge accessibility feedback within seven calendar days and assess a straightforward correction within 30 days; complex changes may require a later target that we explain in reply.
Requests can be sent to Jalan Merdeka Timur No. 11, Gambir, Central Jakarta 10110, Indonesia, or +62 818 2349 7561. The statement was reviewed on 1 October 2026. Future revisions will record the review date and the accessibility area affected.
Accessibility checks also consider heading order, link purpose, keyboard reachability, focus visibility, text scaling, reflow and whether information remains understandable when an image fails to load. Colour is not intended to be the only method of communicating a distinction. A table should retain meaningful row and column relationships when enlarged. These checks are reviewed during material content updates, although browser and assistive technology behaviour can vary.
Image alternatives describe the meaningful visible scene rather than adding promotional language. Decorative elements should not interrupt the reading order, and downloadable or embedded third-party material may have separate limitations. Where practical, the contact desk can provide a plain-text explanation of essential Ijanos content. Visitors should not send medical details or identity documents when reporting a barrier.
Feedback should identify the page address, the barrier, the device or assistive technology involved if known and a safe reply route. We aim to acknowledge feedback within seven calendar days and assess a straightforward correction within 30 days. Complex changes may require a later target, which we will explain in reply. Requests can be sent to Jalan Merdeka Timur No. 11, Gambir, Central Jakarta 10110, Indonesia, or +62 818 2349 7561; this statement was reviewed on 1 October 2026.