Built to be read by everyone.

What works today.

• Touch targets. Every interactive element on every page is at least 44 by 44 pixels, per WCAG 2.5.5 and Apple HIG.
• Keyboard support. Every interactive element can be reached and used with the keyboard. Focus rings are always visible. The mobile drawer has full focus trap, ESC closes, outside-click closes.
• Skip links. Every page has a Skip to content link that lands at #main.
• Semantic HTML. We use <main>, <article>, <section>, <nav>, <aside>, <header>, <footer> appropriately. Headings are hierarchical: h1 once per page, then h2/h3.
• ARIA. Sticky drawer has aria-hidden, aria-expanded on the toggle. Skip link, search-action buttons, navigation, dialogs, and the reading-progress bar all have appropriate ARIA roles.
• Colour contrast. Body text on background is 11 : 1. Primary link blue on cream is 5.8 : 1. We exceed WCAG AA for normal text everywhere.
• Reduced motion. prefers-reduced-motion: reduce disables hero entrance animation, reveal-on-scroll, count-up, pulse on the emergency block, and view transitions.
• Reduced contrast preferences. prefers-contrast: more bumps our hairlines and link decorations to high-contrast values.
• Forced colours. Windows High Contrast Mode is supported via forced-colors: active: borders revert to CanvasText, key elements remain legible.
• Self-hosted fonts. Inter and Fraunces are served from our own domain so they load without third-party tracking. font-display: optional means text appears immediately in fallback fonts during font load.
• No flashing content. No animation pulses faster than 3 Hz, per WCAG 2.3.1. The emergency block's pulsing dot is at 0.5 Hz and respects reduced-motion.
• Alt text. All meaningful images carry alt text. Decorative SVG (icons) carry aria-hidden="true". The facility map has a long alt that describes the geography for screen readers.
• Print stylesheet. Pages are usable in print: chrome stripped, links annotated with their URLs, QR code top-right linking back to the live version.
• Keyboard shortcuts. Press ? (or the Shortcuts button in the footer) for the full list. Press / to focus directory search where available; press . to scroll to the top. Leader-key navigation: g then a letter (h home, o compare, e emergency, u healthcare guide, w/d/l category hubs with search focused, v map with search focused, c corrections desk, t submit desks, s standards, a about, 1/2/3 compare sections, 4/5/6 healthcare guide sections, 7/8 emergency page sections). On any page with sticky section jump nav, press j then 1–9 to jump to that section in order.

What is still imperfect.

• Facility profile navigation. Sticky horizontal section jump nav on every profile, plus a collapsible section list on viewports under 1100px. Desktop users also get the fixed floating section table of contents. Quick facts remain in a pinned details card on small screens.
• Long editorial and directory pages. The same collapsible section list appears below sticky jump nav on standards, privacy, about, masthead, compare, hub pages, the healthcare guide, and the homepage directory. Hash #directory-search on the homepage, #hub-search on hub pages, and #map-browse on the map focus the directory search field. On mobile, a floating Search list chip returns you to the toolbar when you have scrolled past it.
• View Transitions require Chromium-based browsers. Firefox and Safari users get standard page reloads, which work fine but are not as smooth.
• Speculation Rules (prefetch on hover) are Chromium-only. Other browsers see standard navigation.
• The reading-progress bar is not announced to screen readers as a live region. It is positioned out of the document flow and has role="progressbar" with aria-valuenow, but most screen readers do not poll it. Improvement scheduled.
• Thai-language support is not yet shipped. Content is English only; we will add hreflang alternates when Thai pages exist.

When we have failed you.

If any page is unusable for you for any accessibility reason — you cannot reach an interactive element, the contrast is too low for you to read, your screen reader chokes on something, the keyboard trap misbehaves, anything — please tell us. Email [email protected] with "Accessibility:" as the subject prefix. We aim to acknowledge within seven calendar days and to fix substantive issues within thirty.