Accessibility.

Conformance target

We aim to meet WCAG 2.2 Level AA across the guide. We have not completed an assistive-technology review of every page, so this is not a claim of full conformance.

How the guide is designed

• Keyboard navigation. Navigation, school links, filters and controls on the previously saved page are built to work from the keyboard. A skip link precedes the masthead.
• Visible focus indicators. Interactive elements use :focus-visible styling to make keyboard focus easier to find.
• Landmark regions. The page templates use semantic header, nav, main and footer regions, with labels where needed.
• Heading hierarchy. Pages are organised around a main heading and descriptive section headings.
• Colour contrast. We target WCAG 2.2 AA contrast: 4.5:1 for normal text and 3:1 for large text and relevant controls. An audit on 19 May 2026 found contrast problems in the former design; changes on 23 May 2026 addressed that version. Those dates are not a fresh assessment of the current design.
• Reading surface. Pages use dark text on a light background, with a dark masthead.
• Reduced motion. Non-essential motion is limited, and the interface includes prefers-reduced-motion rules.
• Forms and images. Search and filter controls have labels; meaningful images have alternative text. If you encounter an unclear control or image description, please tell us.
• Readable documents. Profiles and guides use headings, paragraphs, lists and tables to keep the information available without relying on a visual layout alone.

Known limits

These parts of the experience need particular care:

• Interactive homepage filtering requires JavaScript. Without it, the school links remain available in their default order.
• Long fee and comparison tables may require horizontal scrolling on a narrow screen. Their information remains in the page.
• The current redesign has not yet had a complete assistive-technology review across every route.

How we test

We review representative pages at desktop and mobile sizes and try key journeys with a keyboard. Automated checks can find some markup and contrast problems, but cannot tell us whether a page is comfortable to use. Feedback from people using assistive technology helps us find barriers those checks miss.

Reporting an accessibility barrier

If a page does not work with your assistive technology, email info@pattaya-school-guide.com with the affected URL, the device or software you used, and what happened. We will review the barrier and reply with the next practical step.

Standards we benchmark against

Our design reference is WCAG 2.2 Level AA, with the ARIA Authoring Practices Guide for interactive controls. These references guide our work; they do not by themselves establish conformance.