Accessibility Statement
Gajema aims to make its editorial material usable across common browsers, keyboard controls, screen readers, and responsive devices. This statement was reviewed on 22 September 2026.
The site is designed around readable HTML, predictable navigation, resizable text, and content that remains useful when images or scripts are unavailable. We continue to review practical barriers rather than treating accessibility as a one-time project.
1. Our approach
We use semantic headings, descriptive links, visible focus, responsive layouts, and text alternatives for editorial photographs. We avoid relying on color alone to communicate meaning.
Headings are organized by topic, links describe their destination, and forms use clear labels. Content should remain understandable at increased zoom and on narrow screens. We aim to follow WCAG 2.2 AA practices where they fit the static publication.
2. Keyboard access
Navigation and forms are intended to work without a mouse. The mobile navigation has a visible control, and interactive controls use native buttons and links.
Focus should move in a logical reading order and remain visible against the page background. If a keyboard trap, inaccessible control, or unexpected focus change is found, please report the page and browser so we can reproduce it.
3. Images
Images include descriptive alternative text when they carry editorial meaning. Decorative treatment is kept secondary to the text and does not replace written context.
Alt text identifies the subject and relevant context without repeating nearby captions. Where an image is purely illustrative, the surrounding prose carries the primary meaning. Image descriptions may be refined as pages are reviewed.
4. Contrast
The palette uses dark charcoal text on light surfaces and light text on the dark footer. Links provide a teal contrast and additional underlining or context where useful.
Users may also use browser zoom, reader modes, high-contrast settings, or custom styles. A color change that does not affect the underlying text should not be the only method used to understand a category.
5. Documents
Gajema primarily publishes HTML pages so text can reflow. If a downloadable document is added, we will identify its format and make a reasonable accessible alternative available.
Download links should identify the file type and approximate size when relevant. A visitor who cannot use a document may request the same material in readable HTML or plain text.
6. Known limitations
Third-party pages linked from Gajema may not meet the same standard. Older browser features or user extensions may also alter presentation.
Some complex technical diagrams may require additional written explanation. We review these cases when reported and may add a caption, transcript, or text summary.
7. Feedback
Report a barrier with the page URL, device, browser, and a short description. Contact 24-1, Nonhyeon-ro 155-gil, Gangnam-gu, Seoul, 06041, Republic of Korea or +82-2-7105-8329.
Visitors may also use the contact page. Please avoid sending passwords, private keys, identity documents, or other confidential information in an accessibility report.
8. Response
We acknowledge accessibility reports where possible and normally review them within 30 days. Urgent barriers affecting essential contact access are prioritized.
Where a quick fix is not possible, we will describe a practical alternative when available. Review notes may be retained for up to 24 months to track recurring barriers.
9. Testing
Editorial staff review headings, focus order, responsive behavior, descriptive links, and image alternatives during page updates. This statement was reviewed on 22 September 2026; the previous review was 1 June 2026.
Reporting an access barrier
Accessibility support applies to the public editorial pages, navigation, forms, notices, and policy documents. Because browsers, assistive technologies, network settings, and device sizes vary, a page that works in one environment may still present a barrier in another. Reports help us identify the practical combination that needs review.
When reporting an issue, please include the page address, the task you were attempting, the type of barrier, and the browser or assistive technology involved if known. A short description is sufficient; please do not send medical information, passwords, identity documents, or other unrelated sensitive material. Screenshots may help when they do not expose personal information.
We aim to acknowledge an accessibility report within 7 business days, assess the issue within 15 business days, and provide a progress update or available workaround within 30 days. Some changes require testing across layouts or depend on an external hosting component. If an immediate fix is not possible, we will record the issue for a later review.
Visitors may request information in a more usable format where reasonably practicable. The request should identify the page and preferred format, such as plain text or a structured document. We will consider the request in light of the content, available resources, privacy requirements, and the need to preserve accurate editorial context.
Accessibility correspondence can be sent to 24-1, Nonhyeon-ro 155-gil, Gangnam-gu, Seoul, 06041, Republic of Korea, or +82-2-7105-8329. This statement was reviewed on 22 September 2026. Material changes to the accessibility approach will be dated so readers can distinguish a current commitment from an earlier review.