Reading should be available to more people.
Prylan works to make its editorial site understandable, navigable, and usable across devices and assistive technologies.
Accessibility is an ongoing editorial and technical practice.
Our approach
We use semantic headings, visible focus states, descriptive link text, readable contrast, responsive layouts, and text alternatives for meaningful imagery. Content is written in plain, direct English wherever the subject allows.
Headings are arranged in a logical order so screen-reader users can move through an article by structure. Links describe their destination, while controls retain a visible keyboard focus indicator. Images that carry information receive descriptive alternative text, and decorative presentation is not relied upon to communicate an essential point.
We review the site against practical principles reflected in WCAG 2.2, while recognizing that accessibility depends on browsers, operating systems, assistive technology, and individual settings. A reader may enlarge text, use high-contrast settings, or navigate without a pointer. The responsive layout is intended to remain readable at narrow widths and increased zoom.
Known limitations
Some older third-party embeds or browser combinations may not expose every interaction in the same way. We review reported issues and prioritize barriers that prevent access to core information.
External links and embedded services are outside Prylan's direct control and may have different labels, focus order, captions, or contrast. When an embedded feature is not necessary to understand an article, the surrounding text remains the primary source of information. If a document is difficult to use, we can provide the relevant information in a plain-text response where practical.
Some older content may require a remediation pass, particularly where a historical link label or image description is incomplete. Reports are recorded, assessed for impact, and addressed during normal editorial maintenance. We do not ask readers to disclose a disability in order to report a barrier.
Feedback
To report a barrier, contact the desk at Jalan Sudirman No. 23, Karet Semanggi, Jakarta Selatan, DKI Jakarta 12922, Indonesia, or call +62 21 784 5932. Please describe the page, device, browser, and task you were trying to complete. Updated 2026.
Reports may be submitted at any time and are reviewed by the editorial desk on business days in Jakarta. We aim to acknowledge a report within five business days and provide an initial assessment within fifteen business days. Please avoid sending passwords, identity documents, or other unnecessary personal information.
If a barrier affects a time-sensitive request, identify the affected page and preferred alternative format in the first message. We will explain any available workaround, note whether a third party is involved, and keep the correspondence limited to resolving the access issue. This statement was reviewed on 5 October 2026; future changes will be dated on this page.
Practical access and feedback
Accessibility applies to the full public site, including article pages, navigation, contact routes, policy notices, and downloadable or linked material where Prylan controls the presentation. The current scope includes desktop and mobile layouts, keyboard navigation, browser zoom, screen readers, reduced-motion preferences, and high-contrast viewing. Some third-party content may have its own accessibility limits, and we identify those limits when they are material to a reader’s task.
Readers can report a missing label, unclear heading, insufficient contrast, keyboard barrier, caption issue, or other obstacle by contacting Prylan at Jalan Sudirman No. 23, Karet Semanggi, Jakarta Selatan, DKI Jakarta 12922, Indonesia, by telephone at +62 21 784 5932, or through the contact page. Please include the page address, the device or assistive technology involved if known, and the result you expected. We aim to acknowledge accessibility reports within five business days and provide a substantive response within fifteen business days; complex issues may require a longer review, with an interim update where practical.
Reports are used to improve the relevant page and are retained only as long as needed to investigate and document the change, normally no longer than twelve months after closure. A reader does not need to disclose a diagnosis or other sensitive information to request an adjustment. If a requested format cannot be produced immediately, the desk will discuss a reasonable alternative, such as plain text or a direct explanation.
This statement was reviewed on 5 October 2026. The next routine review is planned within twelve months, or sooner after a significant redesign, a material change in technology, or a substantiated accessibility concern. Previous versions are not used to reduce a reader’s current access rights.