Accessibility Statement

Reviewed 1 September 2026. Xyjecta aims to make editorial information usable across devices, assistive technologies, and varied reading preferences. This statement is written with our core readership in mind, adults aged 35 and beyond, a group in which presbyopia, mild hearing changes, and varied familiarity with assistive technology are all reasonably common, and where accessible defaults benefit a large share of visitors rather than a narrow minority. We treat accessibility as an ongoing editorial and technical responsibility rather than a one-time project, and this page is reviewed on the same cadence as our other policy pages. Where a specific barrier is reported, we aim to treat it as seriously as a factual correction would be treated under our editorial policy. We also recognise that accessibility needs can change for an individual reader over time, for example as eyesight or hand strength shifts with age, which is one reason we favour durable, standards-based approaches such as adjustable text size over a fixed design calibrated to a single assumed reading condition.

1. Our Aim

We use semantic headings, readable contrast, descriptive image alternatives, keyboard-friendly controls, and responsive layouts. Semantic headings mean that each page follows a logical heading order, allowing a reader using a screen reader to navigate by section rather than scanning the entire page linearly. Readable contrast is applied consistently across both the lighter editorial background and the darker charcoal sections of the site, so that heading and body text remain legible in either context. Responsive layouts mean that articles, tables, and navigation remain usable on a small phone screen as well as a larger desktop display, without requiring horizontal scrolling to read ordinary text. We treat these as baseline expectations for every new page added to the site rather than aspirational goals reserved for a future redesign, and a new page that does not meet them is not considered ready to publish.

2. Content

Articles are written in plain English where possible, with definitions for specialist terms and visible link labels. Where a technical term such as a specific training concept is used, we aim to define it in context or link to the relevant glossary entry rather than assuming prior familiarity. Visible link labels mean that a link's text describes its destination, such as naming the article it leads to, rather than relying on a vague phrase like "click here" that provides little information out of context. We also aim to keep paragraph and sentence length reasonable throughout long-form guides, recognising that very dense text can be harder to process for some readers regardless of assistive technology used. Our glossary, described on glossary.php, exists specifically to support this aim, giving a reader a single place to check an unfamiliar term without having to leave the article they are currently reading for an external search.

3. Images

Editorial images include descriptive alternative text. Decorative choices should not interfere with comprehension. Descriptive alternative text is written to convey what a sighted reader would see and why the image was chosen for that section, rather than a generic label such as "photo" or a filename. Where an image is purely decorative and adds no informational value, we aim to mark it in a way that allows assistive technology to skip over it rather than announcing an unhelpful description. We review alternative text as part of routine editorial maintenance, consistent with the corrections process described in our disclaimer. Where an image accompanies a specific instructional point, such as illustrating a described stretch or a piece of equipment mentioned in an article, the alternative text aims to convey that specific detail rather than a generic scene description, so a reader relying on a screen reader receives comparable information to a sighted reader glancing at the same image.

4. Keyboard Use

Navigation and forms are intended to work without a mouse. Focus should remain visible during movement through a page. This means a reader should be able to tab through the main navigation menu, open a mobile menu, and complete the contact form using only a keyboard, without a control becoming unreachable or trapped. A visible focus indicator, such as an outline around the currently selected link or field, helps a keyboard user understand where they are on the page at any given moment. Where we identify a control that does not behave correctly with keyboard-only navigation, we treat it as a defect to be corrected rather than an acceptable limitation. We test newly added interactive elements, such as a filter control on our guides page, with keyboard-only navigation before publishing them, rather than relying solely on mouse-based testing during development.

5. Motion

The site uses minimal motion and does not require animation to access information. Where a subtle transition is used, such as a hover effect on a content card, it is kept brief and is not essential to understanding or using the page, so a reader with a browser or operating-system setting that reduces motion will not miss any functional information. We do not use auto-playing video with sound or rapidly flashing content, both of which can pose a barrier or a health risk for some readers. Any future addition of video content, such as the video-style sections referenced on the homepage, will be reviewed against this principle before publication. Where our homepage uses a video-placeholder style section, it is presented as a static image with a description rather than genuinely auto-playing footage, consistent with this cautious approach to motion.

6. Contrast

Text and controls use a palette selected for legibility on paper-toned and charcoal backgrounds. The off-white background used for most editorial content is paired with a deep charcoal text colour chosen to provide a comfortable reading contrast over long articles. Where a section uses the darker charcoal background, heading and body text within that section is set to a light, legible colour rather than inheriting the darker tone used elsewhere on the page. The deep teal accent colour used for links and buttons is applied against backgrounds chosen to keep it clearly distinguishable from surrounding text. We periodically check our colour choices against commonly used contrast guidance, and where a new accent or background combination is introduced in a future design update, it is checked for adequate contrast before being applied site-wide rather than after readers begin reporting difficulty.

7. Forms

Labels identify fields, required information is indicated, and successful contact submission is announced on the page. Each field on the contact form, such as name, email, and message, carries a visible label rather than relying solely on placeholder text that disappears once a reader starts typing. Where a field is required, this is indicated in a way that does not rely on colour alone, so a reader who cannot distinguish certain colours is not left guessing which fields must be completed. On successful submission, a confirmation message is displayed on the page so a reader using a screen reader is informed that the message was sent, rather than being left uncertain about whether the action succeeded. Where a field is left incomplete or entered incorrectly, an error message is associated clearly with that specific field rather than presented only as a general notice at the top of the form, so a reader can identify and correct the issue without re-reading every field.

8. Limitations

Third-party pages and older content may not meet every current accessibility expectation. A linked external resource, for example, is built and maintained by its own operator and is outside our ability to modify, even where we would prefer a more accessible presentation. Older articles published before a particular accessibility improvement was adopted site-wide may not yet reflect every current practice, and we prioritise updates to these pages as part of ongoing editorial maintenance rather than all at once. We do not consider these limitations a reason to avoid stating our aim clearly, and we welcome a specific report identifying an older page that needs attention. Where resource constraints mean we cannot address every older page immediately, we prioritise the pages with the highest readership, reasoning that an accessibility improvement there benefits the largest number of readers for the effort involved.

9. Feedback

Report a barrier with the page address and assistive technology details to Jalan Garuda No. 12, Kebon Sirih, Menteng, Jakarta Pusat 10340, Indonesia. Including the specific page address, the assistive technology or browser setting in use, and a brief description of what happened helps us reproduce and address the barrier more quickly than a general comment about the site. A report can also be sent through the ordinary contact form described on contact.php, with a note indicating that it concerns accessibility so it can be prioritised appropriately. We treat an accessibility report with the same seriousness as a factual correction request described in our disclaimer, since both affect whether a reader can actually use the content we publish. Where a report describes a barrier we are not immediately able to reproduce, we may ask a brief follow-up question about the reader's specific browser or assistive technology version, since behaviour can vary meaningfully between versions of the same tool.

10. Review

We log feedback and review this statement annually. The current review date is 1 September 2026; phone support is +62 21 6853 0927. Logged feedback is used to prioritise which pages receive attention first during the next scheduled review, rather than being treated as a one-off response with no lasting record. The 1 September 2026 review confirmed the practices described above remained an accurate reflection of the site's current implementation across its full set of pages. We expect to conduct the next review around the same point in 2027, and sooner if a significant redesign or new feature, such as an interactive tool, is introduced to the site. Where an interim accessibility fix is made between scheduled annual reviews, in response to a specific reader report, we note it internally so the next full review can confirm the fix remains effective rather than treating it as a closed matter requiring no further attention.