Accessibility Statement
In Town Home Buyer is a small local home buying company. We want every homeowner who lands here to be able to read what we do, get their property details to us, and reach a person — regardless of how they use the web.
The standard we build to
We design and build this website to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. WCAG 2.2 includes everything in WCAG 2.1, so work done against the earlier version still holds. Where a Level AAA improvement is practical without harming clarity or performance, we take it.
What we do not claim. We do not describe this site as “ADA certified” or “100% compliant.” No such certification exists, and any site of a reasonable size will have issues at any given moment. What we can tell you is what we build to, what we know is imperfect, and how quickly we respond when someone tells us something is broken.
Assistive technology support
This website is built on custom, hand-written code rather than a page builder or template engine. That matters for accessibility: the underlying HTML is semantic by construction, so the structure a screen reader announces is the same structure a sighted visitor sees, rather than a layer of generic containers reverse-engineered into something announceable.
The site is built and maintained to work with:
- Screen readers — real headings, landmarks, lists, and form labels, so you can navigate by structure instead of reading top to bottom.
- Keyboard-only navigation — every control is reachable and operable by keyboard, with a focus indicator that stays visible and is never hidden behind the sticky header.
- Screen magnification and browser zoom — the layout reflows to a single column and remains usable at 320 pixels wide and at 200% zoom.
- Voice control — buttons and links are named with the words you can actually see on them, so speaking the visible label activates the control.
- Operating-system accessibility settings — reduced motion, increased text size, custom text spacing, and forced-colors / high-contrast modes are respected rather than overridden.
Manual testing with NVDA and VoiceOver is being arranged as part of an independent accessibility audit. Until that testing is complete, the work described above has been verified at the code level and by automated checks only — see Known limitations.
What we have done
- Built the site on semantic HTML — real headings, lists, landmarks, buttons, and links.
- Given every form field a visible label, not just placeholder text, plus autocomplete support so browsers and assistive tech can fill them in.
- Made every function reachable and operable by keyboard alone, with a focus indicator that stays visible.
- Added a “skip to main content” link on every page.
- Made photo upload optional and available through a standard file picker — dragging is never required.
- Written form errors as text that explains how to fix the problem, associated with the field it belongs to, and never signalled by colour alone.
- Checked text and interface contrast against the 4.5:1 and 3:1 thresholds.
- Made the layout work down to 320 pixels wide and at 200% browser zoom.
- Honoured the operating system’s “reduce motion” setting.
- Added a first-party display toolbar (text size, contrast, link highlighting, spacing, motion). This is a convenience on top of an accessible site — not an overlay standing in for one.
Known limitations and third-party components
Being straight with you about where we are weakest:
- Third-party integrations. Parts of this site rely on services supplied by outside vendors — specifically address autocomplete, analytics, and tag management. Their internal code is delivered by the vendor and is outside our direct programmatic control, so we cannot guarantee their accessibility the way we can for code we write ourselves. Where a vendor component could stand between you and something you need, we build an equivalent route that does not depend on it: property addresses can always be typed in manually, and the phone number and email below reach a person directly. If a third-party component blocks you, please tell us — we would rather replace a vendor than lose a visitor.
- Documents. We do not currently run a formal accessibility review process on PDFs and other documents. If any document we send you is not accessible to you, contact us and we will provide the same information in an alternative format — plain text, large print, or read to you over the phone.
- Manual testing is not yet complete. This site has been built and checked against accessibility standards at the code level, and we run automated checks as part of our development process. Independent manual testing with screen readers and keyboard-only navigation is being arranged and has not yet taken place. We would rather tell you that than imply a level of verification we have not reached.
- Ongoing content. New pages and landing pages are added regularly. A page published this week may not yet have had a full manual review.
How we keep this current
Accessibility is treated as a build requirement, not a one-off project. We run automated accessibility checks as part of our development process, before and after every change to a public page. We are currently arranging independent manual accessibility testing, and after that first audit we intend to move to a recurring review schedule.
Automated checks are a first pass only — they cannot detect most real barriers. The keyboard and screen-reader walkthroughs are what actually establish whether this site works, which is why we are not describing it as verified until those are done.
Tell us about a barrier
If any part of this site stopped you from doing something, we want to know. You do not need to know the technical term for it — “the form wouldn’t let me past the phone box” is a perfect report. We aim to respond within two business days.
We would genuinely welcome the chance to fix a problem quickly and directly, and we can usually do so faster than any other route. You are of course free to pursue any other remedy available to you at any time — contacting us is an invitation, not a requirement, and nothing on this page limits your rights.
We can also provide any information on this site in an alternative format — large print, plain text, or read to you over the phone. Just ask.
Reach a person directly
If the website is not working for you
You should never have to call us to do something another visitor can do online. If that happens, it is a bug on our side and we want to fix it. In the meantime, we will happily take your property details over the phone, by text, or by email and handle the rest ourselves — at (617) 295-7229.