Multifamily Top Security is committed to providing a website that is accessible to the widest possible audience, regardless of ability or technology. We treat accessibility as part of normal engineering — not an afterthought — and we test, fix, and iterate continuously.
Our Conformance Target: WCAG 2.2 Level AA
This website is designed and developed to conform with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, published by the World Wide Web Consortium (W3C). WCAG 2.2 AA is the same target used by U.S. federal government websites under Section 508 (revised) and is widely adopted under the Americans with Disabilities Act (ADA).
We test against the four WCAG principles: Perceivable, Operable, Understandable, and Robust.
What We Do
Perceivable
- Text alternatives on all meaningful images. Decorative images use empty alt attributes so screen readers skip them.
- Color contrast meeting at least 4.5:1 for body text and 3:1 for large text and UI components (verified with axe-core and manual checks).
- Information not conveyed by color alone — error states use icons and text, not just red.
- Resizable text up to 200% without loss of content or function.
- No auto-playing audio or video with sound.
Operable
- Full keyboard navigation — every interactive element (links, buttons, form fields, menus) is reachable and operable via Tab, Shift+Tab, Enter, Space, and arrow keys where appropriate.
- Visible focus indicators on all focusable elements with a minimum 3:1 contrast against the background.
- Skip-to-content link as the first focusable element on each page.
- Sufficient time — no automatic timeouts on forms.
- Reduced motion — we honor the
prefers-reduced-motionsystem setting and disable shimmer, parallax, and animated background effects accordingly. - Touch targets at least 44×44 CSS pixels on interactive controls.
Understandable
- Language declared on every page (
<html lang="en">). - Predictable navigation — consistent header, footer, and breadcrumbs across the site.
- Form labels associated with every input. Required fields are marked. Errors are described in text and announced to screen readers.
- Plain English — we avoid jargon outside of legal pages.
Robust
- Semantic HTML — we use
<header>,<nav>,<main>,<article>,<section>,<footer>,<button>, and headings (h1–h6) for their proper purpose, not as decorative wrappers. - ARIA used sparingly — we prefer native HTML semantics and add ARIA only where needed (e.g.,
aria-labelon icon-only links,aria-liveon form status messages). - Modern, valid markup tested against the W3C HTML validator.
How We Test
We combine automated and human testing:
- Automated: axe DevTools and Lighthouse accessibility audits run during development and before each deploy.
- Keyboard-only walkthroughs of every new page before publish.
- Screen-reader spot-checks with NVDA (Windows) and VoiceOver (macOS / iOS).
- Color-contrast sampling on all text/background combinations.
- Manual review of zoom, reduced-motion, and dark-mode behavior.
Known Limitations
We are continuously improving. Areas where we are actively working:
- Animated hero canvases on the home and contact pages use Three.js and may not be fully described to screen readers. Each canvas is marked
aria-hidden="true"and is purely decorative; the same content is reachable in static form below the hero. - Embedded PDFs (CPTED sample reports, contracts) may not be fully tagged. Please request an accessible alternative format if needed.
- Third-party widgets (CallRail call tracker, Google Analytics) include scripts we do not author. We monitor for accessibility issues and report them to the vendors.
Feedback & Accommodation Requests
If you encounter an accessibility barrier on our site, or if you need an alternative format for any content (large-print proposal, plain-text contract, captioned video walkthrough), please contact us. We aim to respond within 2 business days.
Multifamily Top Security — Accessibility
Email: info@tellprojectstx.com (subject line: “Accessibility”)
Phone: (832) 591-7991
Mail: 5328 Prudence Dr, Houston, TX 77045
When you contact us, please include: (a) the page URL or description, (b) the issue you encountered, (c) the assistive technology, browser, and operating system you were using, and (d) the format in which you would like to receive a response.
Enforcement Procedure
If we are unable to resolve an accessibility concern to your satisfaction, you may contact the U.S. Department of Justice Civil Rights Division (ada.gov) regarding alleged violations of the Americans with Disabilities Act.
Ongoing Commitment
Accessibility is not a one-time project. As we add new pages, services, blog posts, and location coverage, we apply the same standards. New components are reviewed against WCAG 2.2 AA before they go live, and this statement is updated when our scope or testing approach materially changes.