Skip to main content

Accessibility snapshotroundrocktexas.gov

roundrocktexas.gov (opens in a new tab)

Automated accessibility check · Homepage · November 21, 2026

Does not yet meet WCAG 2.1 AA — the accessibility standard required of government websites.

roundrocktexas.gov
Homepage of roundrocktexas.gov as captured Nov 21, 2026

Compliance context

  • 50,000+ residents April 26, 2027
  • Under 50,000 and special districts April 26, 2028

Under the Department of Justice's rule for Title II of the ADA, WCAG 2.1 AA is the required standard for state and local government websites. Public entities serving 50,000 or more residents must conform by April 26, 2027, and entities serving fewer than 50,000 residents and special district governments by April 26, 2028. General ADA accessibility obligations already apply today.

Findings

Five issues, listed by impact. Three count toward the WCAG 2.1 AA requirement. The other two are best-practice checks — noted in this report, but beyond what the rule requires, and they don't affect the count.

Elements must meet enhanced color contrast ratio thresholds

Level AAA · beyond the AA requirement
Best practice

Who this is affecting

Users with more significant low vision benefit from the stricter 7:1 ratio.

What we found

Ensure the contrast between foreground and background colors meets WCAG 2 AAA enhanced contrast ratio thresholds

.elementor-element-d6d595b > .elementor-widget-container > .elementor-icon-list-items > .elementor-icon-list-item:nth-child(1) > a > .elementor-icon-list-text.elementor-element-d6d595b > .elementor-widget-container > .elementor-icon-list-items > .elementor-icon-list-item:nth-child(2) > a > .elementor-icon-list-text.elementor-element-cee9b52 > .elementor-widget-container > .elementor-icon-list-items > .elementor-icon-list-item:nth-child(1) > a > .elementor-icon-list-text+26 more

Not counted toward compliance.

All touch targets must be 24px large, or leave sufficient space

WCAG 2.2 · beyond the 2.1 AA requirement
WCAG 2.2

Who this is affecting

People with tremors or limited dexterity, and anyone on a phone, miss targets that are too small or too close together.

What we found

Ensure touch targets have sufficient size and space

.n2-activediv[aria-label="MyMeter"]div[aria-label="downtown"]+11 more

Not counted toward compliance.

Elements must meet minimum color contrast ratio thresholds

Level AA · required
Serious

Who this is affecting

People with low vision or color blindness struggle to read text that blends into its background.

What we found

Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds

#menu-1-311a0706 > .menu-item-605505.menu-item-home.current-menu-item > .elementor-item-active.elementor-item[aria-current="page"]#menu-1-311a0706 > .menu-item-605506.menu-item-type-post_type.menu-item-object-page > .elementor-item.menu-link#menu-1-311a0706 > .menu-item-605507.menu-item-type-post_type.menu-item-object-page > .elementor-item.menu-link+2 more

Links must have discernible text

Level A · required
Serious

Who this is affecting

Screen reader users hear “link” with no way to know where it leads.

What we found

Ensure links have discernible text

.post-823381 > .elementor-post__thumbnail__link.post-555511 > .elementor-post__thumbnail__link

Interactive controls must not be nested

Level A · required
Serious

Who this is affecting

Keyboard and assistive-tech users get stuck on or skip controls placed inside other controls.

What we found

Ensure interactive controls are not nested as they are not always announced by screen readers or can cause focus problems for assistive technologies

.n2-ss-slide-36

Method & coverage

What an automated scan can and can't see

This snapshot comes from an automated WCAG 2.1 AA check of the homepage at roundrocktexas.gov, run on Nov 21, 2026. Automated scanning is reliable at what it can see: color contrast, page structure, and the names and labels assistive technology depends on.

It also has limits. Automated checks detect roughly a third of WCAG issue types, and this scan covered one page. A full picture — forms, documents, and multi-step journeys — requires manual review by a person using assistive technology. That is the gap a full audit closes.

Next steps

  1. Share this report with your IT team or web vendor

    The fix guides above are free — your team or current vendor can start with them today.

  2. A full audit and remediation from Tino

    A manual audit covers what automated checks can't — forms, documents, keyboard journeys — and ends with a prioritized remediation plan in plain language.

  3. Purchasing through TIPS — no RFP

    Tino is a TIPS Awarded Vendor. Texas public entities can engage directly through TIPS contract 260105 — Technology Solutions — without running a separate RFP process.