Accessibility statement

Our goal

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2, level AA on every page, in every language edition.

What we have done

• Readable text: body text is 18px or larger on desktop, with generous line spacing and line lengths kept short. Body text meets at least 4.5:1 contrast, and most pairs meet the stronger 7:1 level, in both light and dark themes.
• Plain language: answers are written at about an eighth-grade reading level, with terms defined the first time they appear.
• Keyboard access: every menu, search panel, accordion and form works with a keyboard. A “Skip to content” link appears first on every page, and focus is always visible.
• Screen readers: pages use proper headings, landmarks and labels. Menus and dialogs announce their state, and every overlay has a visible close button.
• Touch: buttons and links are at least 44 by 44 pixels.
• Motion: the site has almost no animation. Short transitions turn off when your device asks for reduced motion.
• Zoom and reflow: pages work at 200% zoom and on screens as narrow as 320 pixels without sideways scrolling. Wide tables scroll inside their own box.
• Themes: light, dark and system themes, chosen by you and remembered.
• Languages: each page declares its language so screen readers use the right voice.

Known limitations

• Some official sources we link to (government PDFs in particular) may not be fully accessible. We link to the HTML version when one exists.
• Article images are illustrations; we describe them in alt text, but they carry no information that is not also in the text.

Report a problem

If something is hard to use, tell us at Please use the contact form. or through the contact form. Please include the page address and what happened. We aim to reply within 2 business days and to fix confirmed problems within 10 business days, or tell you when we will.

How we test

We check pages with automated tools, keyboard-only use, screen readers, 200% zoom and phone, tablet and desktop screen sizes, in both themes, before publishing changes to templates.