Skip to main content

HyunTools
Accessibility statement
POLICY AND TRUST DOCUMENTS
Privacy policyTerms of serviceUsage policyCommunity guidelinesSecurity reportingAccessibilityCurrentTrust and transparencyOpen-source licensesApplicant privacy
Help Center
Contents
01Our accessibility commitment02Conformance target and current status03Accessibility measures in use04Display and motion preferences05Keyboard and assistive technology06Technologies and environments07Known accessibility limitations08Report an accessibility issue09How we review and improve10Ownership and change history
ACCESSIBILITY STATEMENT

Accessibility statement

A transparent overview of current accessibility support and known limitations so that more people can use HyunTools comfortably.

We publish both our checks and known limitations. We do not claim unverified full compliance and update this statement as issues are improved or discovered.

01

Our accessibility commitment

HyunTools treats accessibility as a baseline quality so that as many people as possible can use our online tools and services regardless of disability, device, or input method.

When we build a new feature or change an existing screen, we review the principles of perceivable, operable, understandable, and robust experiences together. We will continue to address accessibility barriers reported by users.

02

Conformance target and current status

Target
We use WCAG 2.2 Levels A and AA as development targets.
Current status
Partially conformant. Core navigation and general tools include an accessibility foundation, while some complex workspaces still have the known limitations described below.
Assessment method
Our current assessment is based on internal code review and keyboard and responsive-behavior checks during development. We have not received independent accessibility certification or a complete external conformance audit.
“Partially conformant” does not mean that every success criterion has been met. It describes our current state of publishing known limitations and improving them from real user feedback.
03

Accessibility measures in use

  • Use meaningful HTML for page titles, heading levels, primary regions, and navigation.
  • Give icon-only controls and inputs accessible names, and hide decorative icons from assistive technology.
  • Provide visible focus indicators on primary buttons, links, and inputs.
  • Communicate selected, expanded, and pressed states through text and ARIA attributes, and announce important results and errors as status messages.
  • Apply roles, labelled titles, Escape-to-close behavior, and focus return where practical to dialogs and complex menus.
  • Use icons, text, or shape in addition to color when communicating state.
  • Aim for responsive layouts and sufficiently large targets that adapt to different screen sizes.
04

Display and motion preferences

The following preferences can be saved in the current browser under Settings → Accessibility.

SettingBehavior
Reduce motionMinimizes transitions, repeating effects, and smooth scrolling.
High-contrast textMakes supporting copy and selected borders easier to distinguish.
Display themeLets you choose between the Midnight, Black, and Graphite dark themes.
Display densityLets you choose roomier or more compact card spacing.

Some screens also respect reduced-motion preferences set in the operating system or browser. Browser zoom and operating-system text or display scaling can be used alongside these settings.

05

Keyboard and assistive technology

  • Use Tab and Shift+Tab to move between links, buttons, and inputs.
  • Use Enter or Space to activate focused buttons and selection controls.
  • Supported dialogs and popovers can be closed with Escape.
  • Where visual reordering is needed, such as HyunFlow steps, up and down controls provide a non-drag alternative.
  • We provide input names, current states, and action results to screen readers as text where practical.

A shared skip-to-content link is available. We are continuing to improve internal skip links for repeated toolbars and work regions inside complex editors.

06

Technologies and environments

HyunTools accessibility depends on the following web technologies:

  • HTML and WAI-ARIA
  • CSS and responsive layouts
  • JavaScript and browser APIs
  • SVG and Canvas output in selected tools

We develop for current major desktop and mobile browsers, but behavior can vary by browser version and the combination of operating system and assistive technology. If JavaScript is blocked or the browser is outdated, menus, saving, and interactive tools may not work correctly.

07

Known accessibility limitations

FeatureKnown limitationCurrent alternative or plan
HyunDesign and avatar toolsElements and final appearance inside Canvas previews may not be described sufficiently to screen readers.Use the text inputs and numeric controls, then visually review the output. We plan to improve summaries of editable elements.
Dense workspacesHyunCode, HyunFlow, and some table or editing screens may require horizontal scrolling or extra navigation at large text sizes or high zoom.Use browser zoom and roomier display density. We continue to review reflow and zoom support.
Voice and translation featuresDictation, speech synthesis, and on-device language support vary by browser and operating system and may be unavailable in some environments.Direct text entry and copy remain available, and unsupported environments display a notice.
Public user contentHyunTools cannot guarantee in advance the accessibility of every phrase, link, or structure submitted to the anonymous forum.Problematic content can be reported and is reviewed under the community guidelines.
Complex workspace navigationSome editors may not offer enough internal skip links to bypass every repeated toolbar and work region.A global skip-to-content link is available, and we are reviewing additional internal landmarks and shortcuts for complex screens.
08

Report an accessibility issue

If you find a function that cannot be reached with a keyboard, difficult-to-read text, an incorrect screen-reader announcement, or overlapping content when zoomed, please tell us.

Use the issue report page or email hyuntools.owner@gmail.com. The following details help us investigate more quickly:

  1. The page address and feature name
  2. Your browser, operating system, and assistive technology
  3. The keyboard or interaction steps that led to the issue
  4. The actual result and the behavior you expected
  5. A screenshot with personal information removed, or the error text

Where possible, we will acknowledge receipt within seven days and share progress according to impact and implementation difficulty.

09

How we review and improve

  • Include keyboard focus, accessible names, and state communication in new shared UI.
  • Review desktop and mobile responsive behavior and primary keyboard flows when features change.
  • Assess accessibility reports separately from general visual defects when prioritizing work.
  • Require scoped manual and automated evaluation and a record of unresolved issues before claiming full conformance or certification.

This statement is based on self-assessment and is not a certificate from an accessibility specialist.

10

Ownership and change history

Accessibility owner
HyunTools accessibility and user experience
Email
hyuntools.owner@gmail.com
Effective date
August 7, 2026

We update this statement and its history when major accessibility features, assessment status, or known limitations change.

Change history

  • August 7, 2026: Initial accessibility statement
Document info
Effective
August 7, 2026
Version
1.0
Updated
August 7, 2026
Policy contact
hyuntools.owner@gmail.com
Reading progress0%
HyunTools · Independent service hub
PrivacyTermsUsage policyCommunitySecurityAccessibilityTransparencyOpen sourceApplicant privacyContact
hyuntools.com