Accessibility statement

Nebula aims to make its editorial material usable by readers with different abilities, devices and browsing preferences. We use semantic headings, visible focus styles, descriptive alternative text for editorial images, readable contrast and controls that can be reached without a mouse.

Nebula uses the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA as a working reference, while recognising that full conformance is an ongoing task rather than a finished state. Indonesian regulation on disability rights, including Law No. 8 of 2016 on Persons with Disabilities, encourages equal access to information, and the desk treats that principle as part of editorial quality. Readers who use screen readers, magnification, voice control, switch devices or a slow mobile connection are the audience we keep in mind when pages are built and reviewed. Testing combines automated checks with manual review using a keyboard and at least one screen reader on desktop and on a mobile phone. Automated tools find only a share of problems, so the desk treats a clean automated result as a starting point. Reader feedback is the most useful source of information about barriers that tests miss.

1. Scope

This statement applies to Nebula pages and shared navigation published in 2026. Third-party destinations may follow different practices and are outside our direct control.

The statement covers the home page, article and glossary pages, the contact form and the legal pages, in desktop and mobile layouts. It does not cover files hosted by other organisations, such as external journal articles or PDF documents that a link may open. Where Nebula itself publishes a downloadable document, the desk aims to provide a text-based version that works with assistive technology. The statement is based on current versions of widely used browsers on Windows, macOS, Android and iOS. Older browsers may display the pages with fewer visual features, though the text and links should remain usable. Content that was published before 1 January 2026 and carried over is reviewed in the same cycle as new pages.

2. Content structure

Pages use headings in a meaningful order, lists for grouped information and tables only where relationships between data need a table. Links describe their destination rather than relying on vague labels.

Each page has a single main heading followed by section headings that do not skip levels, which lets a screen-reader user move through a page by heading. Link text such as "Read the cardiovascular stamina overview" is preferred to "click here". Data tables, where used, include header cells so that each figure can be matched to its label. Text can be enlarged to 200 percent in a browser without loss of content, and the layout reflows to a single column on narrow screens. Landmarks such as the header, main content and footer are marked so that a reader can jump between regions. Lists are used for grouped items, which lets assistive technology announce the number of entries. Long pages offer a contents list near the top where it helps a reader find a section quickly.

3. Images

Editorial images include descriptive alternative text where they convey information. Decorative treatment is kept separate from the text so readers using assistive technology can follow the same argument.

Alternative text describes what an image shows in a sentence, for example the setting, the activity and the people visible, and avoids starting with the words "image of". Images that add no information are marked so that assistive technology can skip them. If an image carries data, such as a chart, the key finding is also stated in the surrounding text. A reader who finds a missing or unclear description can report the page through contact.php. The desk aims to correct a missing description within 14 days of the report. Images are sized so that they do not hide text on small screens, and they load with fixed dimensions to reduce layout shift. Text is never placed inside an image, so enlarging text or changing colours in the browser affects all of the content.

4. Keyboard access

Navigation and forms are intended to work by keyboard. Focus should remain visible, and the mobile navigation exposes its expanded state to assistive technology.

The Tab key moves forward through links, buttons and form fields in the same order as the visual layout, and Shift plus Tab moves backward. The Enter key activates links and buttons, and the Escape key closes the mobile menu where it is open. The mobile menu button reports whether the menu is expanded or collapsed. There are no keyboard traps, meaning a user can always leave a control using standard keys. A link to skip to the main content is available at the start of each page so that repeated navigation does not need to be tabbed through. Frequently used controls have a target size large enough to press on a touch screen. Readers who rely on voice control can activate a control by speaking its visible label, since visible labels and accessible names match.

5. Motion and colour

Motion is limited and does not carry essential meaning. Colour is paired with headings or text so a reader does not need to distinguish a signal by colour alone.

Text and background colours are chosen to reach at least a 4.5 to 1 contrast ratio for ordinary body text. Links are distinguishable by more than colour, for instance by underline or a clear change on focus. Users who set their system to reduce motion should see minimal animation, and nothing on the site flashes more than three times per second. These choices are reviewed whenever the design changes. Large text is held to a contrast ratio of at least 3 to 1, and interface elements such as form borders and focus outlines are checked against the same threshold. A reader who finds a combination hard to read can report the page and the device, and the desk will review the colours concerned. Print layouts use dark text on a light background regardless of the screen design.

6. Language

The site is published in English. Readers who need a different format may contact the desk and describe the barrier, page and preferred alternative.

Requested alternatives may include a large-print or plain-text copy of an article, a summary read aloud by telephone, or a version with a simplified layout. A request should state the page, the barrier met and the format that would help. The desk aims to acknowledge within 7 business days and to provide the alternative, where practical, within 21 days. Specialist terms are explained in the glossary to help readers who are new to sports science vocabulary. Sentences are kept to a moderate length, and abbreviations are spelled out on first use. Because many readers in Indonesia use English as a second language, the desk avoids idiom where a plain expression is available. A reader who would find a Bahasa Indonesia explanation of a term useful can ask for it through contact.php.

7. Forms

Labels identify contact fields and required information is kept to a minimum. The form confirmation is shown in the page after submission rather than relying only on a transient visual effect.

Each field has a visible label that stays in place while the reader types, and required fields are identified in text and not only by colour. Error messages state which field needs attention and what is expected, for example a valid email address. The confirmation message after sending is placed in the page content so a screen reader announces it. The form does not impose a time limit, so a reader can compose a message at their own pace. Text typed into the form is not stored by Nebula until the message is sent, and it is handled as described in the privacy policy afterwards. A reader who prefers not to use the form can write to the postal address or call the telephone number given on the contact page. The desk replies using the channel the reader chose where that is possible.

8. Known limitations

Some older linked documents or embedded third-party pages may not meet the same standard. We prioritise high-use pages and will improve issues as they are identified. Known limitations include some external PDF documents without a text layer, and some third-party pages that do not support keyboard navigation. Where Nebula links to such a document, the surrounding text describes the content so that a reader can decide whether to open it. The desk can also summarise an external document on request, within 21 days, though this does not replace the original.

9. Feedback

Send accessibility feedback through contact.php or call +62 856 9317 4825. Include the page address, device or assistive technology if known, and the outcome you were trying to achieve. The desk acknowledges feedback within 7 business days and gives a plan or an explanation within 30 days. If a reader is dissatisfied with the response, the editor will review the case again, and the reader may also contact a disability rights organisation or the relevant government office. Feedback is kept for 24 months so that recurring issues can be traced, and it is not shared outside the desk.

10. Review log

This statement was published 1 January 2026 and reviewed 1 October 2026. The next planned review is during the 2027 content cycle, with earlier review if a significant interface changes.

Feedback about accessibility can be sent through contact.php, by post to Jalan Cendrawasih No. 45, Duren Sawit, Jakarta Timur 13440, Indonesia, or by telephone on +62 856 9317 4825. The desk aims to acknowledge feedback within 7 business days, and to report on the planned action within 30 days. This statement was first published on 1 January 2026 and reviewed on 1 October 2026, when keyboard, form and contrast descriptions were rechecked. Future reviews will be dated here, and any newly identified barrier will be described plainly with the intended date of improvement where one is known. The dated entries to date are:

• (a) 1 January 2026: first publication of this statement;
• (b) 1 October 2026: review of keyboard operation, form labelling and contrast, with expanded detail on alternatives and response times.