Accessibility

Accessibility Statement

Every father should be able to use this site, whatever device, ability, or connection he has.

Effective date: October 26, 2026

Last assessed: October 26, 2026

Our goal

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. These are the widely used international standards for making websites usable by people with disabilities. We have not had a formal audit, so we do not claim full conformance.

What we tested, and how

On October 26, 2026 we checked the site with automated test scripts in the Chromium browser, on a phone-sized screen (390 pixels wide) and a desktop screen (1280 pixels wide):

  • Automated checks: we ran axe-core against the WCAG 2.1 A and AA rules on the home page, the directory (with and without filters), the topics list and two topic pages, search, every state page, the guided finder, the Encouragement page and two of its articles, the Suggest a Resource page, the About page, the policy pages, and the "page not found" page. In the guided finder, we ran it at each step and on several results screens. It reported no violations. Automated tools catch only some problems, and some color-contrast results could not be decided automatically, so we can't promise there are no issues.
  • Zoom and reflow: we checked key pages (home, directory, a topic page, search results, the privacy policy, and some state pages), the Encouragement page and two articles, and the Suggest a Resource page at widths equal to 200% and 400% zoom on a desktop screen (640 and 320 pixels wide), plus the finder's results at 320 pixels. The content fit the screen with no sideways scrolling.
  • Without JavaScript: with JavaScript turned off, the menu links, the crisis links, and the full list of resources in the directory and on topic pages still show. The Encouragement page, the two articles we checked, and the Suggest a Resource page still show in full. The directory filters, site search, and guided finder need JavaScript. Without it they are hidden, and the search and finder pages say so and point you to other ways to find help.
  • Keyboard: using the Tab key, we moved through the skip link, the crisis links, the main menu, and the directory filters. Each one received a visible focus outline, in a logical order. The mobile menu opens with Enter and closes with Escape. Clearing the directory filters moves focus back to the keyword box. In the guided finder, pressing Next moves focus to the new step's heading, and the next Tab reaches that step's question.
  • Reduced motion: we ran the guided finder checks with the "reduce motion" setting turned on.

Built-in features

  • A "Skip to main content" link is first on every page.
  • Pages use headings, landmarks (header, navigation, main content, footer), and labeled form fields.
  • The number of matching resources is announced to screen readers when you change a directory filter or get results in the guided finder.
  • If your device is set to reduce motion, we turn off animations.
  • No cookies, pop-ups, or autoplaying media.

Known limitations

  • We have not tested with screen readers such as NVDA, JAWS, VoiceOver, or TalkBack, or in browsers other than Chromium. We have not had testing done by people who use assistive technology. We'd welcome that help.
  • The site is only in English for now.
  • Resources we link to are on other websites, which we don't control and which may not be fully accessible.
  • The Suggest a Resource form is a Google Form hosted on Google's website, so its accessibility is largely outside our control. You can email suggestions instead.

Feedback

If something on D.I.K. is hard to use, please tell us, and we'll fix it or get you the information another way. Email [email protected] and, if you can, include the page address and what went wrong. We aim to reply within 5 business days.