Bliro

Accessibility statement

Reviewed 1 October 2026. Bliro wants its editorial material to be usable across devices, abilities, and reading preferences. This commitment extends to readers using assistive technology, readers browsing on a slower mobile connection, and readers who simply prefer a calmer, less cluttered layout. Accessibility is treated as an ongoing practice rather than a one-time project, since new content and page layouts are added over time. This page describes our current approach and the practical steps we take, as well as how to tell us when something falls short. It applies to every page under the Bliro domain, including articles, resource listings, and the contact form.

1. Our approach

This statement applies to the website operated by Bliro, registered in Indonesia under Nomor Induk Berusaha (NIB) 0812026004571 and Nomor Pokok Wajib Pajak (NPWP) 03.147.882.6-016.000, with its editorial office at Jalan Cempaka Putih Raya No. 15, RT.005/RW.001, Cempaka Putih Timur, Jakarta Pusat 10510, Indonesia. We use semantic headings, readable contrast, descriptive image alternatives, keyboard-friendly controls, and responsive layouts. Accessibility is treated as an ongoing practice rather than a one-time claim. Semantic headings allow a screen reader user to understand a page's structure at a glance and jump directly to a relevant section rather than reading from the top every time. Readable contrast means text color is checked against its background so that most readers, including those with mild vision differences, can read comfortably without strain. Descriptive image alternatives explain what a meaningful image shows and why it matters to the surrounding article, rather than using a generic label. Because templates are shared across many pages, a single improvement, such as a clearer focus indicator for keyboard navigation, benefits every page that uses that template once it is applied.

  • a) Semantic structure: headings and landmarks support direct navigation for assistive tools.
  • b) Contrast: checked so text remains legible against its background.
  • c) Shared templates: a single fix benefits every page using that template.

2. Content structure

Pages use headings, lists, tables, labels, and meaningful links where appropriate. Long policy pages are divided into numbered sections. We review new articles before publication. Meaningful links describe their destination plainly, such as naming the topic of a linked article rather than using an ambiguous phrase like click here, which helps a screen reader user scanning a list of links out of context. Numbered sections on long policy pages, such as this statement and the privacy policy, make it easier to reference a specific point in correspondence or during a review. Reviewing new articles before publication includes checking heading order, confirming that images have appropriate alternative text, and verifying that any table used has properly labeled columns. This pre-publication check is informal but consistent, applied to every new piece of content rather than only periodically.

  • a) Meaningful links: describe their destination rather than using ambiguous phrasing.
  • b) Numbered sections: make long policy pages easier to reference precisely.
  • c) Pre-publication review: applied consistently to every new article.

3. Images

Images include descriptive alternative text when they convey information. Decorative details are kept out of the reading path where possible. Contact us if an image needs a more useful description. Descriptive alternative text for a meaningful image, such as a photograph illustrating a movement routine, names what the image shows and why it is relevant to the surrounding article, rather than a generic label such as photo. Decorative details, such as a repeated background pattern with no informational content, are marked so a screen reader does not interrupt the reading flow with an unhelpful description. When a reader reports that an image's description is missing, inaccurate, or unclear, we review the specific page and aim to correct it rather than waiting for an infrequent batch update. We also check new images against this standard before they are published, rather than relying solely on reader reports after the fact.

  • a) Meaningful images: described in context, naming the subject and its relevance.
  • b) Decorative images: kept out of the screen-reader path where technically possible.
  • c) Reported issues: reviewed and corrected on the specific page affected.

4. Keyboard access

Navigation and forms are intended to work without a pointer. Focus should remain visible during interaction. If a control is difficult to reach, tell us the page and device involved. Controls intended to work without a pointer include the mobile navigation toggle, the cookie consent banner buttons, and every field in the contact form, all of which should respond to the tab key and the enter key without requiring a mouse. A visible focus indicator helps a keyboard user see exactly which element is currently selected as they move through a page, which is especially important on a long article with many links. When reporting a difficulty, including the browser, assistive technology if used, and approximate device type helps us reproduce and address the issue more precisely. We treat keyboard accessibility issues as a priority category because they can prevent a reader from completing basic tasks such as sending a message.

  • a) Keyboard reachability: applies to navigation, consent banner, and form fields.
  • b) Visible focus: helps track position while moving through a page.
  • c) Priority handling: keyboard barriers are treated as high priority when reported.

5. Motion and color

The site avoids unnecessary animation and does not rely on color alone to communicate meaning. Text uses dark charcoal on cream or light text on charcoal. Browser zoom should remain usable. Avoiding unnecessary animation reduces the chance of discomfort for readers sensitive to movement, such as those with vestibular conditions, and keeps pages faster to load on slower connections. Not relying on color alone means an important distinction, such as a required form field, is also indicated with a label or symbol rather than color changes that a colorblind reader might miss. The dark charcoal on cream combination used for body text, and light text on charcoal used in darker sections, is chosen to maintain comfortable contrast in both directions. Browser zoom up to 200 percent should not cause text to overlap or be cut off, which we check when reviewing new page templates.

  • a) Minimal animation: reduces discomfort and supports slower connections.
  • b) Color independence: important information also conveyed through labels or symbols.
  • c) Zoom support: layouts checked to remain usable at up to 200 percent zoom.

6. Documents

Any future downloadable document will be reviewed for headings, text alternatives, and reading order. If an accessible version is needed, contact the editorial desk before relying on the document. A downloadable document, such as a guide offered as a reference, would be checked for a logical heading structure so that a screen reader can navigate it the same way it navigates a web page. Text alternatives would be added for any chart or illustration within the document, consistent with the approach described in Section 3 for images on the website itself. Reading order matters particularly for documents with multiple columns or sidebars, where a poorly tagged layout can cause assistive technology to read content out of sequence. Until a specific document is confirmed accessible, we recommend contacting the editorial desk to request the underlying information in an alternative format.

  • a) Heading structure: checked within any downloadable document before release.
  • b) Text alternatives: added for charts or illustrations within documents.
  • c) Alternative formats: available on request before a document's accessibility is confirmed.

7. Known limits

Third-party pages linked by Bliro may not share our accessibility approach. Some older content may need additional review. We prioritize issues that prevent reading, navigation, or contact. A linked external resource, such as an organization's own website, is governed by that organization's own accessibility practices, which we cannot control or guarantee. Older content published before a template improvement may not yet reflect the latest heading structure or image description standard, and we schedule these for review as part of ongoing maintenance rather than all at once. Issues that prevent reading, navigation, or contact, such as a broken keyboard trap or missing form label, are treated as higher priority than a cosmetic inconsistency. This prioritization reflects limited editorial resources being directed toward the barriers most likely to stop a reader from accomplishing a basic task.

  • a) External links: governed by the linked site's own accessibility practices.
  • b) Older content: reviewed progressively rather than all at once.
  • c) Priority issues: barriers to reading, navigation, or contact addressed first.

8. Request support

Send a request to Jalan Cempaka Putih Raya No. 15, RT.005/RW.001, Cempaka Putih Timur, Jakarta Pusat 10510, Indonesia, or +62 21 7890 3215. Include the page, barrier, and preferred response format. A written letter is appropriate for a detailed request, while a phone call during Jakarta business hours is often faster for a quick clarification about how a specific page behaves. Including the specific page address and a short description of the barrier, such as a control that cannot be reached by keyboard, lets our team reproduce the issue directly rather than guessing. A preferred response format might include a plain-text summary of an article's content if the original layout is causing difficulty for a particular assistive technology. Phone and written requests are logged the same way, so either channel receives equal attention and the same response timeline described in Section 9.

  • a) Written requests: sent to the postal address above for detailed barriers.
  • b) Phone requests: available during Jakarta business hours for quick clarification.
  • c) Alternative formats: available on request when a layout causes difficulty.

9. Response process

We aim to acknowledge accessibility requests within 10 business days and provide a substantive response within 30 days. Some changes require a publishing or hosting update. We will explain any delay. The initial acknowledgment within 10 business days confirms that the request was received and gives a general sense of the next steps, even if the underlying barrier has not yet been resolved. A substantive response within 30 days typically either confirms that a correction has been made, such as adding a missing image description, or explains a realistic timeframe for a larger structural change. Some changes, such as updating a shared page template that affects every article, require coordination with hosting and publishing workflows and may take longer than a single-page correction. Where a delay extends beyond the initial 30-day estimate, we will provide an updated timeframe rather than leaving the request without further communication.

  • a) Acknowledgment: within 10 business days of a request being received.
  • b) Substantive response: within 30 days, confirming a fix or a realistic timeframe.
  • c) Extended delays: communicated with an updated timeframe rather than silence.

10. Change log

This statement was reviewed on 1 October 2026. The review added clearer contact and document guidance. Future updates will display their date and summary. The 1 October 2026 review added the specific response-time commitments in Section 9 and clarified the distinction between meaningful and decorative images in Section 3, both of which earlier wording described more briefly. We generally plan a review at least twice a year, or sooner if a significant redesign or new content category is introduced that could affect how pages are structured. A significant improvement, such as adopting a new heading structure across article templates, will be noted here with the date it took effect. We welcome ongoing feedback between formal review cycles, since reader reports described in Section 8 often surface issues more quickly than a scheduled review would.

  • a) 1 January 2026: initial publication of this accessibility statement.
  • b) 1 October 2026: added response-time commitments and clarified image guidance.
  • c) Planned cadence: at least twice yearly, or sooner after a significant site change.