Market explanation should be available to more readers.

We aim to meet the practical intent of WCAG 2.1 Level AA for the public pages of hkjournal.online. Accessibility is considered in structure, writing, visual design and interaction rather than treated as a final overlay.

This statement describes the current static website. We review the experience when content or templates change and welcome specific reports that help us find barriers we missed.

Pages use semantic landmarks, a logical heading hierarchy, a skip link, visible keyboard focus, descriptive links and text alternatives for meaningful images. Content is presented in a mobile-first layout with constrained reading widths.

Colour choices target sufficient contrast, information is not conveyed by colour alone and controls have practical touch areas. Motion and smooth scrolling are suppressed when a visitor requests reduced motion.

The main navigation uses native links and a details element on narrow screens, so essential content remains available without JavaScript. The site is intended to work with current browsers, keyboard navigation and commonly used screen readers.

Text can be enlarged using browser controls and the layout reflows into a single column on narrow screens. No account, timed process, drag gesture or pointer-only interaction is required.

Generated editorial photographs can communicate context that an alt description cannot fully reproduce. We provide concise descriptions and keep the written argument independent of the photograph.

Third-party email and telephone software opened from our contact links is outside our control. If either route is inaccessible, use the alternative channel or request another reasonable format.

If you need an article, guide or contact detail in a different reasonable format, email contact@hkjournal.online or telephone +852 2311 8668 during office hours.

Please identify the page, the information you need and the format or assistive technology involved. Do not include sensitive financial or identity information in an accessibility request.

When reporting a barrier, tell us what you were trying to do, the page address and what happened. Details about browser, device or assistive technology are helpful but not mandatory.

We record actionable feedback, assess its effect and review this statement when material changes are made. This version was last reviewed on 2 September 2026.