Help using the site.
We build the guides and tools for keyboard use, readable text and clear focus on mobile and desktop. If something blocks your task, tell us the page and what went wrong.
Last substantive update: 8 September 2026 (Asia/Bangkok)
- Current standard
- Usable structure, controls, focus, contrast, motion and responsive layout
- Verification
- Representative automated and manual checks before release
- Need help?
- Contact us with the page and the task you could not complete.
Current implementation
Designed to be easier to use.
- Structure and landmarksSemantic headings, regions, labels and skip links support navigation without relying on visual position alone.
- Keyboard and focusInteractive controls are intended to remain reachable in a logical order with a visible focus indicator.
- Touch and control namesPrimary controls target a minimum 44-pixel touch area and expose an understandable accessible name.
- Contrast and meaningText and controls use high-contrast colours; colour alone should not carry required meaning or state.
- Motion preferencesNon-essential motion is reduced when the operating system requests reduced motion.
- Responsive resiliencePages are designed to avoid horizontal scrolling at common mobile widths and remain usable when text or viewport size changes.
Release verification
How we check accessibility.
Inspect structure
Check page titles, landmarks, heading order, control names and repeated navigation contracts.
Use the keyboard
Move through navigation, menus, disclosures, forms and tools while reviewing order, visibility and escape behavior.
Test responsive layouts
Review representative mobile and desktop widths for overflow, obscured content, target size and zoom resilience.
Review visual access
Inspect text and component contrast, non-colour state cues and dark-surface readability.
Respect preferences
Exercise reduced-motion behavior and ensure content does not depend on animation to become understandable.
Record limitations
Automated and representative checks support review; they do not prove that every device, assistive technology or barrier has been covered.
Reproducible feedback
Report the task that could not be completed.
If a page, control or document is difficult to use, the following context makes the barrier easier to reproduce and prioritise. Do not send sensitive personal documents or credentials.
- Exact URLShare the page address and, if possible, the heading, control or document where the problem occurs.
- EnvironmentInclude device, browser and any assistive technology or accessibility setting involved.
- Task and resultDescribe what you tried to do, what happened and what you expected to happen.
- Useful evidenceInclude a short screenshot or error message only when it does not expose private or sensitive information.
The publication uses this context to reproduce and prioritise issues. No WCAG conformance certification, response time or remediation outcome is claimed.
// REPORT · CORRECT · INSPECT
Keep the support route explicit.
Use current channels for an access barrier, the corrections process for factual content, and the research standard to understand how release evidence is handled.