Policies

Accessibility Statement

What we have built in, what we know is not finished, and how to tell us when this site gets in your way.

Last reviewed: Pending pre-launch audit

Our commitment

Families who need our programs are not a narrow group, and neither are the people who support us. A website that works only for someone with perfect vision, a mouse and a fast connection is not doing its job.

We build toward WCAG 2.2 Level AA and treat accessibility as part of the build rather than a pass at the end. Where we fall short, we would rather know and fix it than claim conformance we have not verified.

Conformance status

Partially conformant, formal audit pending

This site was built to WCAG 2.2 AA and the measures below are implemented and in place. A full audit — automated testing plus manual keyboard and screen-reader review — is scheduled before launch, and the result will be published here, including anything that fails.

What is built in

Structure and navigation

  • A "skip to content" link is the first thing on every page
  • Proper landmarks — header, main, footer and labelled navigation regions
  • One h1 per page and a logical heading order beneath it, with no levels skipped for visual effect
  • The current page is marked with aria-current, not colour alone
  • Breadcrumbs on every interior page
  • Link text that makes sense out of context — no bare "click here"

Keyboard

  • Everything is reachable and operable with a keyboard alone, including the menus and all forms
  • A clearly visible focus outline on every interactive element, which we never remove without replacing
  • Dropdown menus open with Enter or Space, move into with Down-arrow, and close with Escape
  • The mobile menu closes with Escape and returns focus to the button that opened it
  • No keyboard traps anywhere on the site

Forms

  • Every field has a real <label> programmatically associated with it — never a placeholder standing in for a label
  • Required fields are marked in the label, not only with colour
  • Native browser validation messages, so they appear in your own language and with your own assistive technology
  • Submission results are announced through a live region, so a screen-reader user hears success or failure
  • Helper text sits next to the field it applies to
  • Correct autocomplete attributes, so stored details fill in

Visual design

  • Body and heading text meets or exceeds the 4.5:1 contrast minimum against its background
  • Our gold brand colour is deliberately never used for text on a light background or for a meaningful boundary, because it does not meet the contrast minimum there. It appears only as a solid fill behind dark text, as large display type, or as decoration
  • Selected states carry a shape or fill change as well as a colour change
  • Status is never communicated by colour alone — text always says the same thing
  • Text reflows without horizontal scrolling down to 320px wide, and the layout holds when text is enlarged to 200%
  • Tables scroll inside their own container, so the page itself never scrolls sideways

Images and motion

  • Meaningful images carry descriptive alternative text; decorative graphics are hidden from assistive technology
  • All icons are decorative and marked aria-hidden, with the meaning carried in adjacent text
  • prefers-reduced-motion is respected — all animation and transition is disabled, and content that animates in is simply shown
  • Nothing flashes, auto-plays or moves without the user starting it
  • A print stylesheet produces a readable black-on-white document

Technical

  • Plain semantic HTML; the site is fully readable and navigable with JavaScript disabled
  • A declared page language, so screen readers use the right pronunciation
  • Native <details> elements for expandable sections, which inherit correct behaviour
  • Support for Windows high-contrast and forced-colours modes

Known limitations

We would rather list these than let you discover them:

  • Formal audit not yet complete. The measures above are implemented but not independently verified. Scheduled before launch.
  • Photographs are placeholders. Image areas currently show a labelled placeholder describing the photograph needed. Alternative text will be written for each real image as it is added, not generated afterwards in bulk.
  • Documents. No documents are published yet. When they are, PDFs will be checked for tagging, reading order and text layer, and we will provide an accessible alternative on request for anything that falls short.
  • Google Fonts. Two typefaces load from Google. If that request fails, pages fall back to system fonts and remain fully readable, with slightly different proportions.
  • Payment pages. Giving is completed on our payment processor's own pages, whose accessibility we do not control. We will take this into account when selecting a processor, and if you have difficulty giving online we will take your gift another way — just contact us.
  • Third-party content. Any embedded map or video added in future will be assessed before it goes live.

Tell us when something does not work

We want these reports

An accessibility problem on this site is a bug, and we treat it like one. You do not need to know the technical term for what went wrong — "I cannot get the menu to open with my keyboard" is a perfect report.

Use our contact form and choose "website or accessibility problem". If the form itself is the barrier, write to us at Address pending or ask someone to contact us on your behalf.

Please tell us the page, what you were trying to do, what happened, and the device, browser or assistive technology you were using, if you know. Any of those details helps; none of them is required.

What we will do

  • Acknowledge within two business days.
  • Give you a plain answer about whether we can fix it and roughly when.
  • Provide the information another way in the meantime — by phone, email or post — so the barrier does not stop you doing what you came to do.
  • Fix it and tell you when the fix is live.

Reaching us another way

Anything on this website can be done without the website. If a form is not usable for you, contact us however works and a staff member will complete it with you — enrollment enquiries, volunteer applications, event registration and giving included. You will not be asked to use the site.

Ongoing review

We review accessibility quarterly alongside broken links and public documents, and we re-check after any significant change to the site. Accessibility basics and alt-text writing are part of the training for everyone who edits this website.