Accessibility report for doradoplaza.com
Based on an automated WCAG 2.1 Level AA scan on August 1, 2026.
doradoplaza.com does not yet meet WCAG 2.1 Level AA, the accessibility standard written into U.S. and EU law. This automated scan found 8 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 8 elements. In total the scan flagged 20 issues across 8 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
Some images on this page have no description for screen readers.
WCAG 1.1.1 (Level A) Section 508EN 301 549 Affects screen-reader users
Why it matters: Blind and low-vision users rely on screen readers to read pages aloud. When an image has no description, the screen reader either skips it entirely or reads out the file name — useless. Missing alt text is the #2 lawsuit-magnet category.
How to fix it: In your site editor, click each image and look for an 'Alt text' or 'Image description' field. Write a short sentence describing what the image shows or what it links to. For purely decorative images (dividers, background flourishes), enter empty alt text or check a 'decorative' box if the platform offers one.
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.
A dropdown menu has no description.
WCAG 4.1.2 (Level A) Section 508EN 301 549 Affects screen-reader and cognitive-disability users
Why it matters: Screen-reader users hear 'combo box, has popup' but not what the dropdown is for. They can't fill out forms reliably.
How to fix it: In your form editor, check that each dropdown has a visible label above or beside it. If your platform has separate label/field settings, both must be filled.
Some buttons or links are too small to tap reliably on touch screens.
WCAG 2.5.8 (Level AA) Affects low-vision and colorblind users
Why it matters: WCAG 2.2 requires touch targets to be at least 24×24 pixels. Small targets are a problem for users with hand tremors, large fingers, or motor disabilities. They're also frustrating for everyone.
How to fix it: In your editor, increase padding around small icon buttons. If your developer is involved, ask them to ensure all interactive elements have minimum 24×24 CSS pixels of clickable area.
An accessibility rule failed on this page.
Affects screen-reader users
Why it matters: Some users — particularly those using screen readers, keyboard-only navigation, or who have low vision or motor disabilities — may have trouble using this part of the page.
How to fix it: Share the technical rule ID with your developer. They can look up the full fix at https://dequeuniversity.com/rules/axe.
There are multiple footer regions on the page when there should be one.
Affects screen-reader users
Why it matters: Same as duplicate banner — confusing landmark navigation.
How to fix it: Developer fix: 'only one element should have role=contentinfo or be a top-level <footer>; remove duplicates'.
An accessibility rule failed on this page.
Affects screen-reader users
Why it matters: Some users — particularly those using screen readers, keyboard-only navigation, or who have low vision or motor disabilities — may have trouble using this part of the page.
How to fix it: Share the technical rule ID with your developer. They can look up the full fix at https://dequeuniversity.com/rules/axe.
The page tells mobile browsers users can't zoom in.
WCAG 1.4.4 (Level AA) EN 301 549 Affects low-vision and colorblind users
Why it matters: People with low vision rely on pinch-zoom to read small text. Disabling zoom is a real WCAG failure and a common lawsuit target.
How to fix it: In platform site settings, look for a 'Mobile zoom' or 'Pinch zoom' option and enable it. If your developer added user-scalable=no in a viewport meta tag, ask them to remove it.
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 (f0bc60f526e84056…).
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 →