Accessibility Statement

Updated 22 September 2026. Tymbra aims to make its editorial archive usable across devices, browsers, and assistive technologies.

This statement covers the public website, navigation, articles, images, forms, and policy pages. Accessibility can vary with browser settings, assistive technology, connection quality, and third-party destinations. We use ongoing review rather than treating accessibility as a one-time release task. Feedback helps us identify barriers that automated checks may not show.

1. Our approach

We use semantic headings, labelled controls, readable contrast, keyboard-friendly links, and descriptive alternatives for editorial images.

Heading order is intended to support scanning and screen-reader navigation. Controls should have visible names and meaningful focus states. Text remains selectable and is not presented only as an image. We aim to align practical work with WCAG 2.2 principles, while recognising that a small publication may still contain occasional defects.

2. Navigation

Pages share a consistent header and footer. Content is organised with headings so readers can scan or navigate by structure.

Navigation links describe their destination rather than relying only on visual position. The footer provides access to policy, contact, and editorial information. On narrow screens, the navigation may collapse into a menu control that can be operated with a keyboard. A reader can report a link that is confusing, repeated unexpectedly, or difficult to reach.

3. Images

Informational images include specific alternative text. Decorative choices are kept limited so they do not compete with the reading experience.

Alternative text describes the relevant subject, setting, and relationship to the surrounding content. It does not attempt to reproduce every visual detail when the image is supplementary. If an image carries information not available in nearby text, contact us so an equivalent explanation can be considered. Decorative visuals may use a non-announcing treatment where appropriate.

4. Forms

The contact form uses labels, required states, and a visible success message after a valid submission.

Labels are intended to remain associated with their controls when a screen reader or keyboard is used. Validation should identify the affected field and explain what needs attention in plain language. The success message should confirm receipt without exposing submitted content. If the form is unavailable, a reader may contact Tymbra by phone or address.

5. Contrast

Text and controls are designed against white, pale grey, violet-blue, and charcoal surfaces with clear contrast.

Contrast is checked for ordinary text, headings, links, buttons, and focus indicators. Color is not intended to be the sole way to communicate a state or category. Display settings, zoom, and operating-system contrast modes can affect perception. Please report a passage that becomes difficult to read under a particular setting.

6. Keyboard use

Interactive links, buttons, details elements, and form controls can be reached with a keyboard. Focus behavior may vary by browser.

Expected keyboard order follows the visual reading order. Focus should remain visible and should not be trapped inside a component during ordinary browsing. Native controls are preferred because they provide familiar interaction patterns. A report should identify the key sequence and the control that could not be reached.

7. Motion

The site uses minimal motion and does not depend on animation to communicate information.

Transitions are intended to remain brief and secondary to the content. Readers can use browser or operating-system preferences that reduce motion where supported. No essential article meaning should disappear when motion is disabled. If a movement causes discomfort or prevents access, include the page and device in a report.

8. Known limits

Third-party pages linked from Tymbra may not share these practices. Some older documents may require additional review.

Older content can contain inconsistent headings, link wording, or image descriptions even when the surrounding template has been improved. External documents, embedded tools, and downloadable files may follow separate accessibility standards. We prioritise barriers that prevent reading, navigation, form completion, or access to policy information. A reported limitation is recorded for review rather than dismissed because it occurs in older material.

9. Feedback

Tell us the page, device, browser, assistive technology, and barrier you encountered so the desk can investigate.

Useful reports include the exact heading or control, the steps that led to the problem, and an accessible way to reply. Personal data is not required to report a barrier. We aim to acknowledge accessibility correspondence within seven calendar days and provide a status update within 30 days where investigation takes longer. Do not send passwords, recovery phrases, or confidential documents.

10. Contact and review

45 Seolleung-ro, Gangnam-gu, Seoul 06149, Republic of Korea · +82 2-3486-7153. Next scheduled review: 2026.

The 2026 review considers keyboard navigation, heading structure, image alternatives, form feedback, contrast, zoom, and reduced-motion behavior. A future review date will be posted when this statement is updated. Material changes will be described in the page’s revision note. Readers may request the statement in an alternative accessible format through the same contact details.

Feedback and ongoing review

Accessibility feedback is treated as a practical service request rather than as a complaint about the person reporting it. A useful report can include the page address, the task being attempted, the browser or assistive technology involved, and the point at which access became difficult.

We aim to acknowledge feedback within 7 business days and review a reproducible issue within 30 days. A correction may involve a heading, label, alternative description, focus order, contrast choice, or a clearer text equivalent. Third-party pages reached through links may not be under Tymbra’s control, but we can identify the destination and explain the boundary. No personal information beyond what is needed to investigate the report should be included.

Requests may be sent through the contact page or to 45 Seolleung-ro, Gangnam-gu, Seoul 06149, Republic of Korea. If a requested format is not immediately available, we will discuss a reasonable alternative, such as plain text or a direct explanation. We retain accessibility correspondence for up to 24 months after closure so recurring barriers can be tracked, then delete or anonymise it unless a longer period is required for a documented dispute.

Revision record

This statement was updated on 22 September 2026. Future changes will be dated so readers can follow improvements to the site’s accessibility practice.