Practical technology education. Senior-friendly AI. Scam defense. Measurable impact.

Accessibility

Accessibility Statement

This website is built for older adults. Accessibility is the product working, not a compliance exercise laid over the top of it. Last reviewed August 2026.

Our target

We aim to meet WCAG 2.2 Level AA. That is the target we design and test against, and we treat falling short of it as a defect rather than an acceptable trade-off.

What is in place

  • Full keyboard navigation — every control is a standard button, link or form field
  • Visible focus indicators that are never removed
  • A skip-to-content link as the first item you reach with the Tab key
  • 18px minimum body text, and no text below 16px
  • Text can be resized to 200% without losing content or function
  • Minimum 48×48px targets for buttons and navigation controls
  • Color contrast verified against WCAG 2.2 for every color pair in use
  • No meaning conveyed by color alone — links are underlined and states carry text
  • Menus open on click or Enter, never on hover alone, and close with Escape
  • Form errors announced in a live region, tied to their field, in plain language
  • Animation reduced or removed when your device requests reduced motion
  • No auto-rotating carousels and no time limits on reading anything

Known limitations

Stated plainly, because a statement that lists only strengths is not an accessibility statement.

  • Screen-reader testing with NVDA, JAWS, and VoiceOver has not yet been completed. Automated tools catch roughly a third of real accessibility problems, so this is a genuine gap rather than a formality.
  • Testing on real mobile devices with assistive technology enabled is still to be done.
  • Cross-browser verification so far covers Chromium only; Safari and Firefox passes are outstanding.
  • Site search is not built yet, which limits navigation options for people who prefer searching to browsing.

Tell us if something does not work

If any part of this website is difficult or impossible for you to use, we want to know. You do not need to know the technical term for the problem — describing what happened is enough.

Call (404) 492-6377 or email ChetOBeasley@BridgingTechnologiesATL.com. Tell us the page, what you were trying to do, and what happened instead.

If you need information from this site in another format, ask and we will find a way to get it to you.