Accessibility Statement
Perma aims to make its editorial pages readable and usable for people with different access needs. This statement was reviewed 5 October 2026.
Our approach considers keyboard access, readable structure, contrast, alternative text, responsive presentation, and compatibility with common assistive technologies. The site is reviewed on a practical basis, while recognising that browsers, devices, and third-party content differ.
1. Structure
Pages use headings, landmarks, lists, labels, and descriptive links to support navigation.
Headings are arranged to provide a meaningful outline, and links describe their destination where space allows. Long policy pages use numbered sections so a reader can locate a topic without scanning every paragraph. If a heading or label is unclear, please report the page and wording.
2. Contrast
The palette uses dark text on light backgrounds and light text on dark footer sections.
We avoid relying on colour alone to communicate status or meaning. Visitors may also use browser zoom, operating-system contrast settings, or a reader mode. A colour issue should be reported with the page address and affected component.
3. Images
Published images include descriptive alternative text. Decorative treatment is kept limited.
Alternative text describes the subject and purpose rather than repeating a caption. Images that carry no informational value should not interrupt a screen reader’s reading order. If an image is misleading, missing text, or difficult to interpret, contact Perma so the asset can be reviewed.
4. Keyboard use
Navigation and controls are intended to be reachable by keyboard.
Focus should remain visible while moving through links, buttons, details controls, and form fields. A visitor should not need a mouse or touch gesture to open ordinary navigation. We test common tab sequences during page updates and welcome reports of traps or skipped controls.
5. Motion
The interface does not depend on rapid animation or auto-playing media.
Where a browser or embedded service introduces motion, the visitor can use operating-system preferences or the provider’s controls where available. Perma avoids flashing patterns and unnecessary transitions. A motion concern should be described so the relevant page can be checked.
6. Forms
Contact fields have visible labels and required states.
Instructions should appear before submission, and errors should be understandable without depending on colour. A form response is confirmed with a clear message where the feature is available. Do not include medical records or unnecessary personal information in an accessibility report.
7. Mobile
The layout adapts to narrow screens and exposes a mobile navigation control.
Responsive layouts are checked at common phone widths and with increased text size. Horizontal scrolling, small tap targets, and clipped headings are treated as issues for review. Device accessibility settings may alter the final presentation and should be included in a report when relevant.
8. Limitations
Third-party content may not meet the same standard.
External articles, event platforms, video players, fonts, or embedded services may have separate controls and support teams. Perma cannot change their code, but may replace, remove, or provide an alternative link when a serious barrier is identified. We review third-party material before publication where practical.
9. Feedback
Report a barrier at Jalan Sudirman Kav. 22, Karet Semanggi, Setiabudi, Jakarta Selatan, DKI Jakarta 12930 or +62 813 5792 4680.
Please include the page, device, browser, assistive technology if relevant, and the action that could not be completed. We aim to acknowledge feedback within five business days and provide an initial assessment within 30 calendar days. Urgent access to an event should be identified in the subject.
10. Review
The next planned review is December 2026, with material fixes recorded when made.
The 5 October 2026 review is the current baseline. A later revision will record the date, the area reviewed, and material changes. Issues are prioritised according to user impact, frequency, and the availability of a practical alternative.
Accessibility feedback is most useful when it identifies the page address, device or browser, assistive technology if relevant, and the specific control or passage affected. A visitor may describe the task they were trying to complete, such as opening the navigation, reading a policy section, submitting a contact form, or understanding an image. Personal medical or identity information is not needed to report an accessibility issue. Perma aims to acknowledge a report within five business days and will provide an update when a correction needs more investigation.
Some content may be supplied by third parties, including hosting, embedded media, event registration, or linked resources. Perma reviews the way that content appears on its pages, but the third party may control its own markup, keyboard behaviour, captions, or accessibility settings. Where an external component creates a barrier, we will consider an accessible alternative, a descriptive text route, or a direct request to the provider. Browser zoom, text resizing, reader mode, and operating-system settings may also change the presentation.
This statement was reviewed on 5 October 2026. The next planned review is 5 January 2027, with earlier review when a major page template, navigation pattern, form, or media component changes. Feedback can be sent to Jalan Sudirman Kav. 22, Karet Semanggi, Setiabudi, Jakarta Selatan, DKI Jakarta 12930 or +62 813 5792 4680. The request will be handled as accessibility correspondence under the retention periods described in the Privacy Policy.
Practical access guidance
Perma designs pages so that information can be reached with a keyboard, read at enlarged text sizes, and understood without relying on colour alone. Headings are arranged in a meaningful order, links describe their destination, and form controls should have a visible label. These practices support people who use screen readers, magnification, voice control, switch access, or a browser’s reading mode.
Some presentation can vary between browsers, operating systems, and assistive technologies. A heading may be announced differently, a focus outline may use a system colour, or an embedded document may expose its own controls. Perma treats these differences as part of the testing context and records reproducible issues rather than assuming that one device represents every visitor.
Feedback and correction pathway
Send the page address, the task attempted, the device and browser, and a short description of the barrier to Jalan Sudirman Kav. 22, Karet Semanggi, Setiabudi, Jakarta Selatan, DKI Jakarta 12930 or +62 813 5792 4680. Do not include medical information, passwords, identity documents, or other unnecessary private material. We aim to acknowledge a report within five business days and provide a progress update within 30 calendar days.
- Alternative text concerns are reviewed against the purpose of the image.
- Keyboard concerns are tested from page load through completion of the task.
- Caption or transcript requests are assessed against the media format.
- Third-party barriers are reported to the provider and, where practical, paired with an accessible alternative.
This statement was reviewed on 5 October 2026. Operational accessibility records may be retained for up to 24 months, while a correction record may be retained longer when needed to document the publication history. The next scheduled review is 5 January 2027 or sooner after a major template change.