Accessibility statement

1. Commitment

In the area of commitment, Caban aims to make its editorial pages usable by people with different abilities, devices, and browsing preferences. We use semantic headings, readable line lengths, visible focus states, descriptive link text, labels for fields, and alternative text for editorial images relevant to this part of the site. The site is reviewed as part of ordinary content maintenance, but accessibility in relation to commitment is a continuing practice rather than a claim of perfection.

Readers evaluating our approach to commitment can enlarge text, use keyboard navigation, reduce motion in their operating system, or use assistive technology. If this section of the site, covering commitment, creates a barrier, please tell us what page was involved and what would help. We will assess the report and record practical improvements without requesting unnecessary personal information.

Our commitment follows the general spirit of the Web Content Accessibility Guidelines at a conformance level we treat as a working target rather than a certified status, since we have not undergone formal third-party conformance testing. We review accessibility considerations whenever a new page template is introduced, such as the timeline layout used on the about page, rather than only at the time of an annual audit. This commitment extends to readers using older devices common in parts of Indonesia with slower mobile connections, which is why we keep page weight and script usage modest. Accessibility work is prioritized alongside editorial corrections, meaning a reported barrier is treated with similar urgency to a factual error in an article. We expect this statement to evolve as browsing technology and reader feedback change over time.

2. Structure

In the area of structure, Caban aims to make its editorial pages usable by people with different abilities, devices, and browsing preferences. We use semantic headings, readable line lengths, visible focus states, descriptive link text, labels for fields, and alternative text for editorial images relevant to this part of the site. The site is reviewed as part of ordinary content maintenance, but accessibility in relation to structure is a continuing practice rather than a claim of perfection.

Readers evaluating our approach to structure can enlarge text, use keyboard navigation, reduce motion in their operating system, or use assistive technology. If this section of the site, covering structure, creates a barrier, please tell us what page was involved and what would help. We will assess the report and record practical improvements without requesting unnecessary personal information.

Each article follows a single top-level heading for the page title, followed by nested subheadings that reflect the logical order of the content rather than being chosen for visual size alone. Reading order in the underlying markup matches the visual order a sighted reader would follow, which matters for anyone using a screen reader or a browser extension that reads content aloud. Landmark regions such as the main content area, navigation, and footer are marked so that assistive technology users can jump directly to the section they need. Paragraph length is kept moderate and line length is constrained by the site's container width to support comfortable reading for people with certain cognitive or visual conditions. We avoid relying on color alone to convey meaning, such as marking a required form field with text in addition to any color change.

3. Keyboard access

In the area of keyboard access, Caban aims to make its editorial pages usable by people with different abilities, devices, and browsing preferences. We use semantic headings, readable line lengths, visible focus states, descriptive link text, labels for fields, and alternative text for editorial images relevant to this part of the site. The site is reviewed as part of ordinary content maintenance, but accessibility in relation to keyboard access is a continuing practice rather than a claim of perfection.

Readers evaluating our approach to keyboard access can enlarge text, use keyboard navigation, reduce motion in their operating system, or use assistive technology. If this section of the site, covering keyboard access, creates a barrier, please tell us what page was involved and what would help. We will assess the report and record practical improvements without requesting unnecessary personal information.

Every interactive element on the site, including navigation links, the mobile menu toggle, the cookie banner buttons, and form fields, can be reached and activated using the Tab and Enter keys without requiring a mouse. Focus order follows the visual layout of the page so that tabbing through a page does not jump unpredictably between unrelated sections. A visible focus outline is preserved around the active element rather than removed for stylistic reasons, which helps a keyboard user track their position on the page. We test new page layouts, such as a table or a multi-column card grid, by navigating them with a keyboard before publishing. If a keyboard trap or an unreachable control is reported, it is treated as a priority fix rather than a cosmetic issue.

4. Contrast and type

In the area of contrast and type, Caban aims to make its editorial pages usable by people with different abilities, devices, and browsing preferences. We use semantic headings, readable line lengths, visible focus states, descriptive link text, labels for fields, and alternative text for editorial images relevant to this part of the site. The site is reviewed as part of ordinary content maintenance, but accessibility in relation to contrast and type is a continuing practice rather than a claim of perfection.

Readers evaluating our approach to contrast and type can enlarge text, use keyboard navigation, reduce motion in their operating system, or use assistive technology. If this section of the site, covering contrast and type, creates a barrier, please tell us what page was involved and what would help. We will assess the report and record practical improvements without requesting unnecessary personal information.

Body text uses a dark charcoal tone against a light background designed to exceed a 4.5 to 1 contrast ratio for standard text and a 3 to 1 ratio for larger headings, consistent with widely used accessibility guidance. Font sizing uses relative units where practical so that a reader's browser-level zoom or text-size setting is respected rather than overridden by a fixed pixel value. Line height is set for comfortable reading rather than tightly compressed, which particularly helps readers with dyslexia or low vision. We avoid placing body text directly over a busy photographic background without a solid or near-solid panel behind it to preserve legibility. Where an accent color such as the site's copper tone is used for emphasis, it is paired with sufficient contrast against its background rather than relied upon as the sole indicator of meaning.

5. Images and alternatives

In the area of images and alternatives, Caban aims to make its editorial pages usable by people with different abilities, devices, and browsing preferences. We use semantic headings, readable line lengths, visible focus states, descriptive link text, labels for fields, and alternative text for editorial images relevant to this part of the site. The site is reviewed as part of ordinary content maintenance, but accessibility in relation to images and alternatives is a continuing practice rather than a claim of perfection.

Readers evaluating our approach to images and alternatives can enlarge text, use keyboard navigation, reduce motion in their operating system, or use assistive technology. If this section of the site, covering images and alternatives, creates a barrier, please tell us what page was involved and what would help. We will assess the report and record practical improvements without requesting unnecessary personal information.

Every editorial photograph carries a descriptive alternative text written to convey the specific scene, such as a man performing a kettlebell swing with correct hip-hinge form, rather than a generic label like "photo" or "image one". Purely decorative graphic elements are marked so that assistive technology does not announce them as meaningful content and interrupt the reading flow unnecessarily. Where a chart or diagram conveys data, we describe the key takeaway in the surrounding text so the information is not available only through the visual alone. We review alternative text when an image is replaced or an article is substantially revised, since a new photograph requires new, accurate description. Readers who find an image with missing, generic, or inaccurate alternative text are encouraged to point us to the specific article so it can be corrected.

6. Motion and scripts

In the area of motion and scripts, Caban aims to make its editorial pages usable by people with different abilities, devices, and browsing preferences. We use semantic headings, readable line lengths, visible focus states, descriptive link text, labels for fields, and alternative text for editorial images relevant to this part of the site. The site is reviewed as part of ordinary content maintenance, but accessibility in relation to motion and scripts is a continuing practice rather than a claim of perfection.

Readers evaluating our approach to motion and scripts can enlarge text, use keyboard navigation, reduce motion in their operating system, or use assistive technology. If this section of the site, covering motion and scripts, creates a barrier, please tell us what page was involved and what would help. We will assess the report and record practical improvements without requesting unnecessary personal information.

The site uses minimal animation, limited mainly to subtle hover effects on cards and buttons that respect a reader's operating-system preference for reduced motion where that signal is available. We avoid auto-playing video with sound, flashing content, or animations that could trigger discomfort for a reader sensitive to motion. JavaScript is used for small enhancements such as the mobile menu toggle and the cookie-choice banner, and core reading content remains accessible even if a script fails to load. We do not use intrusive interstitials or pop-ups that trap focus and prevent a reader from reaching the article content. Scripts are kept lightweight to support consistent performance on lower-powered devices and slower mobile connections.

7. Forms

In the area of forms, Caban aims to make its editorial pages usable by people with different abilities, devices, and browsing preferences. We use semantic headings, readable line lengths, visible focus states, descriptive link text, labels for fields, and alternative text for editorial images relevant to this part of the site. The site is reviewed as part of ordinary content maintenance, but accessibility in relation to forms is a continuing practice rather than a claim of perfection.

Readers evaluating our approach to forms can enlarge text, use keyboard navigation, reduce motion in their operating system, or use assistive technology. If this section of the site, covering forms, creates a barrier, please tell us what page was involved and what would help. We will assess the report and record practical improvements without requesting unnecessary personal information.

The contact form associates a visible label with every field using proper markup, so a screen reader announces the purpose of each field rather than leaving a user to guess from placeholder text alone. Required fields are indicated with both a visual marker and accessible text, and an error, such as a missing email address, is described in text near the relevant field rather than communicated only through a color change. Submitting the form produces a clear on-screen confirmation message so a reader using assistive technology knows the message was sent successfully. We avoid time limits on completing the contact form, recognizing that some readers need additional time to compose a message. Field order follows a logical sequence from name through message, matching how a reader would naturally think through providing the information.

8. Tables and links

In the area of tables and links, Caban aims to make its editorial pages usable by people with different abilities, devices, and browsing preferences. We use semantic headings, readable line lengths, visible focus states, descriptive link text, labels for fields, and alternative text for editorial images relevant to this part of the site. The site is reviewed as part of ordinary content maintenance, but accessibility in relation to tables and links is a continuing practice rather than a claim of perfection.

Readers evaluating our approach to tables and links can enlarge text, use keyboard navigation, reduce motion in their operating system, or use assistive technology. If this section of the site, covering tables and links, creates a barrier, please tell us what page was involved and what would help. We will assess the report and record practical improvements without requesting unnecessary personal information.

Where a comparison table appears, such as one contrasting training approaches, column and row headers are marked properly so a screen reader can announce the relationship between a header and its corresponding cell. Link text is written to describe its destination in context, such as "read the mobility guide" rather than an ambiguous "click here" repeated across a page. We avoid using a URL alone as the visible link text, since that is difficult to parse when read aloud. External links that open in a new tab are indicated in the surrounding text so a reader is not surprised by an unexpected context change. Tables are kept to a reasonable number of columns so they remain usable on a narrow mobile screen without excessive horizontal scrolling.

9. Assistive technology

In the area of assistive technology, Caban aims to make its editorial pages usable by people with different abilities, devices, and browsing preferences. We use semantic headings, readable line lengths, visible focus states, descriptive link text, labels for fields, and alternative text for editorial images relevant to this part of the site. The site is reviewed as part of ordinary content maintenance, but accessibility in relation to assistive technology is a continuing practice rather than a claim of perfection.

Readers evaluating our approach to assistive technology can enlarge text, use keyboard navigation, reduce motion in their operating system, or use assistive technology. If this section of the site, covering assistive technology, creates a barrier, please tell us what page was involved and what would help. We will assess the report and record practical improvements without requesting unnecessary personal information.

We test key page templates periodically with a screen reader and with keyboard-only navigation to check that headings, landmarks, and interactive elements behave as expected. We also consider how the site performs with a browser's built-in reading mode or text-only view, since some readers prefer these simplified presentations. Where a third-party embed, such as a map or a video player, is used in the future, we intend to evaluate its accessibility before publishing it rather than assuming it meets the same standard as the rest of the site. We do not currently track which specific assistive technology or browser configuration an individual visitor uses, consistent with our general approach to privacy. Feedback from a reader using a particular screen reader or browser combination is especially useful, since it reflects real-world conditions our internal testing may not fully replicate.

10. Feedback and revisions

In the area of feedback and revisions, Caban aims to make its editorial pages usable by people with different abilities, devices, and browsing preferences. We use semantic headings, readable line lengths, visible focus states, descriptive link text, labels for fields, and alternative text for editorial images relevant to this part of the site. The site is reviewed as part of ordinary content maintenance, but accessibility in relation to feedback and revisions is a continuing practice rather than a claim of perfection.

Readers evaluating our approach to feedback and revisions can enlarge text, use keyboard navigation, reduce motion in their operating system, or use assistive technology. If this section of the site, covering feedback and revisions, creates a barrier, please tell us what page was involved and what would help. We will assess the report and record practical improvements without requesting unnecessary personal information.

A reader reporting a barrier is asked to describe the page address, the device and browser or assistive technology involved if known, and what outcome would have worked better, though none of this detail is required to submit a report. We aim to acknowledge an accessibility report within five business days and to provide an update on a practical fix within thirty days where the issue requires a template or design change rather than a simple content correction. Reports that reveal a pattern affecting multiple pages, such as an entire template missing a label, are prioritized above a single-page wording issue. This statement was reviewed 1 October 2026, with the most recent substantive update, adding the keyboard-navigation testing note, completed on 20 June 2026. We expect to continue reviewing this statement at least annually alongside the site's other policy pages.

Business registration

This accessibility statement is issued by PT Caban Media Nusantara, operating as Caban from Jalan Purnawarman No. 27, Bandung Wetan, Bandung, Jawa Barat 40115, Indonesia, registered under business number NIB 0311230091827 and tax identification number NPWP 02.481.736.4-428.000. Accessibility questions can be sent to [email protected] or by telephone at +62 811 7265 9304.