Accessibility statement
Genese aims to make its English-language editorial resource usable by people with different abilities, devices and browsing preferences. This statement applies from 5 October 2026.
1. Our aim
We work toward clear structure, readable contrast, keyboard access and meaningful link text across the site. For example, a link reading "read the recovery article" rather than a bare "click here" helps a screen-reader user understand a link's destination out of context. The practical consequence is that readers using assistive technology can navigate the site's articles, glossary and contact form with a similar level of understanding as readers using a conventional browser. An edge case involves older browser versions that may not support every modern layout feature consistently; in that situation we aim for the content to remain readable even if some visual styling is simplified. This aim guides ongoing review rather than describing a single finished state.
- a) Link text describes its destination rather than relying on generic phrases.
- b) Core content remains readable even where a browser does not support every modern styling feature.
- c) This aim is reviewed on an ongoing basis rather than treated as a one-time completed task.
-
2. Structure
Pages use headings, navigation landmarks, lists and tables where those structures help understanding. For example, a comparison of training approaches is presented as an actual table with header cells, rather than as a visually aligned block of text, so assistive technology can announce row and column relationships correctly. The practical consequence is that a reader using a screen reader can jump directly between headings to find a relevant section rather than listening through an entire page sequentially. An edge case involves a long glossary page; its definitions are structured as a list with clear terms so a reader can scan or navigate by list item rather than by paragraph alone. This structural approach is applied consistently across articles, policy pages and the glossary.
- a) Comparative information is marked up as a genuine table rather than visually styled text.
- b) Heading structure allows navigation directly to a relevant section.
- c) List-based content, such as the glossary, is structured for scanning and navigation.
-
3. Images
Editorial images include descriptive alternative text so the visual subject is available in words. For example, a photograph accompanying an endurance article might carry alternative text describing a runner on a track at dawn rather than a generic label such as "photo" or "image one." The practical consequence is that a reader using a screen reader receives roughly the same contextual information as a sighted reader glancing at the photograph. An edge case involves purely decorative imagery that adds no informational content; where that occurs, the image is marked so assistive technology can skip past it without interrupting the reading flow. We review alternative text when images are added or replaced to keep descriptions accurate and specific.
- a) Alternative text describes the specific visual subject rather than using a generic label.
- b) Purely decorative images are marked so they do not interrupt assistive-technology reading flow.
- c) Alternative text is reviewed whenever an image is added or replaced.
-
4. Keyboard use
Links, controls, form fields and the cookie choice should be reachable using a keyboard or assistive technology. For example, a reader navigating with the Tab key should be able to move through the main navigation menu, into an article, down to the contact form fields, and reach the cookie banner's accept or reject buttons, all without needing a mouse. The practical consequence is that a visitor with a motor impairment or a preference for keyboard navigation is not excluded from any core function of the site. An edge case involves the visible focus indicator, which should remain clearly visible as a reader tabs between elements so they always know which control is currently active. We test primary navigation paths periodically to confirm keyboard reachability remains intact after design updates.
- a) Full keyboard navigation covers menus, articles, the contact form and the cookie banner.
- b) A visible focus indicator helps a keyboard user track their current position on the page.
- c) Primary navigation paths are periodically tested for keyboard reachability after updates.
-
5. Contrast
Text and backgrounds are selected for legibility, with special care on dark footer and hero areas. For example, white or light-neutral text is used on the darker footer background rather than a mid-tone grey that could blend into the background for a reader with low vision. The practical consequence is that a reader with reduced contrast sensitivity, a common change with age, can still read footer links, the address and the phone number clearly. An edge case involves bright outdoor lighting on a mobile screen, where lower-contrast text can become difficult to read regardless of a device's own brightness setting; our contrast choices are intended to remain legible under a reasonable range of viewing conditions. We review contrast whenever a new background colour or section style is introduced.
- a) Light text on the darker footer is chosen to remain legible rather than blending into the background.
- b) Contrast choices account for age-related changes in contrast sensitivity among readers.
- c) Contrast is reviewed whenever a new background colour or section style is introduced.
-
6. Motion
Genese avoids decorative motion that is necessary for understanding. Browser preferences may further reduce effects. For example, an interactive diagram would convey its underlying information in static form as well, so a reader who finds animation distracting or disorienting does not lose access to the content itself. The practical consequence is that no article depends on a moving element to be understood; any animation present is supplementary rather than load-bearing. An edge case involves readers who experience vestibular discomfort from certain motion effects; where a browser-level reduced-motion preference is set, we aim for that preference to limit non-essential animation on the site. We do not use flashing or rapidly repeating visual effects anywhere on the site.
- a) No article depends on animation to convey its core information.
- b) Browser-level reduced-motion preferences are respected for non-essential animation where applicable.
- c) Flashing or rapidly repeating visual effects are not used anywhere on the site.
-
7. Documents
Information is published as web content where possible, rather than requiring a separate inaccessible file. For example, an article's full content appears directly on its page as readable text rather than being locked inside a downloadable image-based file that assistive technology cannot interpret. The practical consequence is that a reader does not need a particular additional program or viewer to access the substance of an article. An edge case involves a future downloadable resource, such as a printable summary; if introduced, we aim to provide its core information in accessible web-page form as well, rather than exclusively as a file. Where a document format is unavoidable, we aim to describe its content in the surrounding page text.
- a) Article content is published as readable web text rather than locked inside an image-based file.
- b) Any future downloadable resource would also have its core content available as a web page.
- c) Where a document format is unavoidable, surrounding text describes its content.
-
8. Feedback
Tell us which page, device and barrier you encountered. Specific details help us reproduce and correct the issue. For example, a report noting that a specific button on the contact page was unreachable using a particular screen reader on a specific phone model gives us enough detail to test that exact combination. The practical consequence of specific reporting is a faster, more accurate fix compared with a general comment that a page "did not work." An edge case involves a barrier that appears only in one browser version; identifying the browser and its version helps us reproduce the issue in testing before confirming a correction has resolved it. We welcome feedback from readers using any assistive technology, device or browser combination.
- a) Naming the specific page, device, browser and assistive technology speeds up an accurate fix.
- b) Browser-specific barriers are easier to resolve once the exact browser and version are known.
- c) Feedback is welcomed regardless of which assistive technology or device combination is used.
-
9. Response
We aim to acknowledge accessibility reports within seven days and assess practical fixes in the next editorial maintenance cycle. For example, a report submitted on a Monday would typically receive an acknowledgement by the following Monday at the latest, confirming that it has been received and is being reviewed. The practical consequence is that a reader knows their report has not been overlooked even if a full technical fix takes longer to implement. An edge case involves a report describing a barrier that requires a broader layout change; such a fix may be scheduled across more than one maintenance cycle, and we aim to update the reader on progress where contact details were provided. Reports that identify a genuine, reproducible barrier are prioritised over general stylistic suggestions.
- a) Acknowledgement of a report is targeted within seven days of receipt.
- b) Fixes requiring broader layout change may span more than one maintenance cycle.
- c) Reproducible barriers are prioritised ahead of general stylistic suggestions.
-
10. Contact
Write to Genese at Jalan Kemang Raya No. 12, Mampang Prapatan, Jakarta Selatan, 12730, DKI Jakarta, Indonesia, or call (021) 7586-9172. For example, a reader who finds it easier to describe an accessibility barrier by phone rather than in writing is welcome to call during Jakarta business hours and describe the issue verbally. The practical consequence of offering both channels is that readers can choose whichever method suits their own needs and preferences. An edge case involves a reader contacting us from a significantly different time zone; messages are reviewed on the next working day in Jakarta regardless of when they are sent. Written correspondence by post to the address above is also accepted as an alternative to a phone call or the contact form.
- a) Both phone and written contact are available, and readers may choose whichever suits them.
- b) Messages from other time zones are reviewed on the next Jakarta working day.
- c) Postal correspondence to the address above is accepted as an alternative channel.
-
11. Revision log
5 October 2026: statement updated for the current navigation, image descriptions, cookie banner and responsive layout. For example, this revision reflected a review of alternative text across recently added article images and a check of keyboard reachability for the cookie banner's accept and reject controls. The practical consequence of logging this update is that a returning reader can see when the statement's substance was last reviewed, separate from the general site publication date. An edge case involves a future minor wording correction that does not change the substance of any numbered section; such a correction may not warrant a new dated entry on its own. Material changes to how accessibility is addressed on the site will be added to this log with their own date going forward.
- a) 5 October 2026: current version, covering navigation, image descriptions, the cookie banner and responsive layout.
- b) Minor wording corrections without substantive change may not require a new dated entry.
- c) Future material changes to accessibility practice will be logged here with their own date.