ACCESSIBILITY

Designed for clear, flexible reading.

Reviewed 14 October 2026.

1. Our aim

Onward aims to make editorial information usable across common devices, screen sizes, input methods, and assistive technologies. We use semantic headings, descriptive links, visible focus styles, and readable contrast.

2. Structure

Pages use landmarks, headings, lists, tables, and labels to give content a predictable shape. We avoid using color alone to communicate meaning and keep navigation links available in the footer.

3. Images

Every editorial image includes descriptive alternative text intended to communicate its visual role. Decorative details are not used as the only source of meaning. Images are sized to remain comfortable to scroll.

4. Keyboard use

Primary links, buttons, form fields, and the mobile navigation can be reached with a keyboard. Focus should remain visible. If a browser or assistive technology behaves differently, please tell us the page and device.

5. Language and readability

We use US English, short paragraphs, clear labels, and explanations for specialized terms. Readers can enlarge text through browser controls. Layouts respond to smaller screens without requiring horizontal scrolling for ordinary content.

6. Forms

Contact fields have labels and required states. After a valid submission, the page displays a success message. No form should require a visitor to disclose more than is needed for an editorial reply.

7. Known limitations

Third-party content, older browsers, and embedded services may not meet the same standard. Some complex tables or changing browser settings may require an alternative reading path. We prioritize issues affecting core content.

8. Testing

We review pages using responsive layouts, keyboard navigation, contrast checks, and common browser behavior. Testing is ongoing rather than a claim that every combination works perfectly.

9. Request support

Contact Onward at Jalan Thamrin No. 10, Menteng, Central Jakarta, DKI Jakarta 10310, Indonesia, or +62 813 7489 2560. Describe the barrier, page address, and preferred response method.

10. Response and change log

We aim to acknowledge accessibility feedback within 10 business days. This page was reviewed 14 October 2026; a 20 September 2026 update clarified keyboard and form behavior. Changes will be dated.

Feedback and response process

Accessibility feedback is most useful when it identifies the page address, the task a visitor was attempting, the device or browser involved, and whether keyboard navigation, zoom, contrast, captions, labels, or alternative text was affected. Visitors do not need to provide a medical detail or any information unrelated to the access issue.

Feedback may be sent through the contact page or to +62 813 7489 2560. We normally acknowledge a report within five business days and assess core-content barriers within 15 business days. Complex third-party or browser-specific issues may take longer; when that happens, we provide a progress note and record the practical workaround if one is available.

We retain accessibility correspondence for up to 24 months after closure so repeated issues can be compared and resolved consistently. Limited technical logs may be retained for up to 90 days for security and troubleshooting. Accessibility reports are shared only with hosting, development, support, or relevant third-party providers when their involvement is needed.

Our ongoing review includes semantic structure, focus order, text resizing, descriptive links, image alternatives, form labels, and responsive behavior. The page was reviewed on 14 October 2026. Material changes to this statement will be dated and explained so visitors can follow the improvement history.