Reviewed 22 September 2026
Accessibility statement
Wridian wants its educational material to be usable by people with different devices, abilities, and reading preferences. We work toward clear structure, sufficient contrast, keyboard access, descriptive alternative text, and language that does not assume specialist knowledge. This statement describes our current approach and how to report a barrier.
1. Our commitment
We design pages with semantic headings, landmark regions, labels, visible focus, and responsive layouts. The site is tested at common desktop and mobile widths. Accessibility is an ongoing practice rather than a certification claim.
2. Text structure
Pages use one primary heading followed by meaningful section headings. Lists and tables are used for relationships that benefit from structure. Paragraphs are kept readable and links describe their destination.
3. Images
Informational images include descriptive alternative text. Decorative treatment is avoided when an image does not add meaning. Visitors can report an image whose alternative text is inaccurate, vague, or missing.
4. Keyboard use
Navigation, links, buttons, form fields, and cookie controls are designed to work with a keyboard. A visible focus state helps users understand their position. If a component traps focus or cannot be reached, please report its page and browser.
5. Contrast and typography
Wridian uses dark charcoal text on light backgrounds and light text on dark footer areas. Headings use a clear scale and body text uses generous line height. Browser zoom and text enlargement should remain usable on supported modern browsers.
6. Motion and interaction
The site uses limited interaction and does not rely on animation to convey essential information. Menu behavior is controlled by a simple button. Cookie controls require an explicit choice and do not auto-dismiss.
7. Forms
The contact form labels name, email, and message fields and identifies required input through browser validation. A successful submission message appears after the form is handled. No form asks for private keys, passwords, or recovery phrases.
8. Known limitations
Third-party linked pages may not meet the same standard. Some technical vocabulary may remain difficult even with plain-language framing. Embedded tools, when used, can change independently of Wridian.
9. Reporting a barrier
Contact the desk with the page URL, the task you attempted, your device or browser, and the barrier observed. Do not include sensitive personal information. We review reports during Seoul business hours and prioritize barriers that prevent reading or contacting the desk.
10. Response process
We acknowledge actionable reports where possible and assess whether the problem is content, markup, styling, or a third-party dependency. A correction may be made directly or documented as a known limitation. We retain accessibility correspondence for up to 24 months.
11. Contact
Write through contact.php or call +82 2-3486-7129. Postal correspondence may be sent to 15, Gangnam-daero 98-gil, Gangnam-gu, Seoul, 06231, Republic of Korea.
12. Review date
This statement was reviewed on 22 September 2026 and will be reviewed when the site navigation or publishing system materially changes.
Our current approach follows the principles commonly associated with WCAG 2.2, while this statement is not a formal conformance certification. Content is reviewed at a practical level for headings, labels, focus order, contrast, zoom, and alternative text. A page may still contain a barrier introduced by a browser update, a third-party link, or a newly published image, and reports help us locate those cases.
Visitors may request information in a different format or ask for a reasonable adjustment to a form or navigation path. Please identify the page address, the task that could not be completed, the device or assistive technology involved, and a preferred way to receive a response. Do not include health details or other sensitive information unless it is necessary to explain the barrier.
Accessibility reports are routed to the editorial and site-maintenance contacts. We aim to acknowledge a report within five business days, assess its priority within 10 business days, and provide an update within 30 days. Urgent access problems affecting a core contact route may be reviewed sooner when the relevant details are available.
Modern browsers provide zoom, text enlargement, reduced-motion preferences, captions, and other controls that may change the reading experience. Wridian does not treat those browser features as a substitute for accessible markup, and we test common combinations where practical. A third-party destination may have separate controls and should be contacted directly for its own accessibility issue.
This statement was reviewed on 22 September 2026. We record material improvements and recurring barriers so future reviews can address patterns rather than isolated pages. The next review may update examples, browser guidance, or contact instructions without changing the commitment to clear, keyboard-accessible educational content.
Our approach is informed by common accessibility practices, though this page is not a formal WCAG 2.2 conformance certification. Pages are tested at practical levels for headings, labels, focus order, color contrast, zoom behavior, and descriptive alternative text. A new image, browser update, or embedded resource may introduce a barrier, and reports help us identify and address those cases. We do not ask visitors to use a assistive technology in a particular way, but we test common combinations.
Visitors may request a page in a different format, ask for an adjustment to a form or path, or clarify an accessibility concern. Please identify the page URL, the task that could not be completed, the device or assistive technology involved, and a preferred way to be contacted. Do not include health details, recovery phrases, passwords, or other sensitive information unless it is necessary to explain the barrier.
Accessibility reports are reviewed by the editorial and site-maintenance contacts. We aim to acknowledge a report within five business days, assess its priority during the next 10 business days, and provide an update within 30 days. An urgent barrier affecting the main contact route or a critical accessibility control may be reviewed sooner if the necessary technical details are available.
Modern browsers offer zoom, text enlargement, reduced-motion preferences, captions, voice-control, and other features that may change the reading experience. Wridian does not treat those browser features as a substitute for accessible markup, and we test common viewport sizes and scaling levels. A linked third-party service may have its own controls and should be contacted directly if an accessibility issue occurs there.
This statement was reviewed on 22 September 2026. We maintain a record of resolved barriers and recurring topics so that future reviews can address patterns. The next review may update browser examples, guidance, or contact information without changing the commitment to clear, keyboard-navigable, and inclusive educational content.