EDO Accessibility Checker

WCAG 2.1 AA · ADA Title II web rule

Scan your site

Website accessibility readiness report

cedarbluffedo.example

Prepared for
Jordan Ellis
Scanned
October 13, 2026
Pages scanned
4
Standard
WCAG 2.1 Level AA
Compliance date
April 26, 2027 or 2028By city size, see below

Several problems would block some visitors with disabilities. Plan the fixes now so they are done before your compliance date.

  • 4Critical problems
  • 5Serious problems
  • 10Moderate and minor
  • 7Checks passed
  • 13Checks for a person

Fix these first

Problems the scan confirmed, most serious first. Each one says how to fix it, so you can forward this report to your web team.

  1. Form fields without labels

    CriticalWCAG 1.3.1, 3.3.2

    Placeholder text disappears as soon as someone types and is often not announced, so prospects using screen readers or memory aids cannot tell what a field asks for.

    How to fix: Give every field a visible label connected to it. Placeholder text can stay as an example, but it cannot be the only label.

    Where the scan found it: 1 page, 4 items
    • Contact | Cedar Bluff EDO (4)Field "Name" (placeholder only)Field "Email address" (placeholder only)Field "Company" (placeholder only)

  2. Links with no name

    CriticalWCAG 2.4.4, 4.1.2

    Screen readers announce these as "link" and nothing more. It usually happens with logo and social media icons, so people cannot tell where the link goes.

    How to fix: Give icon links a text name: alt text on the logo image ("[EDO name] home") or an accessible label on each social icon ("Facebook").

    Where the scan found it: 1 page, 2 items
    • Home page (2)Link to /Link to facebook.com/cedarbluffedo

  3. Images missing alt text

    CriticalWCAG 1.1.1

    A screen reader has nothing to announce for these images, so a blind visitor misses what they show, from a site map to a photo of your industrial park.

    How to fix: Add alt text that says what the image shows and why it matters, such as "Aerial view of the 148-acre logistics park along I-20." Mark purely decorative images as decorative (empty alt) so screen readers skip them.

    Where the scan found it: 1 page, 1 item
    • Home page (1)Image cedar-bluff-logo.svg

  4. Clickable items the keyboard can't reach

    CriticalWCAG 2.1.1

    These items respond to a mouse click but cannot be reached with the Tab key, which locks out people who use a keyboard or switch device.

    How to fix: Use real links and buttons for anything clickable. If a custom element is unavoidable, give it a button role, make it focusable, and make Enter and Space activate it.

    Where the scan found it: 1 page, 1 item
    • Contact | Cedar Bluff EDO (1)"Call the EDO office"

  5. Text with too little contrast

    SeriousWCAG 1.4.3

    Light gray text, pale labels and thin type on white are hard to read for people with low vision, and for everyone on a phone in sunlight.

    How to fix: Darken the text or the background until regular text reaches 4.5:1 and large text reaches 3:1. Change it in your site-wide style settings so every page updates at once.

    Where the scan found it: 2 pages, 4 items
    • Home page (3)"Labor force within 30 minutes" 2.56:1, needs 4.5:1 (#9aa3ad on #ffffff)"Certified industrial land" 2.56:1, needs 4.5:1 (#9aa3ad on #ffffff)"Regional colleges train welders, …" 4.48:1, needs 4.5:1 (#777777 on #ffffff)
    • Available Sites | Cedar Bluff EDO (1)"Data updated quarterly by the EDO." 2.43:1, needs 4.5:1 (#a0a0a0 on #f7f7f2)

  6. Embedded content without a title

    SeriousWCAG 4.1.2

    Maps, property search tools and videos embedded without a title are announced as "frame," so screen reader users cannot tell what is inside.

    How to fix: Add a title to each embed that names what it is, such as title="Interactive map of available sites."

    Where the scan found it: 2 pages, 2 items
    • Home page (1)Embed from google.com
    • Available Sites | Cedar Bluff EDO (1)Embed from zoomprospector.com

  7. Moving content with no pause button

    SeriousWCAG 2.2.2

    Background video, sliders and tickers that move for more than 5 seconds need a pause control. Constant motion pulls attention from the content and can make people with vestibular conditions dizzy.

    How to fix: Add a visible, keyboard-reachable pause button to every background video and auto-advancing slider. Many site builders include one; check that it is turned on.

    Where the scan found it: 1 page, 2 items
    • Home page (2)Video cedar-bluff-aerial.mp4 (plays on its own, no pause button)Slider that advances on its own, no pause button

  8. Links marked by color alone

    SeriousWCAG 1.4.1

    Links inside paragraphs that differ from the text only by color are invisible to many people with color blindness.

    How to fix: Underline links in body text, or give them a color with at least 3:1 contrast against the surrounding text plus an underline on hover and focus.

    Where the scan found it: 1 page, 1 item
    • Home page (1)Link to /plan ("2026 strategic plan")
Show 11 more problems

  1. Zoom blocked on phones

    SeriousWCAG 1.4.4

    The page tells phones not to allow pinch zoom, so visitors with low vision cannot enlarge the text.

    How to fix: Remove maximum-scale=1 and user-scalable=no from the viewport setting in the page head.

    Where the scan found it: 1 page, 1 item
    • Home page (1)Viewport setting: width=device-width, initial-scale=1, maximum-scale=1

  2. Contact fields without autofill

    ModerateWCAG 1.3.5

    Autofill lets people with motor or memory disabilities complete name, email and phone fields without typing them out.

    How to fix: Add autocomplete values to personal fields, such as autocomplete="name", "email", "tel" and "organization".

    Where the scan found it: 1 page, 3 items
    • Contact | Cedar Bluff EDO (3)Field "Name"Field "Email address"Field "Company"

  3. Alt text that is a file name or placeholder

    ModerateWCAG 1.1.1

    Alt text like "DJI_0042" or "image" is read aloud word for word and tells the listener nothing.

    How to fix: Replace it with a short description of what the image shows. Drone and camera file names are a common slip when photos are uploaded in bulk.

    Where the scan found it: 1 page, 2 items
    • Home page (2)Image DJI_0042.jpg (alt="DJI_0042")Image park.jpg (alt="__wf_reserved_inherit")

  4. Missing or generic page title

    ModerateWCAG 2.4.2

    The page title is the first thing a screen reader announces and the name shown on browser tabs and in search results.

    How to fix: Give each page a unique title that names the page and your organization, such as "Available Sites | [EDO name]."

    Where the scan found it: 1 page, 1 item
    • Home page (1)Title is only "Home"

  5. Custom tab order

    ModerateWCAG 2.4.3

    A tabindex above zero makes the keyboard jump around the page out of reading order.

    How to fix: Remove positive tabindex values and arrange content so the code order matches the visual order.

    Where the scan found it: 1 page, 1 item
    • Contact | Cedar Bluff EDO (1)Field "Email address" (tabindex=3)

  6. Data tables without headers

    ModerateWCAG 1.3.1

    Without header cells, a screen reader reads a sites table as a stream of numbers with no column names attached.

    How to fix: Mark the top row (and first column, if needed) as header cells so each value is announced with its heading, such as "Acres: 148."

    Where the scan found it: 1 page, 1 item
    • Available Sites | Cedar Bluff EDO (1)Table with 3 rows and no header cells

  7. No "Skip to main content" link

    ModerateBest practiceWCAG 2.4.1

    Keyboard users have to Tab through every menu item on every page before reaching the content.

    How to fix: Add a "Skip to main content" link as the first item on the page. It can stay hidden until it receives keyboard focus.

    Where the scan found it: 3 pages, 3 items
    • Home page (1)The first thing you can Tab to is not a skip link
    • Available Sites | Cedar Bluff EDO (1)The first thing you can Tab to is not a skip link
    • Contact | Cedar Bluff EDO (1)The first thing you can Tab to is not a skip link

  8. Vague link text like "Learn more"

    ModerateBest practiceWCAG 2.4.4

    Screen reader users often move from link to link. A list of "Learn more" links gives no clue where each one goes.

    How to fix: Write link text that names the destination ("Explore available sites"), or add a hidden label that starts with the visible words, such as "Learn more about workforce."

    Where the scan found it: 2 pages, 4 items
    • Home page (2)Link to /workforce ("Learn more")Link to /sites ("Learn more")
    • Available Sites | Cedar Bluff EDO (2)Link to /sites/i20-logistics-park ("View details")Link to /sites/north-loop ("View details")

  9. Heading levels that skip

    ModerateBest practiceWCAG 1.3.1

    Jumping from an H2 to an H4 suggests a missing section and makes the page outline confusing to navigate.

    How to fix: Choose heading tags by outline level and control their size with your style settings.

    Where the scan found it: 1 page, 1 item
    • Home page (1)H2 then H4 "Workforce"

  10. No main content region

    ModerateBest practiceWCAG 1.3.1

    A main region lets screen reader users skip past the menu straight to the content.

    How to fix: Wrap each page's content (everything except header and footer) in a main element. Most site builders let you set this tag on a section.

    Where the scan found it: 1 page, 1 item
    • Home page (1)No <main> region on this page

  11. Document links that don't name the file type

    MinorBest practiceWCAG 2.4.4

    Visitors should know before clicking that a link opens a PDF or Word file, which may not work well with their assistive technology.

    How to fix: Add the file type and size to the link text, such as "Annual Report 2025 (PDF, 2 MB)."

    Where the scan found it: 1 page, 1 item
    • Home page (1)Link to /docs/annual-report-2025.pdf ("Annual Report 2025")

Page by page

How many types of problems the scan found on each page.

PageCriticalSeriousModerateMinor
Home pagecedarbluffedo.example2561
Available Sites | Cedar Bluff EDOcedarbluffedo.example/sites0230
Incentives | Cedar Bluff EDOcedarbluffedo.example/incentives0000
Contact | Cedar Bluff EDOcedarbluffedo.example/contact2030

Checks that need a person

A scanner cannot judge these, but the rule covers them. Each takes a few minutes; "How to check" walks through it.

Keyboard and focus

  • Use the whole site with only a keyboard

    CriticalWCAG 2.1.1, 2.1.2

    People who cannot use a mouse rely on a keyboard or devices that act like one.

    The scan found 2 items that may block or confuse keyboard users.

    How to check
    1. Click in the address bar, then press Tab over and over to move through the page.
    2. Open the main menu, the mobile menu and any dropdowns with Enter or Space, and close them with Esc.
    3. Reach and send the contact form, and play any video, without touching the mouse.
    4. You should never get stuck in one spot.

  • See what is selected while pressing Tab

    SeriousWCAG 2.4.7

    Without a visible focus indicator, keyboard users cannot tell where they are on the page.

    How to check
    1. Press Tab slowly through the home page.
    2. Each link and button should show a clear outline or highlight when selected, including on dark sections.

Zoom, color and reading

  • Read every page zoomed to 200% and 400%

    SeriousWCAG 1.4.4, 1.4.10

    Many visitors with low vision enlarge pages to read them.

    How to check
    1. On a desktop, press Ctrl and + (Cmd and + on a Mac) until the browser shows 200%. Text should grow without overlapping or getting cut off, and the menu should still work.
    2. At 400%, you should be able to read by scrolling only up and down. Maps and data tables may scroll sideways.

  • Read text on photos and video in every frame

    SeriousWCAG 1.4.3

    Bright frames in a hero video can wash out white headlines, and a scanner cannot measure text on moving images.

    The scan found 3 text items on photos, video or animation.

    How to check
    1. Look at headlines and buttons that sit on photos or background video.
    2. Watch the full video loop. Text must stay readable in the brightest frame; a dark overlay behind the text usually fixes this.

  • Keep stats and infographics as real text

    ModerateWCAG 1.4.5

    Screen readers cannot read text inside an image, and it blurs when people zoom.

    How to check
    1. Try to highlight the words with your mouse. If you cannot select them, they are part of an image.
    2. Logos are exempt. Charts and infographics need their key numbers written out nearby.

  • Show links, required fields and charts without relying on color

    ModerateWCAG 1.4.1

    About 1 in 12 men has some form of color blindness.

    How to check
    1. Required form fields should say "required" in words, not only show a red border.
    2. Charts and maps should use labels or patterns as well as color.

Video and motion

  • Caption every video with speech

    CriticalWCAG 1.2.2

    Deaf and hard of hearing visitors cannot follow your story without captions, and many people watch with the sound off.

    The scan found 4 videos on the pages it checked.

    How to check
    1. Play each video and turn on captions (CC).
    2. Captions should match what is said word for word and name who is speaking.
    3. Automatic captions from YouTube or Vimeo must be reviewed and corrected. Social posts and recorded board meetings count too.

  • Say aloud what videos show on screen

    SeriousWCAG 1.2.5

    Blind visitors hear the music but miss facts that only appear as text on screen.

    The scan found 4 videos on the pages it checked.

    How to check
    1. Play the video without looking at the screen.
    2. Every statistic, name, place and contact detail shown as on-screen text should also be spoken, or offered in a version with audio description.

  • Keep video free of rapid flashing

    CriticalWCAG 2.3.1

    Rapid flashing can trigger seizures in people with photosensitive epilepsy.

    The scan found 4 videos on the pages it checked.

    How to check
    1. Watch for strobe effects, lightning, fireworks or fast cuts between light and dark shots.
    2. Nothing should flash more than three times in one second.

Forms, documents and tools

  • Explain form errors in words

    SeriousWCAG 3.3.1, 3.3.3

    A prospect who cannot tell why a form failed gives up, and the EDO loses the lead.

    The scan found 7 form fields on the pages it checked.

    How to check
    1. Send your contact or site inquiry form with a required field empty and an email address missing the @.
    2. The form should say in text which field is wrong and how to fix it. A red border alone is not enough.

  • Make posted PDFs and documents accessible

    SeriousWCAG 1.1.1, 1.3.1

    Agendas, annual reports and incentive applications are core public information under the rule.

    The scan found 3 document links, including "Annual Report 2025", "Incentive Application (PDF)", "Incentive application (PDF, 240 KB)".

    How to check
    1. Open a recent PDF in Adobe Acrobat Pro and run the Accessibility Check.
    2. Scanned pages that are only pictures of paper always fail.
    3. Documents posted after your compliance date must be accessible, and applications people still use must be fixed even if they are older.

  • Check property search tools and maps

    SeriousWCAG 2.1.1, 1.1.1

    Site selection tools and maps are often the most-used features on an EDO site, and content a vendor provides counts as yours.

    Embedded tools found: google.com, zoomprospector.com.

    How to check
    1. Use only the Tab key to operate your site selection tool or interactive map.
    2. Check that the same sites or data also appear as plain text or a table on the page.
    3. Ask each vendor for an Accessibility Conformance Report (sometimes called a VPAT).

Requests and policy

  • Publish an accessibility page with a way to ask for help

    ModerateADA Title II

    The ADA requires you to provide information in another format when someone asks, and people need a way to ask.

    The scan found a link to an accessibility page.

    How to check
    1. Add an "Accessibility" link in the footer.
    2. The page should name the standard you follow (WCAG 2.1 AA) and give an email address and phone number for requests or problems, with a response time.

What passed

  • Every button has a name
  • Nothing plays sound on its own
  • Page language is set
  • Hidden items are skipped
  • No timed refresh
  • Pages have an H1 heading
  • No empty headings

Your compliance date

The federal rule sets the date by the population of the city or county your EDO belongs to, using the 2020 Census count.

City or county populationCompliance dateDays left
50,000 or moreApril 26, 2027195
Under 50,000, or a special districtApril 26, 2028561

Private nonprofit organizations fall under ADA Title III, which has no fixed date but uses the same standard in practice. A federal lawsuit filed May 21, 2026 asks the court to restore the original dates, one year earlier. Dates current as of October 13, 2026.

Next steps

  1. Forward this report to your web team or vendor. Each problem says how to fix it.
  2. Fix critical and serious problems first, starting with parts every page shares, such as the header, menu, footer and contact form. Fixing them once fixes every page.
  3. Work through the checks that need a person, especially keyboard use, video captions and documents.
  4. Publish an accessibility page with an email and phone number for requests, if you do not have one.
  5. Scan again after the fixes, and get a full manual audit before your compliance date.

What this scan can't tell you

This scan checked 4 pages of cedarbluffedo.example for problems a computer can detect. Automated tools find only part of what affects people with disabilities, so treat this report as a starting point, not a certification of compliance. It is not legal advice.