Accessibility at Evance

Evance aims to make its editorial website readable and usable for people with different abilities, devices and connection speeds. We treat accessibility as ongoing work rather than a completed badge. This statement explains the current approach and how to report a barrier.

Our working reference is the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, which we use as a goal and not as a claim of full conformance. Reading is the main activity on the site, so we give most attention to text, structure and forms. Testing is done by editors on desktop and mobile browsers and with keyboard-only navigation. Findings are recorded and revisited at each review.

Checks include tabbing through every page without a mouse, enlarging text to 200 percent, reading pages with a screen reader on a sample basis, and viewing them on a phone with a slow connection. Pages are also reviewed with images turned off to see whether the text still makes sense. We have not commissioned an external audit, so this statement describes our own testing and should be read as such.

1. Our scope

This statement covers pages published by Evance, navigation, forms, cookie controls, headings, links and available media. Third-party destinations may have different accessibility arrangements and are outside our direct control.

That includes external research journals, government pages and embedded tools. When we link to a document in a format that is hard to use with assistive technology, we try to say so. If you cannot use a source we reference, ask and we will describe its key points in plain text where permitted. Older articles are reviewed in turn, and those with the greatest readership are checked first.

The statement also covers the policy pages, the contact form and the cookie notice, since these are the parts of the site a reader must be able to use to exercise his choices. Content supplied by outside contributors is checked against the same standard before publication. Where a barrier is found in older material, we record it with the date found and the date fixed.

2. Structure

We use headings in a meaningful order, semantic landmarks, descriptive links and labels for form controls. The page title identifies the subject, while the navigation provides routes to major sections and policies.

Each page has one main heading, followed by subheadings that do not skip levels. Landmarks such as header, main, navigation and footer help screen-reader users move quickly. Link text describes the destination, so that a phrase like read the methodology is used in preference to click here. Form fields have visible labels and, where an error occurs, the message states which field needs attention.

Error messages are written in plain words, for example that the email address looks incomplete, and they stay on the page until the field is corrected. After a message is sent through the contact form, a confirmation appears in the page itself, so a reader does not need to rely on a colour change or a brief pop-up. Tables are used only for data and include header cells, so that a screen reader can announce which column a figure belongs to.

• (a) Page titles: unique and descriptive of each page.
• (b) Headings: ordered, with no decorative use.
• (c) Forms: labelled fields, a clear confirmation message after sending.
• (d) Language: each page declares English as its language so that screen readers choose the right voice.
• (e) Skip routes: a way to jump past repeated navigation to the main content.

3. Visual design

Our palette uses dark charcoal text on light backgrounds and a sage accent. Text can be enlarged with browser controls. Focus indicators and responsive layouts are intended to support keyboard and small-screen use.

Charcoal text on an off-white background gives a contrast ratio well above the 4.5:1 minimum for body text. The sage accent is used for links and buttons together with underlines or labels, so colour is never the only signal. Text is set at a comfortable size and line height and can be enlarged to 200 percent without loss of content. Layouts reflow to a single column on narrow screens, which helps readers using zoom or large system fonts.

Line length is kept within a comfortable range so that readers with dyslexia or low vision do not lose their place. Body text uses a plain, widely available type style with generous spacing between lines and paragraphs. Where white text appears on the dark footer, it is a solid light colour rather than a semi-transparent one, so that contrast does not depend on what sits behind it. Readers who use a high-contrast mode in their operating system should find the layout still usable.

4. Images

Editorial images include descriptive alternative text where they convey information. Decorative details are not intended to carry meaning. If an image description is unclear, please tell us the page and the wording you encountered.

Photographs that illustrate a concept have a description of what is shown, such as a man performing a hip hinge with a kettlebell in a bright studio. Images that are purely decorative are given an empty description so that screen readers skip them. Charts and tables, where they appear, have a text summary or are presented as real tables with headers. If an image carries information that is not repeated in the text, that is a fault we want to fix.

Descriptions aim to be short and specific, usually a single sentence, and they avoid phrases such as image of. They do not describe a person's body in a way that suggests a judgement about health or ability. When a photograph is used to set a scene rather than to inform, the surrounding text carries the meaning. Reports about unclear descriptions are treated as accessibility reports and answered in the same time frame.

5. Keyboard and touch

Navigation and contact controls are designed to work without a mouse. The mobile menu exposes the same destinations as the desktop navigation. Touch targets are given practical spacing, though device settings can affect the result.

Interactive items such as the menu button, the cookie notice buttons and form controls receive keyboard focus in a logical order, and a visible outline shows where focus is. The Escape key closes the mobile menu, and the cookie notice can be dismissed without a pointing device. Buttons and links have a target area large enough for a fingertip. If you find a control that cannot be reached with the Tab key, please report the page and the control's name.

Menus that open and close announce their state to assistive technology, so a screen-reader user hears whether the navigation is expanded or collapsed. When the mobile menu opens, focus remains inside it until it is closed, and returns to the menu button afterwards. Speech-recognition users can activate links by their visible text, because the accessible name of a control matches what is shown on screen.

6. Motion and media

Evance does not require autoplay video for core content. Readers may use browser or operating-system preferences to reduce motion. Future interactive features will be reviewed for pause, stop and keyboard considerations.

Animations on the site are limited to subtle hover effects and are disabled when the operating system requests reduced motion. Nothing on the site flashes more than three times per second. If video or audio is added, it will start only when the reader chooses to play it, will offer captions or a transcript, and will not carry information that is unavailable in text.

Any new interactive element would be tested with the keyboard and a screen reader before release. If it cannot meet that bar, we would publish the information in plain HTML instead. Time limits are not used on pages, so a reader can take as long as needed with a form or an article.

7. Documents

We prefer accessible HTML for editorial information. If a downloadable document is introduced, we will identify its format and provide an HTML alternative where reasonably possible.

A downloadable file would be labelled with its type and approximate size, and would use real headings, a document title and a defined reading order. If a document cannot be made accessible in a reasonable time, we will offer the content by another route, such as a text email or a telephone explanation. Requests for another format are answered within ten business days.

Alternative formats we can provide include a plain-text email, a large-print letter posted to your address, or a telephone reading of the page. There is no charge for these. We keep the request only as long as needed to complete it, and no longer than the 24 months stated for accessibility reports.

8. Known limits

Older external links, browser-specific rendering, third-party tools and some complex data displays may not work equally well for everyone. We record recurring issues and prioritize barriers that block essential information.

Examples of current limits are comparison tables that require horizontal scrolling on small phones, a few external diagrams without detailed text descriptions, and language switching, since the site is published in English only. Readers using older browsers may see simpler layouts. We prioritise problems by how much they prevent a reader from getting the information, then by how many pages they affect.

• (a) Tables: wide comparison tables scroll sideways on narrow screens; a text summary is given above them.
• (b) External material: journals and PDFs we link to may not be tagged for screen readers.
• (c) Language: content is in English only, and no automatic translation is offered.

9. Reporting a barrier

Contact Evance at Jalan Anggrek Raya No. 15, Kemang, Jakarta Selatan 12730, Indonesia or +62 817 9345 1820. Include the page, device, browser, assistive technology if relevant and the outcome you expected. Do not send sensitive medical information.

You can describe the issue in your own words, and you do not need to name a disability. If it is easier, call and we will write the report with you. We use the details only to understand and fix the problem and keep the report for 24 months, in line with the privacy policy. If we cannot fix a barrier promptly, we will offer an alternative such as sending the text of the page or a call to talk through the content.

Reports are logged with the date, the page and the type of barrier, and the person who receives it passes it to the editor responsible for templates. Fixes that need a template change are batched into the next scheduled update, normally within 60 days, while a barrier that blocks a form or a policy page is handled sooner. We tell the reporter when the issue is resolved if contact details were provided.

10. Review

This statement was published 1 January 2026 and reviewed 1 October 2026. We aim to acknowledge reports within five business days and to explain the next step or a reasonable workaround.

If you are not satisfied with our response, you may write to us again asking for a second review by a different staff member, or you may contact the Indonesian authority responsible for disability rights and digital services. Reviews are carried out at least once a year and after any major change to templates.

The annual review compares the reports received during the year with the fixes made and notes which barriers remain open. Open items are listed internally with a target date and are checked again at the next review. The aim is for this statement to describe the site as it is, including its faults, rather than as we would like it to be.

• 1 January 2026: statement first published.
• 1 October 2026: annual review; keyboard, motion and document sections expanded.