Section 01
Executive Summary
Morton Technology Consulting conducted a WCAG 2.1 Level AA accessibility audit of the City of Florida City's official website (floridacityfl.gov) on May 17, 2026. Florida City (population ≈13,200) serves as the gateway community to the Florida Keys and Everglades National Park. Three pages were reviewed: the homepage, the Community Development Documents page, and the City Information page.
Overall Conformance
The site does not conform to WCAG 2.1 Level AA. Seven distinct failure categories were identified. Critical failures include a missing page language declaration (which affects every page on the site) and a library of 55 inaccessible PDF permit and zoning documents that are required for public business with the City.
Business & Legal Risk
Under the DOJ's 2024 Title II web accessibility rule, local governments with populations under 50,000 face a compliance deadline of April 26, 2027 — approximately 11 months from this audit date. Non-compliance exposes the City to DOJ complaint investigations, private litigation under Title II, and complications with CDBG grant civil rights certifications. The PDF library failure is the most acute risk: blind residents and contractors cannot access any of the 55 required government forms.
Recommended Next Steps
- Add
lang="en" to the HTML root element — a 30-minute fix that improves every page
- Remediate the PDF library using Adobe Acrobat Pro or axesPDF (phased over 60–90 days)
- Fix "Read More" and "View" link text with descriptive
aria-label attributes
- Engage a full Parallax audit to cover all site pages before the April 2027 deadline
Section 02
Methodology
Automated Testing
Automated checks were performed using the axe-core 4.x rule set — the industry standard integrated into WAVE, Deque's browser extension, and Google Lighthouse. Automated testing reliably detects approximately 30–40% of WCAG failures. Manual testing is required for the remainder.
Manual Testing
Manual testing tools and methods
| Method |
Tools |
What it finds |
| Keyboard navigation |
Tab, Shift+Tab, Arrow keys, Enter, Escape |
Focus order, keyboard traps, missing focus indicators |
| Screen reader (Windows) |
NVDA 2024.1 + Firefox |
Landmark navigation, heading structure, link lists, image descriptions |
| Screen reader (macOS) |
VoiceOver + Safari |
Cross-platform SR consistency, ARIA implementation |
| Color contrast |
WebAIM Contrast Checker + DevTools eyedropper |
Text/background ratio failures (4.5:1 normal, 3:1 large text) |
| PDF inspection |
Adobe Acrobat Pro Accessibility Checker |
Tags, reading order, language, form field labels |
Pages Audited
| Page | URL | Notes |
| Homepage |
floridacityfl.gov/ |
Hero, news feed, navigation, footer |
| Community Development Documents |
floridacityfl.gov/community-development-documents |
55 PDF permit and zoning documents |
| City Information |
floridacityfl.gov/city-information |
ADA statement, Commission agendas, city services |
Section 03
Findings
The <html> root element on all audited pages lacks a lang attribute. The page opens as:
<html>
<head>
<title>City of Florida City</title>
Screen reading software — NVDA, JAWS, VoiceOver — uses the lang attribute to select the correct speech synthesizer voice and apply appropriate pronunciation rules. Without it, screen readers may default to the OS language setting, producing incorrect pronunciation of English content. This is especially significant for Florida City's Spanish-speaking resident population, for whom content may be rendered in the wrong language entirely.
This is a Level A failure — the most foundational accessibility tier.
Remediation
<html lang="en">
Single template change in Jux-CMS propagates to all pages.
Estimated effort: 0.5 hours.
The Community Development Documents page hosts 55 PDFs required for public business with the City — permit applications, zoning codes, contractor forms, and affidavits. Inspection of a representative sample (Sitework_Application.pdf) via Adobe Acrobat Accessibility Checker reveals:
| PDF Feature | Status | WCAG Impact |
Structure tags (/StructTreeRoot) |
Absent |
Screen readers receive unstructured character stream |
Document language (/Lang) |
Absent |
SR cannot select correct voice/pronunciation |
| Interactive form fields (AcroForm) |
Absent |
Form areas not keyboard-accessible or SR-navigable |
Image alt text (/Alt entries) |
Absent |
City seal and graphics invisible to screen readers |
| Reading order defined |
Absent |
Multi-column layouts read in wrong order |
| Native text content |
Present |
Not a scanned image — text is remediable |
A blind contractor cannot read, complete, or submit any of these 55 required government forms using a screen reader. Title II prohibits imposing a burden that requires a person with a disability to seek sighted assistance to complete government business.
Remediation
Immediate (week 1): Add a phone number and email address on the Community Development Documents page for accessible format requests — this provides an equivalent accommodation while remediation proceeds.
Medium-term (30–90 days): Remediate PDFs using Adobe Acrobat Pro DC's Make Accessible wizard or axesPDF batch tagging tool. Process high-traffic permit applications first, then zoning codes.
Estimated effort: 60–120 hours for all 55 documents.
The homepage renders four identical "Read More" links in the News & Updates section. All carry no aria-label, aria-labelledby, or title attribute:
<a href="/news/notice-of-public-hearing-cdbg-first-public-hearing">Read More</a>
<a href="/news/joint-commission-agenda-review-meeting-may-7-2026">Read More</a>
<a href="/news/city-of-florida-city-joint-commission-agenda-review-meeting">Read More</a>
Additionally, 55 links on the Community Development Documents page are all labeled "View" with no distinguishing text.
Screen reader users commonly use their reader's Links List feature (NVDA: Insert+F7) to scan all links on a page. When all links in a section read identically ("Read More" / "View"), users must navigate to each link and listen to surrounding context — a process 3–5× slower than sighted scanning.
Remediation
<!-- Option A: aria-label -->
<a href="/news/notice-of-public-hearing-cdbg-first-public-hearing"
aria-label="Read more about CDBG First Public Hearing Notice">
Read More
</a>
<!-- Option B: visually hidden text -->
<a href="/news/...">
Read More
<span class="sr-only">about CDBG First Public Hearing</span>
</a>
Estimated effort: 4 hours (CMS template modification + QA).
Three distinct failure patterns were identified:
Pattern A — File name used as alt text:
<img alt="marketing.png" src="/uploads/..."> <!-- describes filename, not content -->
<img alt="megaphone" src="/uploads/..."> <!-- generic object, not informative -->
Pattern B — Functional logo missing alt text entirely (dark mode variant):
<!-- Dark logo linked to homepage — no alt attribute: -->
<a href="/">
<img src="/uploads/1771694582914-logo-dark.png">
</a>
<!-- Light logo correctly labeled: -->
<a href="/">
<img alt="City of Florida City logo — return to homepage"
src="/uploads/logo-light.png">
</a>
Dark-mode users receive no announcement when their screen reader encounters the logo link — only the raw URL / is read aloud.
Recommended Alt Text
| Image | Current alt | Correct alt |
| Dark logo (linked) |
absent |
"City of Florida City — return to homepage" |
| Megaphone / announcement icon |
"megaphone" |
"Announcements" or "" if purely decorative |
| marketing.png (news image) |
"marketing.png" |
Describe what the photo shows; "" if decorative |
| City seal (non-functional) |
absent |
"" (decorative — no additional information) |
Estimated effort: 2 hours (content editor review).
Every page contains two identical <nav> elements (desktop and mobile) plus two repeated footer link groups ("Useful Links" and "More Links"), none of which carry distinguishing aria-label attributes:
<nav> <!-- desktop navigation — no aria-label -->
<ul>...</ul>
</nav>
<nav> <!-- mobile navigation — identical content, no aria-label -->
<ul>...</ul>
</nav>
NVDA's landmark navigation (D key) presents both as "navigation" with no way to distinguish them. Keyboard-only users must Tab through all navigation links twice before reaching main content. The skip navigation link (Skip to main content) is present and mitigates this on initial load — but not when returning to the top of the page.
Remediation
<nav aria-label="Primary navigation">...</nav>
<nav aria-label="Mobile navigation" aria-hidden="true">
<!-- Hidden from accessibility tree when desktop nav is active -->
</nav>
Toggle aria-hidden on the inactive navigation via JavaScript as viewport changes.
Estimated effort: 2 hours.
The site footer on all pages reads only: "© 2026 City of Florida City. All rights reserved. | Made with Jux-CMS by XSSIT" — no accessibility statement link, no ADA coordinator contact, no mechanism for reporting barriers.
The City Information page does contain an "ADA Grievance Process" section with a grievance form, but this page is not linked from the footer, the homepage, or the primary navigation. Under the DOJ's 2024 Title II rule, entities must provide a notice of nondiscrimination and a means for requesting accessible materials — burying it inside an inner page fails this requirement.
Remediation
<footer>
...
<a href="/city-information#ada-statement">Accessibility / ADA</a>
</footer>
Estimated effort: 1 hour.
The Community Development Documents page skips from H1 directly to H3 for all section headings, omitting H2 entirely:
H1: Community Development Documents
H3: Building Applications ← should be H2
H3: Additional Building Forms ← should be H2
H3: Community Development Applications ZONING ← should be H2
H3: Zoning Codes ← should be H2
Screen reader users navigating by headings (NVDA: H key) expect a logical hierarchy. A skipped level creates confusion about document structure and may cause users to assume they have missed content above the H3 headings.
Remediation
Change section headings from <h3> to <h2>. Apply CSS styling if the visual size of H2 differs from the intended design — never use a lower heading level for visual purposes.
Estimated effort: 0.5 hours.
Section 04
Remediation Roadmap
| # |
Finding |
Effort |
Impact |
Priority |
| 1 |
Missing lang attribute |
0.5 hr |
High — all users, all pages |
Do now |
| 3 |
Generic link text |
4 hr |
High — blocks SR navigation |
Sprint 1 |
| 5 |
Duplicate nav without ARIA |
2 hr |
High — keyboard + SR users |
Sprint 1 |
| 4 |
Image alt text |
2 hr |
Medium — blind users |
Sprint 1 |
| 7 |
Heading level skip |
0.5 hr |
Medium — SR navigation |
Sprint 1 |
| 6 |
Accessibility statement |
1 hr |
Regulatory compliance |
Sprint 1 |
| 2 |
PDF library (55 docs) |
60–120 hr |
Critical — document access |
60–90 day phase |
Phased Approach
Phase 1 — Quick Wins (Weeks 1–2)
A developer addresses Findings 1, 5, and 7 via CMS template changes — single changes that propagate sitewide. A content editor addresses Findings 3, 4, and 6. Estimated total: 10 hours.
Phase 2 — PDF Remediation (Days 30–90)
Building and Zoning Department staff process PDFs through Adobe Acrobat Pro's Make Accessible workflow, prioritizing permit applications (highest public use), then zoning codes, then affidavits. Estimated total: 60–120 hours.
Phase 3 — Verification (Month 3)
Full re-testing of Phase 1 remediations with NVDA and keyboard-only navigation. Interim PDF audit to confirm remediation quality. Estimated: 8 hours.
Phase 4 — Final Conformance (Before April 2027)
Full site re-audit covering all pages. Conformance statement published to the site's accessibility page. DOJ deadline met.
Total estimated remediation: 78–138 developer and content-editor hours across three months — achievable well before the April 26, 2027 DOJ deadline.
Section 05
About Morton Technology Consulting
Morton Technology Consulting LLC provides WCAG 2.1 Level AA accessibility audits for state and local government agencies under the Parallax service offering. Our audits deliver what automated scanners cannot: real findings from real assistive technology use, with remediation guidance your IT department can act on immediately.
Full Parallax Audit
A full engagement covers your complete public-facing web presence — not just three pages. The DOJ Title II deadline for local governments is April 26, 2027. Fixed fee — no hourly overages, no scope creep.
Automated axe-core scan across all public pages
Manual keyboard + screen reader testing on all distinct templates
Color contrast analysis via DevTools sampling
PDF accessibility review (up to 25 documents)
Findings report with WCAG citations and remediation code examples
Prioritized remediation backlog (Jira / Azure DevOps export)
One re-test cycle after remediation
Conformance statement for your website
$9,500
Fixed fee — no hourly overages