Accessibility statement
Effective 13 October 2026. Veneran aims to make its editorial publication usable across devices, connection conditions, and assistive technologies.
This statement covers the public pages, navigation, forms, articles, and downloadable resources published by Veneran. Accessibility work is guided by practical usability and by the principles commonly reflected in WCAG 2.2, while recognising that conformance can vary by browser, device, and third-party content.
1. Our aim
We work toward readable contrast, meaningful headings, keyboard access, descriptive image alternatives, and responsive layouts. Accessibility is treated as an ongoing practice rather than a finished label.
Reviews consider sight, hearing, mobility, speech, cognitive, and temporary access needs. A page that works with a mouse but not a keyboard is treated as incomplete, as is a page whose meaning depends only on colour. We prioritise barriers that prevent reading, navigation, form completion, or understanding.
2. Content structure
Pages use headings, lists, labels, navigation landmarks, and link text that describe destinations. Long material is divided into sections so readers can orient themselves.
Headings are intended to follow a logical order, and tables are reserved for information that benefits from row and column relationships. Form controls should have visible labels and useful error text. When a link opens another service, the destination is described where practical.
3. Images
Images include descriptive alternative text where they communicate information. Decorative choices are kept limited. If an image is confusing or missing an alternative, please tell us which page and section.
Alternative text describes the relevant subject and purpose rather than repeating a file name. A decorative image should not add noise to a screen reader experience. Where a complex image carries information that cannot fit in an alt attribute, we aim to provide nearby explanatory text.
4. Keyboard use
Interactive controls are intended to be reachable with a keyboard and show a visible focus state. Browser and assistive technology combinations can behave differently, so reports help us test real situations.
Menus, links, forms, and dismissal controls should be operable without a pointer. Focus should not disappear behind a fixed header, and the mobile menu should close in a predictable way. A report is especially useful when it includes the key sequence that caused the problem.
5. Motion
The site avoids unnecessary animation and does not require motion to understand editorial content. Browser preferences and device settings may also influence presentation.
We aim to respect reduced-motion settings and avoid flashing or rapidly changing content. If a transition makes a control difficult to use, a visitor can report the page and browser combination. Static content remains the primary way information is communicated.
6. Mobile access
Navigation adapts to smaller screens and content remains available without hover. We test common phone widths and revise layouts when a control becomes difficult to use.
Responsive work includes readable line lengths, sufficient spacing, usable touch targets, and content that does not require horizontal scrolling in ordinary reading. Network conditions in Indonesia can vary, so pages are kept focused and images are presented with useful alternatives.
7. Documents
Where downloadable materials are added, we will aim to provide accessible formats or an equivalent HTML reading path. Ask the reader desk for an alternative when needed.
Document checks include reading order, headings, language metadata, contrast, links, and whether a text alternative is available. Third-party documents may not be fully controlled by Veneran; in that case, we will identify an equivalent route where practical.
8. Feedback
Send accessibility feedback to Veneran at Jl. Pahlawan Seribu No. 8, Sektor 4, BSD City, Tangerang Selatan, Banten 15310, Indonesia. Include the page, device, browser, assistive technology, and the barrier you encountered.
You may also call +62 813 6745 9021. We aim to acknowledge feedback within 7 days, assess straightforward issues within 30 days, and explain the next step when a correction requires more time. Please do not include unnecessary personal information.
9. Review record
This statement was reviewed on 13 October 2026. Future revisions will record the date, the affected area, and the general reason for the change. Accessibility feedback is considered alongside content, security, and performance work.
Feedback, testing, and support
Accessibility feedback is most useful when it identifies the page address, the task being attempted, the device or browser involved, and the barrier encountered. A reader may also describe an alternative format or communication method that would help. We do not require a person to disclose a disability, diagnosis, or other private detail in order to report a problem. Reports are handled as service information and shared only with people who need them to investigate.
We aim to acknowledge an accessibility report within 7 calendar days and to provide a practical response or progress update within 30 days. A fix may involve content, markup, contrast, focus order, image alternatives, captions, downloadable material, or a third-party component. Some changes require testing across browsers and may take longer; in that case we explain the interim option and expected review path. Readers who cannot use a form may write to Jl. Pahlawan Seribu No. 8, Sektor 4, BSD City, Tangerang Selatan, Banten 15310, Indonesia, or call +62 813 6745 9021.
Our accessibility work is reviewed alongside ordinary content updates and is informed by WCAG 2.2 principles, keyboard testing, zoom checks, screen-reader checks where available, and reports from readers. Third-party documents or linked services may have separate accessibility controls, and we will identify that boundary when practical. This statement was reviewed on 13 October 2026; material changes will be dated so readers can understand what has been updated.