Accessibility Statement
Alliant Association Management is committed to making alliantam.com usable by everyone, including people who rely on assistive technology.
Last reviewed: September 2, 2026
Accessibility is part of how we serve communities
We manage homeowner and condominium associations across Southwest Florida, and the residents, board members, and vendors who use this website have a wide range of abilities, devices, and browsing preferences. We treat digital accessibility as an ongoing operational responsibility, not a one-time project.
Our goal is that anyone can find information about our services, reach the right office, submit a form, and contact our team without barriers.
Conformance status
The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA.
alliantam.com is designed and built to conform with WCAG 2.1 Level AA. “Conform” means the content meets the applicable success criteria at that level. Because the site is updated regularly with new pages, news posts, and documents, we treat conformance as a continuously maintained standard and re-check pages as they change.
Measures we take to support accessibility
- Accessibility requirements are included in our website design and development process rather than added afterward.
- Color palettes, type sizes, and interactive states are checked against WCAG 2.1 AA contrast minimums before they ship.
- New pages and templates are reviewed with automated tooling and manual keyboard and screen reader checks.
- Forms, navigation, and interactive components are built with semantic HTML and ARIA only where native semantics are insufficient.
- Staff who publish content are given guidance on writing descriptive link text, meaningful image alternative text, and correctly ordered headings.
- Accessibility feedback from residents and board members is routed to our team and addressed as a support priority.
Accessibility features of this site
Structure and navigation
- A logical heading hierarchy on every page, so screen reader users can navigate by structure.
- A visible “skip to main content” link as the first focusable element.
- Landmark regions (header, navigation, main, footer) identified for assistive technology.
- Consistent navigation and link labeling across pages.
Keyboard and focus
- All interactive elements — links, buttons, form fields, menus — are reachable and operable by keyboard alone.
- Visible focus indicators that meet contrast requirements, never removed for aesthetics.
- No keyboard traps, and no functionality that requires a mouse, hover, or pointer gesture.
Content and media
- Text alternatives for meaningful images; decorative images are hidden from assistive technology.
- Body text that reflows and remains readable when zoomed to 200% or resized to 400% at narrow widths.
- Form fields with programmatically associated labels, clear instructions, and error messages that identify the field and describe the fix.
- Documents and PDFs are provided in accessible formats where possible, and we will supply an alternative format on request.
- Motion is limited and respects the operating system’s reduced-motion preference.
How we test
We combine automated auditing with manual review, because automated tools alone cannot verify every WCAG success criterion.
WAVE (WebAIM)
No errors or contrast errors
Page-level evaluation of structure, alternative text, labeling, and contrast on our primary templates.
Google Lighthouse
Accessibility audits passing
Automated accessibility audits run against our key page templates as part of routine site review.
Automated results are supported by manual testing: keyboard-only navigation of every interactive component, screen reader review of page structure and forms, zoom and reflow checks, and verification of contrast on text, icons, and focus indicators.
Note on automated scores
A clean automated audit is a baseline, not a guarantee. Automated tools can detect roughly a third of WCAG issues, so we do not treat a passing score as the end of the review.
Compatibility with browsers and assistive technology
alliantam.com is designed to work with current versions of Chrome, Edge, Firefox, and Safari on desktop and mobile, used with the operating system’s built-in accessibility features and with common screen readers, including NVDA, JAWS, VoiceOver, and TalkBack.
The site may not perform as expected in browsers older than three versions, or in browsers with JavaScript disabled.
Known limitations
Despite our efforts, some limitations may remain. Where we are aware of an issue, we work to resolve it and can provide the information in another format in the meantime.
- Third-party services. Resident portal, payment processing, and document library tools are operated by outside vendors. We select vendors with accessibility in mind and raise issues with them, but we do not control their code.
- Embedded maps. Interactive map embeds may be difficult to use with a screen reader. Every office address and phone number is also provided as text on our contact page.
- Older documents. Some archived PDFs and association documents predate our current standards and may not be fully tagged. Contact us and we will provide an accessible version.
- User-generated content. Material submitted by third parties may occasionally lack alternative text or captions; we correct these as they are identified.
Feedback and assistance
We welcome your feedback on the accessibility of alliantam.com. If you encounter a barrier, need information in an alternative format, or need help completing a form, contact us and a member of our team will assist you directly.
Contact our team
We aim to respond to accessibility requests within two business days. Our offices are open Monday through Friday, 9am to 3pm.
Phone
(239) 454-1101
Online
alliantam.com/contact/
Mail
13831 Vector Ave, Fort Myers, FL 33907
When reporting an issue, it helps to include the page address, a description of the problem, and the browser and assistive technology you were using.
This statement was created on September 2, 2026 and is reviewed as the site changes.