Accessibility statement
Nenova wants its editorial material to be usable by as many readers as possible. This statement explains the practices used across the 2026 site, the limitations we know about, and how to report a barrier. Accessibility is an ongoing publishing responsibility rather than a one-time certification.
1. Our aim
We aim to provide clear structure, readable contrast, keyboard access, descriptive image alternative text, and language that does not require specialist knowledge. We consider desktop and mobile reading, zoom, screen readers, and different ways of navigating a page.
2. Structure
Pages use headings, landmarks, lists, tables, labels, and link text to communicate purpose. A heading should describe the section that follows. Tables are reserved for relationships that benefit from rows and columns, rather than being used for decoration.
3. Images
Editorial images include descriptive alternative text when they convey information. Decorative repetition may be treated differently so it does not create noise. If an image meaning is unclear or an alt description is inaccurate, tell us the page and we will review it.
4. Keyboard use
Navigation, details controls, forms, and buttons are intended to work without a mouse. A visible focus treatment helps show where a keyboard user is located. Browser extensions, assistive technology, and unusual input devices can expose issues that our normal checks do not reproduce.
5. Contrast and typography
The design uses a dark charcoal text colour on warm light backgrounds and light text on dark bands. Headings use a serif face and body text uses a sans-serif face. Readers can use browser zoom or operating-system text settings; a layout may reflow as it becomes larger.
6. Motion
Nenova avoids decorative animation that is necessary to understand content. The reading progress indicator is not required for navigation. If a movement or transition causes difficulty, tell the desk and we will consider a reduced-motion improvement.
7. Forms
Contact and newsletter forms use labels, required states, and a visible success message after submission. Do not place sensitive medical information in a form. If a form is inaccessible, contact the desk by phone at +62 21 5289 7416 or by post.
8. Known limitations
Third-party links and embedded services may not meet the same standard as Nenova pages. Older articles may have inconsistent wording or image descriptions. We prioritise issues that prevent a reader from understanding a health or safety limitation.
9. Feedback
Send the page address, the task you were attempting, the technology you use if relevant, and the result you expected. We do not require a diagnosis or disability description. We aim to acknowledge feedback within seven days and provide a practical response within 30 days.
10. Alternatives
If a page cannot be accessed, request the article text or an alternate format through contact.php. We will assess the request and protect any personal information included in the conversation. A reasonable alternative may be a plain-text response or a corrected accessible page.
11. Review
The site is reviewed throughout 2026 and after significant template changes. This statement was reviewed on 12 October 2026; the previous review was 1 April 2026. Findings may lead to code, content, design, or editorial process changes.
12. Contact
Accessibility enquiries can be sent to Nenova, Jl. Merdeka Raya No. 45, Gondangdia, Central Jakarta, Jakarta 10350, Indonesia, or by phone at +62 21 5289 7416. Please mention Accessibility in the topic so the message reaches the right desk.
Our current review process includes keyboard-only movement through the main navigation, visible focus checks, heading-order checks, form-label checks, image alternative-text review, and basic testing at enlarged browser zoom. These checks are practical quality controls rather than a statement that every combination of browser, operating system, screen reader, or assistive technology will behave identically.
Some content may come from an independent third-party service. A linked document, embedded player, advertising unit, or external form may have a different accessibility experience and its own support route. We will identify a known limitation where practical and can help provide a plain-text route to the relevant information when a reader tells us what is needed.
Readers can request an article in a different format, report a missing label, describe a focus problem, or explain that contrast, language, motion, captions, or reading order creates a barrier. Please include the page address, the task you were attempting, the device or assistive technology if known, and a preferred contact method. Do not include medical records or unnecessary personal information.
Accessibility reports are acknowledged within five business days. We aim to assess a straightforward content correction within 15 business days and to provide an update within 30 days for a technical issue that requires investigation. A temporary alternative may be offered while a broader site fix is being considered.
Contact Nenova at Jl. Merdeka Raya No. 45, Gondangdia, Central Jakarta, Jakarta 10350, Indonesia, phone +62 21 5289 7416. If the response does not resolve a barrier, a reader may request escalation to the site publisher and may contact an appropriate local accessibility or consumer authority. This statement was reviewed on 12 October 2026; future revisions will be dated and will note material changes.
Our review covers the public navigation, article templates, forms, headings, links, focus order, text resizing, color contrast, image alternatives, and the reading experience on common mobile and desktop browsers. It also considers whether a reader can understand the purpose of a control without relying only on color, pointer movement, sound, or animation. These checks are repeated when substantial templates or publishing components change.
Known limitations may arise from older articles, third-party embeds, downloadable documents, advertising components, or browser and assistive-technology combinations that Nenova cannot reproduce. A limitation does not make a reader responsible for solving the barrier alone. We will consider a plain-text explanation, an accessible replacement, or another practical route to the same information.
When reporting a barrier, please share the page URL, the action that could not be completed, the type of device or assistive technology if known, and a safe way to reply. Please avoid sending health information, identity documents, passwords, or unrelated personal details. A report is used for accessibility review and is not treated as a request for marketing.
Accessibility reports are acknowledged within five business days. Straightforward content fixes are targeted for review within 15 business days, while technical issues may require a progress update within 30 days. Records of a resolved report are normally kept for up to 24 months so recurring issues can be compared and the response can be documented.
Contact Nenova at Jl. Merdeka Raya No. 45, Gondangdia, Central Jakarta, Jakarta 10350, Indonesia, phone +62 21 5289 7416. The statement was reviewed on 12 October 2026; a material change to the testing approach, known limitations, or contact process will be recorded with a new date.
Accessibility work also considers the language of notices, the clarity of error messages, the order in which a keyboard user encounters controls, and whether a reader can distinguish a link from surrounding text. We avoid relying on color alone for status and keep essential instructions available as text. When a page contains a table, the headings and relationships should remain understandable when the layout changes on a narrow screen.
Our records of accessibility requests normally include the page, issue category, date received, response, and closure date, but not unnecessary personal details. Records are retained for up to 24 months to help identify recurring barriers and review whether a correction worked. The policy was reviewed on 12 October 2026 and is informed by applicable Indonesian requirements and widely used WCAG principles.