Accessibility Statement

Most people who read this site are either older adults or the family members helping them. A fair number arrive with a screen reader, magnified text, or a keyboard instead of a mouse. Building for that is the whole point of the site, so we treat accessibility as part of the work rather than a page we published once.

What we aim for

We build against the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. That is our internal target. We have not been audited by an outside firm and we do not hold any accessibility certification, so we are not going to claim conformance we have not had checked. What we can tell you is what we do and what we know is imperfect.

What we do

• Every page can be reached and used with a keyboard alone, and the focus outline stays visible as you move.
• A "skip to content" link is the first thing a keyboard or screen reader lands on, so you can jump past the navigation.
• Headings run in order, so a screen reader can be used to move through a page by structure instead of reading all of it.
• Body text meets at least a 4.5 to 1 contrast ratio against its background, and larger text meets 3 to 1.
• Buttons and links that matter are at least 48 pixels tall, which is comfortably above the 24 pixel minimum and easier for unsteady hands.
• Text reflows without a horizontal scrollbar when the page is zoomed to 200 percent.
• Images that carry meaning have alt text. Images that are decoration are hidden from screen readers rather than described.
• Comparison tables use real table markup with proper headers, so a screen reader can say which column a figure belongs to.
• Animation is kept minimal and respects the reduced motion setting in your operating system.

What we do not do

We do not use an accessibility overlay or a widget that claims to fix a site automatically. They tend to interfere with the screen reader or magnifier you have already set up, and they do not fix the underlying markup. If something here does not work with your own tools, that is a problem with our code and we would rather fix the code.

Known gaps

We are working through the site page by page. Older articles can still carry a heading that skips a level or a link whose text does not make sense read on its own. If you hit one, telling us is genuinely useful, because it is faster than us finding it.

Tell us about a problem

Email hello@ageinplaceguide.com and say what page you were on and what happened. If you can tell us what you were using, such as VoiceOver on an iPhone or NVDA on Windows, that helps us reproduce it. We aim to reply within five working days.

If you need something on this site read to you or explained over email, ask. We would rather answer the question directly than leave you stuck on a page.

See also our Privacy Policy, Terms of Use, and how we review products.