Access / Updated 14 October 2026
Accessibility statement
Derive aims to make long-form reading practical for as many people as possible.
1. Our aim
We design clear structure, readable contrast, keyboard-friendly controls, and descriptive alternative text.
2. Content structure
Headings are used to organize topics. Lists and tables are introduced with context so readers can choose how to navigate.
3. Keyboard use
Navigation and form controls are intended to be reachable without a pointer. Focus should remain visible during movement through a page.
4. Contrast
Text and backgrounds use a restrained palette with strong contrast in body and footer areas.
5. Images
Editorial images include descriptive alternative text that conveys the visible subject and setting.
6. Motion
The site uses no autoplay video or required animation. Reduced-motion preferences are respected where motion is introduced.
7. Forms
Labels identify fields and the success message confirms a submitted editorial message.
8. Limitations
Some older content or third-party links may not meet every current expectation. We prioritize meaningful corrections.
9. Feedback
Tell us the page, barrier, device, and preferred contact method. We aim to acknowledge requests within 10 working days.
10. Review
This statement was reviewed 14 October 2026 and will be reconsidered each editorial year.
11. Contact
Write through contact.php or to 120 Cihampelas Street, Bandung, West Java 40131, Indonesia.
Our accessibility work covers the public pages, article templates, navigation, forms, and policy documents available on the site. We test common keyboard paths, readable focus states, heading order, link clarity, image descriptions, and responsive layouts as part of ordinary editorial maintenance. Some third-party content may follow a different interface or standard, and those services remain responsible for their own accessibility features.
Readers may request an alternative format, a plain-text copy, or help locating a particular article. Please identify the page, the barrier, the device or assistive technology involved, and the preferred response method. We aim to acknowledge a request within 10 working days and provide an update within 30 calendar days. Requests are used to improve the affected page and are retained only as long as needed to track the correction.
Feedback may be sent through contact.php or to 120 Cihampelas Street, Bandung, West Java 40131, Indonesia. General telephone contact is +62 22 731 8975. This statement was reviewed on 14 October 2026, with the next planned review in October 2027 and earlier review if a substantial template or navigation change is introduced.
The aim applies to public pages, article templates, forms, policy pages, navigation, and any reusable component controlled by Derive. We use semantic headings, readable spacing, visible focus states, descriptive links, and text alternatives as part of ordinary publishing work. Testing includes keyboard navigation and narrow-screen review, while recognizing that devices and assistive technologies behave differently. We prioritize fixes that prevent a person from understanding, navigating, or completing a basic task.
Alternative formats can include plain text, a structured copy of an article, or a direct explanation of where information appears on a page. A request should identify the URL, the barrier, the device or software involved, and a preferred response method. This information helps the desk reproduce the issue without requesting unnecessary personal data. Accessibility correspondence is normally kept for up to 24 months to track the fix and then reviewed for deletion.
Third-party pages, embedded services, and external links may use different controls and may have their own accessibility statements. Derive can report an issue to a provider or offer an equivalent text route where practical, but cannot change a service that it does not operate. Older archived pages may require template work before they meet the current approach. Material changes to navigation or forms trigger an earlier review rather than waiting for the annual cycle.
Requests are acknowledged within 10 working days and normally receive an update within 30 calendar days. A complex issue may take longer when it depends on a vendor or a browser-specific defect, and the desk will explain the status. Feedback may be sent through contact.php, to 120 Cihampelas Street, Bandung, West Java 40131, Indonesia, or by phone at +62 22 731 8975. This statement was reviewed on 14 October 2026 and is planned for reconsideration in October 2027.