Expand Digital Apps

An honest statement

Accessibility.

Expand Digital Apps aims to make its website and tools usable with a keyboard, screen reader, zoom, large text, dark mode and reduced motion. This is a practical commitment, not a claim of formal certification.

Last reviewed: 13 July 2026

Status The portfolio has not had a complete independent accessibility audit and no WCAG conformance certificate is claimed. Automated and manual checks help, but they do not prove that every user journey is barrier-free.

What this statement covers

This statement covers the static app pages at apps.expand.digital, the four Flutter web calculators, the combined UK Money Toolkit and the Ping Thing Android app. Because these surfaces use different rendering technologies, accessibility behaviour can vary between browsers, operating systems and assistive technologies.

Measures built into the portfolio site

  • Semantic headings, landmarks, lists, tables and link text.
  • A skip link to bypass repeated navigation.
  • Visible keyboard focus with a high-contrast focus indicator.
  • Responsive layouts that reflow from two columns to one without requiring horizontal scrolling for ordinary content.
  • System light or dark preference by default, with a labelled theme control that updates its accessible name.
  • System font stacks, no external font dependency and text that can be resized by the browser.
  • Reduced or removed movement when the operating system requests reduced motion.
  • Decorative images and icons hidden from assistive technology so they do not repeat nearby headings.
  • Colour is supported by text, labels or shapes rather than being the only signal.
  • Page content remains available if JavaScript is disabled; only the manual theme control and automatic copyright year depend on it.

Accessibility in the tools

The finance tools and Ping Thing use labelled controls, Material semantics, touch-friendly targets and layouts intended to adapt to narrow screens and larger text. Calculation logic is kept separate from presentation and has automated tests. Some tools also provide text or table equivalents for visual information, such as the mortgage balance chart's year-by-year schedule.

Those design choices reduce barriers, but Flutter web and native Android accessibility depend partly on the Flutter engine, browser or Android accessibility services. Behaviour should be checked with the specific assistive technology you use.

Known limitations and risks

  • No comprehensive assistive-technology matrix: the portfolio has not been exhaustively tested across all combinations of VoiceOver, TalkBack, NVDA, JAWS, browsers and devices.
  • Flutter web semantics: some browser and screen-reader combinations may announce custom Flutter controls less predictably than equivalent native HTML controls.
  • Dense financial results: calculation breakdowns and amortisation schedules contain many numbers and can require substantial navigation at high zoom or with a screen reader.
  • Charts: visual charts may be difficult to interpret with colour or low vision. Textual values or tables are supplied where implemented, but they may not provide the same overview.
  • Third-party destinations: GitHub, Buy Me a Coffee and linked government or provider sites are outside Expand Digital's control.
  • Very small screens and extreme text sizes: the layouts are designed to reflow, but unusual device widths or very large custom text settings may expose issues not yet found.

Using the site

  • Use your browser's zoom controls to enlarge text and content.
  • Use the theme button in the header to switch between light and dark themes. Without JavaScript, the site follows the system preference.
  • Keyboard users can press Tab from the top of a page to reveal the skip link.
  • Tables on narrow screens can be scrolled horizontally without forcing the whole page to scroll.
  • For calculator results, browser selection and copy features can help move values into a preferred reading or magnification tool.

Reporting a problem

If something prevents you from using a tool, please report the page or app, device and browser, what you were trying to do, and the assistive technology involved. Use the contact page or the owner's public GitHub profile. Contributors who already have repository access can create an issue there. Do not include private financial information, passwords, tokens or sensitive network details.

There is no published service-level target for responses or fixes, but maintainers can track reproducible accessibility defects in the source repository.

Standards approach

WCAG 2.2 Level AA is used as a reference point when designing and reviewing the portfolio. That sentence describes an aim and review framework only. It does not assert full conformance, legal certification or third-party accreditation.