Accessibility report for adiserorlando.com
Based on an automated WCAG 2.1 Level AA scan on September 21, 2026.
adiserorlando.com does not yet meet WCAG 2.1 Level AA, the accessibility standard written into U.S. and EU law. This automated scan found 3 types of barrier affecting people with disabilities.
On this page, the most frequent barrier is "Some content on the page isn't inside a recognized region (header, nav, main, footer, aside)" — found on 3 elements. In total the scan flagged 5 issues across 3 categories of WCAG 2.1 Level AA.
WCAG 2.1 Level AA is the standard U.S. courts apply under the ADA, and the law across the EU under the European Accessibility Act. These barriers block screen-reader, keyboard-only, and low-vision users — and every one of them is fixable. Here's how.
What needs fixing to meet the standard
An element uses a screen-reader role but is missing required information for that role.
WCAG 4.1.2 (Level A) EN 301 549 Affects screen-reader users
Why it matters: Custom controls (sliders, tabs, dialogs) need specific extra info to work properly with screen readers. Missing pieces = broken behavior.
How to fix it: Developer fix: 'this role requires additional aria-* attributes; check axe-core docs for the specific role'.
Get compliant, free
The free wcagcheckr browser extension finds every one of these issues on your own pages and gives you the fix recipe for each — at no cost. Run it, fix what it finds, and re-check this page anytime.
Own this site? Fix the issues, then re-scan — this report updates automatically, and comes down entirely once you pass.
The page doesn't declare what language it's in.
WCAG 3.1.1 (Level A) EN 301 549 Affects screen-reader users
Why it matters: Screen readers use this to pick the right voice and pronunciation rules. Without it, English content might be read with a French accent (or vice versa).
How to fix it: In your platform's site settings, find a 'Site language' option and set it (English = en, Spanish = es, etc.). Most modern platforms do this automatically — if it's missing, ask your developer to add lang='en' to the html element.
Some content on the page isn't inside a recognized region (header, nav, main, footer, aside).
Affects keyboard-only users
Why it matters: Screen-reader users navigate by these regions. Content outside any region can be missed when skimming.
How to fix it: Developer fix: 'wrap orphaned page content in semantic landmark elements (<main>, <aside>, <nav>) so it's reachable via landmark nav'.
This is an automated scan and catches a portion of accessibility barriers; full WCAG 2.1 Level AA conformance also requires manual and assistive-technology testing. See our methodology for what we do and don't claim.
Learn more
How this report was produced
This report is an automated scan of the page as it was publicly served on
,
using [email protected]. The captured page and these results are sealed with a
tamper-evident hash (eeaeb4893e4f036a…).
We report only what the page publicly returned at that time.
This seal is anchored to a trusted RFC-3161 timestamp via freetsa.org on . Independently verify this receipt →