Accessibility statement

Genesis aims to make its English-language editorial content usable across current browsers, screen readers, keyboards and different display sizes. We use semantic headings, readable contrast, descriptive image alternatives and visible focus states. The site is reviewed during 2026 and improvements are recorded as issues are identified.

1. Access and improvement

Content is structured so readers can move through headings and links without relying on colour alone. Images include descriptive alternatives, while decorative detail is kept out of the reading path. Forms identify labels and provide a confirmation after submission. Some third-party material may not meet every expectation, and browsers or assistive technologies can interpret features differently. We welcome reports describing the page, problem, device and preferred contact method. Genesis will assess reports in a reasonable period and prioritise barriers that prevent access to essential information. The office is at Jl. Sudirman 12, Jakarta Pusat, DKI Jakarta 10220, Indonesia, and the phone is +62 813 5792 4680. This statement was published 1 January 2026 and reviewed 1 June 2026.

Standard we work towards. Our target is conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. We check pages against these criteria during design and again after changes. We have not commissioned a formal external audit at this stage, so we describe the standard as a goal rather than a certification. Results of internal checks are summarised in the change log below.

1. Perceivable: text alternatives, contrast, resizable text.
2. Operable: keyboard access, visible focus, clear navigation.
3. Understandable: consistent layout and plain language.
4. Robust: valid markup that assistive tools can read.

Standards followed. The design and content aim to follow the Web Content Accessibility Guidelines 2.1 at level AA, published by the World Wide Web Consortium. These guidelines are organised around four principles: content should be perceivable, operable, understandable and robust. The Indonesian government encourages accessible digital services under Law No. 8 of 2016 on Persons with Disabilities, and Genesis uses that law as a reference for good practice. Conformance is a continuing goal, and no claim of complete conformance is made.

1. Target: WCAG 2.1 level AA.
2. Reference: Law No. 8 of 2016 on Persons with Disabilities.
3. Conformance is reviewed rather than assumed.

Keyboard and navigation. All links, buttons, the menu and form controls can be reached with the Tab key and activated with Enter or Space. A skip link allows keyboard users to move past repeated navigation. On small screens the menu opens from a labelled button, and the focus order follows the visual order. Headings are arranged in a logical hierarchy so that screen-reader users can jump between sections.

1. Skip to content link at the top of each page.
2. Focus outline visible on every interactive element.
3. Menu button announces whether it is open or closed.

Keyboard and focus support. All navigation links, buttons, form fields and disclosure controls can be reached and used with a keyboard. The Tab key moves forward through interactive elements and Shift plus Tab moves backward, with a visible outline showing the current focus. The mobile menu opens and closes with Enter or Space and can be dismissed with Escape. A skip link at the top of each page lets keyboard users jump directly to the main content.

1. Visible focus outline on interactive elements.
2. Menu operable with Enter, Space and Escape.
3. Skip link to the main content.

Screen readers and images. Photographs carry descriptive alternative text that explains what is shown, while purely decorative items are hidden from assistive technology. Tables used for comparisons include header cells so that data can be read in context. We test pages with at least one desktop and one mobile screen reader. Link text describes the destination rather than saying only to click here.

1. Alt text written for meaning, not decoration.
2. Table headers associated with data cells.
3. Descriptive link text throughout.

Screen reader compatibility. Pages use landmark regions for the header, navigation, main content and footer, so that screen reader users can move between them quickly. Headings follow a logical order from a single level one heading downward, and lists and tables use native markup. Form fields have programmatic labels, and the confirmation message after sending the contact form is announced politely without moving focus unexpectedly. The site has been checked with NVDA on Windows and VoiceOver on iOS during 2026, and further testing is planned.

1. Landmarks for header, navigation, main and footer.
2. Logical heading hierarchy on every page.
3. Form confirmation announced to assistive technology.

Colour, contrast and text size. Body text uses a charcoal colour on light backgrounds and white text on dark navy, both exceeding the 4.5:1 contrast ratio. Information is never conveyed by colour alone. Text can be enlarged to 200 percent in the browser without loss of content or functionality, and layouts reflow to a single column on narrow screens. Motion is minimal, and we respect the reduced-motion preference.

1. Minimum contrast ratio of 4.5:1 for body text.
2. Zoom to 200 percent supported.
3. No flashing content.

Colour, contrast and text. Body text uses a dark charcoal on a light background, which exceeds the 4.5 to 1 contrast ratio required for normal text. Links are distinguishable by underline or by additional cues rather than colour alone. Text can be enlarged to 200 percent in the browser without loss of content or function, and line spacing is set generously for readability. Readers who prefer a different colour scheme can use browser or operating system settings, which the layout respects.

1. Contrast of at least 4.5 to 1 for body text.
2. Links not distinguished by colour alone.
3. Zoom to 200 percent supported.

Forms and messages. Each field in the contact form has a visible label, and required fields are marked in text. Error and success messages appear in the page rather than in a transient pop-up, and they are announced to assistive technology. Users can reach us by telephone on +62 813 5792 4680 or by post if the form is not suitable. Time limits are not imposed on completing the form.

1. Visible labels and instructions.
2. Clear confirmation after sending.
3. Alternative contact channels available.

Images, media and motion. Meaningful images carry descriptive alternative text that explains what the picture shows, while purely decorative images are marked so that assistive technology can skip them. The site does not play audio or video automatically. Animations are limited, and readers who have chosen reduced motion in their system settings see minimal movement. If video or audio is added later, captions or transcripts will be provided with it.

1. Descriptive alternative text for informative images.
2. No autoplay of audio or video.
3. Reduced motion preference respected.

Known limitations. Some older articles may contain images whose descriptions are less detailed than we would like, and a few embedded or third-party items may not fully meet the guidelines. Charts and tables with complex data may be easier to follow with the accompanying text summary than visually. We list identified issues internally and give priority to those that block access to essential information such as contact details or policies.

1. Alt text of archived articles under review.
2. Third-party content outside our control.
3. Complex data supplied with text summaries.

Forms and error handling. The contact form uses visible labels, indicates which fields are required and explains what went wrong if a field is left empty or entered incorrectly. Error messages are written in plain language and positioned next to the relevant field. There is no time limit for completing the form, and no information is lost if a reader pauses. A clear success message confirms that the message was sent and tells the reader when to expect a reply.

1. Visible labels and required-field indicators.
2. Plain-language error messages near the field.
3. No time limit on completion.

Browsers and devices. The site is designed for current versions of Chrome, Safari, Firefox and Edge on desktop and mobile, and for common screen readers and magnifiers. We aim to avoid reliance on features that are only available in a single browser. Printing is supported through a simple print style. If a page does not display correctly on your setup, please tell us which browser and version you use.

1. Responsive layout from small phones to large monitors.
2. Works without precise pointer control.
3. Print-friendly article pages.

Known limitations. Some older articles contain tables that are wide and may require horizontal scrolling on narrow screens. A small number of externally sourced charts may lack full text descriptions, and PDF files listed on the resources page may not be fully tagged for screen readers. These items are recorded in our improvement list and are scheduled for correction during 2026. Where a document cannot be made accessible quickly, the editorial desk can provide the content in another format on request.

1. Wide tables on narrow screens.
2. Some external charts lack full descriptions.
3. Alternative formats available on request.

Reporting a barrier and response times. To report a problem, send the page address, a description of the issue, the device and assistive technology used, and how you prefer to be contacted. We acknowledge reports within 5 working days and provide a plan or alternative format within 20 working days. Where a fix takes longer, we explain why and offer the information another way, for example as plain text by email.

1. Contact: contact.php or +62 813 5792 4680.
2. Post: Jl. Sudirman 12, Jakarta Pusat, DKI Jakarta 10220, Indonesia.
3. Alternative formats on request.

Testing approach. Accessibility is checked in three ways: automated scanning for common errors, manual testing with keyboard and screen reader, and feedback from readers. Automated tools find only a portion of problems, so manual review is treated as essential. New pages are checked before publication, and the full site is reviewed at least once per year. Findings are logged with an owner and a target date so that fixes are tracked to completion.

1. Automated scans on every release.
2. Manual keyboard and screen reader checks.
3. Annual full-site review with a tracked action list.

Training and ownership. The editorial desk is responsible for accessibility, and everyone who publishes content receives guidance on headings, alt text and plain language. New features are checked before release and again after changes. Contributors are asked to supply image descriptions with their submissions. Feedback from readers is logged and reviewed monthly.

1. Publishing checklist includes accessibility checks.
2. Feedback reviewed monthly.
3. Responsibility sits with the editor.

How to request help or report a barrier. Readers who find content difficult to use can write through contact.php, telephone +62 813 5792 4680 or post a letter to the Jakarta address above. Please include the page address, the problem encountered and the browser or assistive technology used. Reports are acknowledged within 5 working days, and the editorial desk aims to provide the information in an accessible form or a fix timeline within 20 working days. Requests for alternative formats such as large print or plain text are handled without charge.

1. Acknowledgement within 5 working days.
2. Accessible alternative or fix timeline within 20 working days.
3. No charge for alternative formats.

Review log. We record accessibility reviews with dates so readers can follow progress.

1. 1 January 2026: statement published after initial keyboard and contrast checks.
2. 1 June 2026: review of navigation, forms and image descriptions; reporting process clarified.
3. Next review within twelve months or after significant redesign.

Review and change log. This statement is updated whenever a significant accessibility change is made and is reviewed at least annually. If a reader is not satisfied with the response, the matter can be escalated to the editorial lead, who replies in writing within 10 working days.

1. 1 January 2026: first accessibility statement published.
2. 1 June 2026: added testing approach, known limitations and response times.
3. Next review within twelve months.