SafeFamily: Accessibility and Inclusion Analysis

SafeFamily DNS filtering aims to protect children from harmful online content. This document analyses barriers that may prevent certain families from accessing or effectively using

Download (4.9 KB)

SafeFamily: Accessibility and Inclusion Analysis

Overview

SafeFamily DNS filtering aims to protect children from harmful online content. This document analyses barriers that may prevent certain families from accessing or effectively using the service, and proposes mitigations.


Identified Barriers

Families Without Smartphones

Parents who lack smartphones cannot use mobile apps to manage SafeFamily settings. They may rely on shared devices, pay-as-you-go phones, or no phone at all. Without a management interface, they cannot configure categories, view reports, or respond to alerts.

Families Where English Is Not the First Language

Documentation, category labels, setup wizards, and support materials may be inaccessible to non-English speakers. Technical terms like "DNS," "filtering," and "categories" may not translate well or may be confusing in translation.

Parents With Disabilities

  • Visual impairments: Screen readers must work with all interfaces; colour contrast and font sizing matter.
  • Motor impairments: Touch targets, keyboard navigation, and voice control must be considered.
  • Cognitive impairments: Complex flows, jargon, and multi-step setup can exclude parents who need simpler, step-by-step guidance.

Children With Special Educational Needs

Some children require different category rules-for example, stricter limits on certain content, or exemptions for educational resources. One-size-fits-all defaults may not suit children with autism, ADHD, or learning differences.

Digital Literacy Gaps

Parents who do not understand DNS, routers, or technology may struggle to set up SafeFamily. They may not know what "blocking" means in practice or how to interpret category reports.

Households Without Broadband (Mobile-Only)

Mobile-only households use cellular data, tethering, and mixed-network access. Home-network DNS alone is insufficient for these families, so SafeFamily must support mobile operator filtering and on-device managed DNS to provide meaningful protection off home Wi-Fi.

Multigenerational Households

Grandparents acting as caregivers may have different technical skills and expectations. They may need simpler interfaces and more human support.

Traveller and Roma Communities

These communities may face mobility, connectivity, and trust barriers. Services that assume fixed addresses or mainstream tech adoption may not reach them.

Low-Income Families

Cost of devices, data, or premium support may exclude low-income families. Free or subsidised access must be clearly communicated.


Proposed Mitigations

BarrierMitigation
No smartphonePhone helpline for setup and changes; web-based management accessible from libraries or shared devices
Non-English speakersMulti-language support for UI, docs, and helpline; plain-language translations of category names
DisabilitiesSimplified interfaces, WCAG 2.1 AA compliance, keyboard/voice support, high-contrast mode
Special educational needsPer-child profiles with customisable category rules; guidance for parents of children with SEN
Digital literacy gapsCommunity workshops, video tutorials, ISP-assisted setup, "SafeFamily in 5 minutes" guides
Mobile-onlyMobile-first inclusion path: operator per-SIM filtering (MNO/MVNO), on-device managed DNS setup (iOS/Android), and clear full/partial/off coverage status in parent app
MultigenerationalGrandparent-friendly guides; helpline staff trained for older users
Traveller/RomaOutreach via trusted community organisations; flexible setup options
Low-incomeFree tier; clear signposting of subsidies; no premium paywall for core safety features


Irish Language (Gaeilge) Provision

As an initiative intended for national adoption, SafeFamily should offer:

  • Irish-language option in the parent app and web dashboard (toggle between English and Irish)
  • Block page displayed in both languages, or matching the device's language preference
  • Public communications and materials available in Irish (consistent with the Official Languages Act 2003 and the Official Languages (Amendment) Act 2021, which strengthens Irish language obligations for public bodies)
  • If SafeFamily is operated as a public service or state-funded initiative, Irish-language compliance is likely a legal requirement, not optional

Implementation note: Irish-language interface localisation is a relatively low-cost addition (~€5-10k for translation and UI work) and should be budgeted in Phase 2.


Summary

SafeFamily must be usable by families regardless of language, ability, income, or technical skill. A combination of phone helpline, multi-language support (including Irish), simplified interfaces, community workshops, ISP-assisted setup, and mobile-first protections for SIM-based households can reduce exclusion and ensure the service serves all families who need it.