Accessibility statement

1. Our aim

We aim for the site to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. We treat accessibility as part of editorial quality, not an add-on, and review it whenever we change a template.

This statement covers every page published at www.zandrel.id, including the article pages, the glossary, the resource list, the contact form and the legal pages. It does not cover external websites that we link to, or documents that are hosted elsewhere. Our commitment is also informed by Law No. 8 of 2016 on Persons with Disabilities in Indonesia, which recognises access to information and communication as part of equal participation, and by the practical needs of readers who use screen readers, magnification, voice control or a keyboard instead of a mouse.

The current conformance status is “partially conforms” to WCAG 2.1 level AA. That wording is used because most success criteria are met on every template, while a small number are met only in part, as described in section 3. We would rather describe that gap openly than claim full conformance that we cannot demonstrate for every page.

The review behind this statement took place between 14 and 25 September 2026 and combined several methods, so that no single tool decided the outcome:

• Keyboard-only use of every template, checking that each link, button, accordion and form field can be reached and operated in a logical order.
• Reading pages with a desktop screen reader in a current browser and with the built-in screen readers on iOS and Android phones.
• Zooming to 200 percent and to the equivalent of 400 percent on a narrow window to check that text reflows and nothing is cut off.
• Measuring colour contrast of text, links, buttons and form borders against the WCAG ratios, and re-checking after any colour change.
• Validating the HTML so that headings, lists, tables and landmarks are marked up correctly.

The site is hosted by Amazon Web Services in its Asia Pacific (Jakarta) region. We mention this because page speed matters for accessibility too: pages that load quickly on mobile connections are easier to use for readers on older phones or limited data plans, and the site avoids large scripts and heavy media for the same reason.

2. What we have done

• Semantic page structure with a single main heading, ordered subheadings and landmark regions.
• A “Skip to main content” link at the start of every page.
• Full keyboard operation of navigation, accordions, forms and the cookie notice, with visible focus outlines.
• A mobile menu button that announces whether it is expanded or collapsed.
• Text colour and background combinations chosen for contrast: dark charcoal text on cream, and a darker terracotta for links.
• Body text set at 17 pixels with generous line spacing, and layouts that reflow on small screens without horizontal scrolling of the main text.
• Descriptive text alternatives for informative images.
• Labels attached to every form field, with a status message shown when the contact form is sent.
• Motion kept to subtle hover effects, which are switched off for people who set a reduced-motion preference.
• Plain language, short paragraphs and a glossary of terms.

The points below explain how some of these features work in practice, including the edge cases that readers most often ask about:

1. Page structure. Each page has one main heading, and subheadings follow in order without skipping levels. Screen reader users can therefore move between headings, or jump to the main content, header, navigation and footer landmarks. Breadcrumbs are marked up as an ordered list so that the reader hears the position of the page in the site.
2. Keyboard and focus. The Tab key moves forward through interactive elements and Shift with Tab moves back. A visible outline shows where the focus is. The cookie notice is part of the page, not a pop-up that traps the keyboard, so it can be skipped or answered at any time.
3. Colour and contrast. Information is never conveyed by colour alone. Links are underlined or otherwise distinguishable from surrounding text, and table headers are marked up with scope attributes so that each cell can be read with its column heading.
4. Images. Photographs that carry meaning have a text alternative that describes what is shown. Decorative graphics, such as the small leaf symbol beside the site name, are hidden from assistive technology so that they do not add noise.
5. Forms. Every field has a visible label. Required fields are identified in text, not only by colour or a symbol. After the contact form is sent, a status message confirms that the message was received, and it is announced by screen readers without moving the focus away.
6. Motion. Hover effects are small and nothing flashes or auto-plays. If your device is set to reduce motion, transitions are switched off. The site has no video or audio at present, so captions and transcripts are not yet needed; they will be provided if media is added.
7. Language. The page language is declared in the page code as English for Indonesia, which helps screen readers choose the right pronunciation. Indonesian terms that appear in the text are explained in the surrounding sentence or in the glossary.

3. Known limitations

• Some data tables are wide and scroll horizontally on narrow screens.
• Linked external sites, such as government portals, are outside our control and may not meet the same standard.
• Indonesian terms are included in some articles; we do not yet provide full Indonesian translations of pages.

We are working on these items and will update this page as they change.

To give a clearer picture of each limitation: wide tables, such as the reference tables on the topic pages, sit inside a scrollable container so that the page itself does not become wider than the screen. The container can be reached and scrolled with the keyboard, but reading a table of five or six columns on a small phone is still less comfortable than on a larger screen. We shorten table headings where we can and add a plain-text summary above the table so that the main point is available without scrolling.

Regarding external sites, we cannot repair the pages of other organisations, but we choose official sources with a record of publishing accessible content, and we mention in the resource list when a source is a PDF document, because PDF files can be harder to use with assistive technology. Regarding language, the site is currently written in English with Indonesian terms explained in context. Full Indonesian versions of the articles are under consideration for a future year; no date has been set, and we will not announce one until the work is resourced.

We also know of the following smaller issues, which are listed here so that readers are not surprised by them:

• Some older article images have short text alternatives that could describe more of what is shown. These are being rewritten in order of readership during the first quarter of 2027.
• The accordion controls on the FAQ and home page announce their expanded or collapsed state, but the wording of that announcement depends on the screen reader and may differ from what is described in our help text.
• The glossary is long, and there is not yet a letter-by-letter index at the top of the page to jump to a term.

4. Tips for adjusting the site

You can enlarge text using your browser's zoom (usually Ctrl or Cmd with the plus key) or increase the default font size in browser settings. Most browsers also offer a reader view that simplifies article pages, and the site works with common screen readers and with operating system high-contrast modes.

Settings that readers commonly find useful are listed below. Menu names change between versions, so search the settings of your device for the words in italics if a path differs from the one given:

• On a computer. Use browser zoom up to 200 percent or more, switch on the browser's reader view for long articles, or choose a high-contrast theme in the operating system's accessibility or ease of access settings.
• On an Android phone. Open Display size and text to enlarge the font, and use Select to Speak or the built-in screen reader to have text read aloud.
• On an iPhone or iPad. Use Display & Text Size to increase text, Speak Screen to listen to a page, and Reduce Motion if animation is uncomfortable.
• With voice control. The visible text of links and buttons matches their accessible name, so spoken commands such as “click Contact” work as expected.
• With a keyboard. Press Tab to move forward, Shift with Tab to move back, Enter to follow a link or press a button, and Space to expand or collapse an accordion item.

5. Feedback and requests

If you meet a barrier or need information in a different format, please tell us:

• Email: [email protected]
• Telephone: +62 813 6745 2918, Monday to Friday, 09:00 to 17:00 WIB
• Post: Zandrel Editorial, Jalan Bunga Raya No. 25, Kebayoran Baru, Jakarta Selatan, DKI Jakarta 12160, Indonesia
• Or use the contact form.

Please include the page address, a description of the problem and the browser or assistive technology you use. We aim to reply within five working days and to fix confirmed issues in the next scheduled update.

What happens after you write to us is set out here so that you know what to expect. We first acknowledge your message and, if needed, ask a short question to reproduce the problem. We then decide whether it is a defect on our side or a limitation of an external site. Defects are logged with a priority: problems that stop a reader from finishing a task, such as a form that cannot be submitted with a keyboard, are fixed within 15 working days, and other issues are fixed in the next monthly update. We will tell you when the fix has been published and ask whether it solves the problem for you.

If you need the content of an article in another form, we can provide a plain-text version by email, a version with larger type as a document file, or a read-aloud copy of a specific page on request. We do not charge for these formats. Requests are answered within the same five working days, and the format itself is normally supplied within ten working days, depending on the length of the page.

6. Related pages

See also our privacy policy and sitemap, which lists every page on the site.

If you are not satisfied with our reply, you can ask for the matter to be reviewed by the editor-in-chief, who will respond within ten working days. You may also raise a concern with the National Commission on Disabilities (Komisi Nasional Disabilitas) or with the Ministry of Communication and Digital Affairs (Komdigi). This statement will be reviewed again at least once a year, and the next scheduled review is September 2027, or earlier if a template changes significantly.