Skip to content
https://cloudavize5stg.wpenginepowered.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
73
GRADE
C
FIX
6
REVIEW
6
PASS
12
INFO
0
Checks
24
12 PASS 6 REVIEW 6 FIX
D
Tabindex Anti-Patterns
Action
0 positive, 17 -1-on-focusable
FIX
0 positive, 17 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <button id="e-n-tab-title-1049118252">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="e-n-tab-title-1049118253">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="e-n-tab-title-1049118254">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="e-n-tab-title-1049118255">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="e-n-tab-title-1049118256">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="e-n-tab-title-1049118257">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="e-n-tab-title-1049118258">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="e-n-tab-title-1049118259">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="e-n-tab-title-958063022">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="e-n-tab-title-958063023">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="e-n-tab-title-958063024">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="e-n-tab-title-958063025">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="e-n-tab-title-958063026">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="e-n-tab-title-958063027">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="e-n-tab-title-958063028">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="e-n-tab-title-958063029">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="e-n-tab-title-9580630210">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
8 landmarks
REVIEW
8 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

B
Form Accessibility
10 of 10 controls have issues
REVIEW
10 of 10 controls have issues
Warning::
10 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="text-69">; <input type="email" name="email-564">; <input type="text" name="text-352">; <input type="text" name="text-180">; <textarea name="textarea-218">; <input type="text" name="text-69">; <input type="email" name="email-564">; <input type="text" name="text-352">; <input type="text" name="text-180">; <textarea name="textarea-218">
10 controls
0 labeled
10 placeholder only
0 unlabeled
ControlTypeLabelMethod
text-69text(Enter Full Name)placeholder only
email-564email(Email Address)placeholder only
text-352text(Company Name)placeholder only
text-180text(Phone Number)placeholder only
textarea-218textarea(How Can We Help?)placeholder only
text-69text(Enter Full Name)placeholder only
email-564email(Email Address)placeholder only
text-352text(Company Name)placeholder only
text-180text(Phone Number)placeholder only
textarea-218textarea(How Can We Help?)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="text-69">; <input type="email" name="email-564">; <input type="text" name="text-352">; <input type="text" name="text-180">; <textarea name="textarea-218">; <input type="text" name="text-69">; <input type="email" name="email-564">; <input type="text" name="text-352">; <input type="text" name="text-180">; <textarea name="textarea-218">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

B
Iframe Accessibility
2/2 iframe(s) missing title; 0 placeholder(s)
REVIEW
2/2 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://www.google.com/maps/embed?pb=!1m18!1m12!1m3!1d859104.0816611499!2d-97.6…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 84/100 — 5 failing, 26 passed
REVIEW
84

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Jordan Bitancor Administrative Assistant As the Administrative Assistant at Cl… div.elementor-column > div.elementor-widget-wrap > div.elementor-element > div.swiper

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > button.vs-menu-toggle div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > button.vs-menu-toggle

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.elementor-column > div.elementor-widget-wrap > div.elementor-element > iframe div.elementor-column > div.elementor-widget-wrap > div.elementor-element > iframe

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
As the top IT managed service provider in Dallas, TX since 2019, Cloudavize has… div.elementor-element > div.elementor-widget-container > div.title-area > p.desc
About Us div.elementor-element > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
Contact Us form.wpcf7-form > div.form-wrap1 > div.form-style1 > h2.form-title
Or claim your free consultation today! div.form-wrap1 > div.form-style1 > div > a
24 HOURS SERVICE AVAILABLE  div.elementor-element > div.call-media > div.media-body > span.call-media__label
Why Choose Cloudavize For Dallas Managed IT Services div.elementor-element > div.elementor-widget-container > div.title-area > h2.sec-title3
READ MORE div.row > div.col-xl-4 > div.feature-style2 > a.link-btn
GET A FREE QUOTE FOR IT SOLUTIONS div.elementor-element > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
div.e-n-tabs > div.e-n-tabs-heading > button#e-n-tab-title-1049118251 > span.e-n-tab-title-text div.e-n-tabs > div.e-n-tabs-heading > button#e-n-tab-title-1049118251 > span.e-n-tab-title-text
div#accordionStyle6ad6cb4509099 > div.accordion-item > div#heading6968c986ad6cb4509099 > button.accordion-button div#accordionStyle6ad6cb4509099 > div.accordion-item > div#heading6968c986ad6cb4509099 > button.accordion-button
div.e-n-tabs > div.e-n-tabs-heading > button#e-n-tab-title-958063021 > span.e-n-tab-title-text div.e-n-tabs > div.e-n-tabs-heading > button#e-n-tab-title-958063021 > span.e-n-tab-title-text
WHAT DALLAS SAYS ABOUT OUR MANAGED IT SERVICES div.elementor-element > div.elementor-widget-container > div.title-area > p.sec-subtitle
17. August, 2022. div.ti-inner > div.ti-review-header > div.ti-profile-details > div.ti-date
20. October, 2022. div.ti-inner > div.ti-review-header > div.ti-profile-details > div.ti-date
2. November, 2022. div.ti-inner > div.ti-review-header > div.ti-profile-details > div.ti-date
FAQS div.elementor-element > div.elementor-widget-container > div.title-area > p.sec-subtitle
What are Managed IT Services? div#accordionLayout1 > div.accordion-item > h2#accHead1 > button.accordion-button
WEEKLY UPDATES div.elementor-element > div.elementor-widget-container > div.title-area > p.sec-subtitle
div.menu-links-container > ul#menu-links > li#menu-item-191 > a div.menu-links-container > ul#menu-links > li#menu-item-191 > a
div.menu-links-container > ul#menu-links > li#menu-item-16643 > a div.menu-links-container > ul#menu-links > li#menu-item-16643 > a
div.menu-links-container > ul#menu-links > li#menu-item-19117 > a div.menu-links-container > ul#menu-links > li#menu-item-19117 > a
div.menu-links-container > ul#menu-links > li#menu-item-11932 > a div.menu-links-container > ul#menu-links > li#menu-item-11932 > a
div.menu-links-container > ul#menu-links > li#menu-item-11933 > a div.menu-links-container > ul#menu-links > li#menu-item-11933 > a
div.menu-links-container > ul#menu-links > li#menu-item-12008 > a div.menu-links-container > ul#menu-links > li#menu-item-12008 > a
div.menu-links-container > ul#menu-links > li#menu-item-187 > a div.menu-links-container > ul#menu-links > li#menu-item-187 > a
div.menu-links-container > ul#menu-links > li#menu-item-18775 > a div.menu-links-container > ul#menu-links > li#menu-item-18775 > a
div.menu-services-container > ul#menu-services > li#menu-item-19832 > a div.menu-services-container > ul#menu-services > li#menu-item-19832 > a
div.menu-services-container > ul#menu-services > li#menu-item-11934 > a div.menu-services-container > ul#menu-services > li#menu-item-11934 > a
div.menu-services-container > ul#menu-services > li#menu-item-11936 > a div.menu-services-container > ul#menu-services > li#menu-item-11936 > a
div.menu-services-container > ul#menu-services > li#menu-item-11937 > a div.menu-services-container > ul#menu-services > li#menu-item-11937 > a
div.menu-services-container > ul#menu-services > li#menu-item-11938 > a div.menu-services-container > ul#menu-services > li#menu-item-11938 > a
div.menu-services-container > ul#menu-services > li#menu-item-11939 > a div.menu-services-container > ul#menu-services > li#menu-item-11939 > a
div.menu-services-container > ul#menu-services > li#menu-item-11940 > a div.menu-services-container > ul#menu-services > li#menu-item-11940 > a
div.menu-services-container > ul#menu-services > li#menu-item-11941 > a div.menu-services-container > ul#menu-services > li#menu-item-11941 > a
div.menu-locations1-container > ul#menu-locations1 > li#menu-item-11982 > a div.menu-locations1-container > ul#menu-locations1 > li#menu-item-11982 > a
div.menu-locations1-container > ul#menu-locations1 > li#menu-item-11983 > a div.menu-locations1-container > ul#menu-locations1 > li#menu-item-11983 > a
div.menu-locations1-container > ul#menu-locations1 > li#menu-item-11991 > a div.menu-locations1-container > ul#menu-locations1 > li#menu-item-11991 > a
div.menu-locations1-container > ul#menu-locations1 > li#menu-item-11992 > a div.menu-locations1-container > ul#menu-locations1 > li#menu-item-11992 > a
div.menu-locations1-container > ul#menu-locations1 > li#menu-item-16984 > a div.menu-locations1-container > ul#menu-locations1 > li#menu-item-16984 > a
div.menu-locations1-container > ul#menu-locations1 > li#menu-item-11984 > a div.menu-locations1-container > ul#menu-locations1 > li#menu-item-11984 > a
div.menu-locations1-container > ul#menu-locations1 > li#menu-item-11985 > a div.menu-locations1-container > ul#menu-locations1 > li#menu-item-11985 > a
div.menu-locations1-container > ul#menu-locations1 > li#menu-item-11986 > a div.menu-locations1-container > ul#menu-locations1 > li#menu-item-11986 > a
div.menu-locations1-container > ul#menu-locations1 > li#menu-item-11987 > a div.menu-locations1-container > ul#menu-locations1 > li#menu-item-11987 > a
div.menu-locations1-container > ul#menu-locations1 > li#menu-item-11988 > a div.menu-locations1-container > ul#menu-locations1 > li#menu-item-11988 > a
div.menu-locations1-container > ul#menu-locations1 > li#menu-item-11989 > a div.menu-locations1-container > ul#menu-locations1 > li#menu-item-11989 > a
div.menu-locations2-container > ul#menu-locations2 > li#menu-item-11994 > a div.menu-locations2-container > ul#menu-locations2 > li#menu-item-11994 > a
div.menu-locations2-container > ul#menu-locations2 > li#menu-item-11995 > a div.menu-locations2-container > ul#menu-locations2 > li#menu-item-11995 > a
div.menu-locations2-container > ul#menu-locations2 > li#menu-item-11996 > a div.menu-locations2-container > ul#menu-locations2 > li#menu-item-11996 > a
div.menu-locations2-container > ul#menu-locations2 > li#menu-item-11997 > a div.menu-locations2-container > ul#menu-locations2 > li#menu-item-11997 > a
div.menu-locations2-container > ul#menu-locations2 > li#menu-item-11998 > a div.menu-locations2-container > ul#menu-locations2 > li#menu-item-11998 > a
div.menu-locations2-container > ul#menu-locations2 > li#menu-item-15830 > a div.menu-locations2-container > ul#menu-locations2 > li#menu-item-15830 > a
div.menu-locations2-container > ul#menu-locations2 > li#menu-item-11999 > a div.menu-locations2-container > ul#menu-locations2 > li#menu-item-11999 > a
div.menu-locations2-container > ul#menu-locations2 > li#menu-item-12000 > a div.menu-locations2-container > ul#menu-locations2 > li#menu-item-12000 > a
div.menu-locations2-container > ul#menu-locations2 > li#menu-item-12001 > a div.menu-locations2-container > ul#menu-locations2 > li#menu-item-12001 > a
div.menu-locations2-container > ul#menu-locations2 > li#menu-item-12002 > a div.menu-locations2-container > ul#menu-locations2 > li#menu-item-12002 > a
div.menu-locations2-container > ul#menu-locations2 > li#menu-item-12003 > a div.menu-locations2-container > ul#menu-locations2 > li#menu-item-12003 > a
div.menu-locations2-container > ul#menu-locations2 > li#menu-item-17315 > a div.menu-locations2-container > ul#menu-locations2 > li#menu-item-17315 > a

These are opportunities to improve the legibility of your content.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.apo-ucar-on html.apo-ucar-on

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A+
Heading Hierarchy
73 headings
PASS
73 headings
Info::
Single H1 present
  • H1 Managed IT Services Dallas - Cloudavize
  • H2 Have Peace Of Mind And Grow Your Business With Our Comprehensive IT Services
  • H2 Dallas Managed IT Services and IT Support
  • H2 Contact Us
  • H2 Claim Your Free Consultation Today!
  • H2 Why Choose Cloudavize For Dallas Managed IT Services
  • H3 Expertise at Fingertips
  • H3 Saves You Money
  • H3 Helps Mitigate Downtime
  • H3 Strategic Consulting
  • H3 Fixed Fee Costs
  • H3 Dedicated Team
  • H3 Proactive Maintenance
  • H3 Adherence to SLA
  • H3 Comprehensive IT Support
  • H2 What Dallas Managed Service Provider Has To Offer
  • H2 Achieve Quick and Better Outcomes With Our Managed IT Service Model
  • H2 Industries Served by Cloudavize as Dallas Managed IT Service Provider
  • H2 Offering Exceptional Managed IT Services in DFW Cities
  • H2 WE HAVE EXPERT TEAM
  • H3 Cody Sukosky
  • H3 Carl Tagle
  • H3 Vu Do
  • H3 Michael Barbin
  • H3 Mark Joseph Cabadin
  • H3 Ara Carina Adam
  • H3 Carl Labrador
  • H3 Vincent Ortiz
  • H3 Jorenzo Lucero
  • H3 Jordan Bitancor
  • H2 Jorenzo Lucero
  • H2 Jordan Bitancor
  • H2 Cody Sukosky
  • H2 Carl Tagle
  • H2 Cody Liang
  • H2 Mark Cabrera
  • H2 Michael Barbin
  • H2 Mark Joseph Cabadin
  • H2 Ara Carina Adam
  • H2 Carl Labrador
  • H2 Vincent Ortiz
  • H2 Jorenzo Lucero
  • H2 Jordan Bitancor
  • H2 Cody Sukosky
  • H2 Carl Tagle
  • H2 Need A Consultation?
  • H2 CUSTOMER’S FEEDBACK
  • H2 Our Partners For Managed IT Services In Dallas
  • H2 Awards and Certification Qualifying Us As IT Managed Service Providers In Dallas
  • H2 Frequently Asked Question
  • H2 What are Managed IT Services?
  • H2 What Does an MSP Do?
  • H2 What are the Benefits of hiring Managed Service Provider?
  • H2 How Much Does Managed IT Service Cost at Cloudavize?
  • H2 Are Managed IT Services Worth IT?
  • H2 Can I Choose a Month-to-Month Contract with Cloudavize?
  • H2 LATEST BLOG
  • H3 What is IT Automation?
  • H3 Managed IT Services: Definition, Benefits, Costs, Types and Future
  • H3 How Much Does IT Outsourcing Cost In 2025?
  • H3 What is an IT Service Provider? Types, Importance, and Requirements
  • H3 Information Technology (IT):Definition, Importance, Types, Examples and More
  • H3 IT Support Technician: Roles, Skills, Qualifications & Career
  • H3 IT Services: Definition, Types, Importance and Trends
  • H3 What Is IT Consulting? A Complete Guide
  • H3 What is IT Support?
  • H3 10 Top Benefits of Hiring a Managed Service Provider (MSP)
  • H3 What is MSP (Managed Service Provider)?
  • H2 Where Do You Stand with our Managed IT Services?
  • H2 Contact Us
  • H3 Office Address
  • H3 Working Hours
  • H3 Contact Us
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
3 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 3 all-caps heading(s)
A+
Alt Text Quality
All 162 images OK
PASS
All 162 images OK
Info::
162 image(s) with good alt text
162 images 162 good alt text
All images have appropriate alt text.
A
Form Input Types
2 input(s) using type=text where a specific type would help
PASS
2 input(s) using type=text where a specific type would help
Info::
Input "text-180" should use type="tel" (currently type="text")
Field name "text-180" suggests type="tel". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="tel">.
Info::
Input "text-180" should use type="tel" (currently type="text")
Field name "text-180" suggests type="tel". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="tel">.
A+
Form Input Quality
10 form control(s) checked, no input-semantic issues
PASS
10 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 110 visible text node(s) render at >= 12 CSS pixels
PASS
All 110 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Managed IT Services …19.46:13.0:1
#000000
#F5F6FB
Pass
h2 Have Peace Of Mind A…19.46:13.0:1
#000000
#F5F6FB
Pass
h2 Your Business With O…19.46:13.0:1
#000000
#F5F6FB
Pass
h2 Dallas Managed IT Se…19.46:13.0:1
#000000
#F5F6FB
Pass
h2 Contact Us19.46:13.0:1
#000000
#F5F6FB
Pass
h2 Why Choose Cloudaviz…19.46:13.0:1
#000000
#F5F6FB
Pass
h2 What Dallas Managed …19.46:13.0:1
#000000
#F5F6FB
Pass
h2 Achieve Quick and Be…19.46:13.0:1
#000000
#F5F6FB
Pass
h2 Industries Served by…19.46:13.0:1
#000000
#F5F6FB
Pass
h2 Offering Exceptional…19.46:13.0:1
#000000
#F5F6FB
Pass
h2 WE HAVE EXPERT TEAM19.46:13.0:1
#000000
#F5F6FB
Pass
h2 Jorenzo Lucero19.46:13.0:1
#000000
#F5F6FB
Pass
h2 Jordan Bitancor19.46:13.0:1
#000000
#F5F6FB
Pass
h2 Carl Tagle19.46:13.0:1
#000000
#F5F6FB
Pass
h2 Cody Liang19.46:13.0:1
#000000
#F5F6FB
Pass
h2 Mark Cabrera19.46:13.0:1
#000000
#F5F6FB
Pass
h2 Michael Barbin19.46:13.0:1
#000000
#F5F6FB
Pass
h2 Mark Joseph Cabadin19.46:13.0:1
#000000
#F5F6FB
Pass
h2 Ara Carina Adam19.46:13.0:1
#000000
#F5F6FB
Pass
h2 Carl Labrador19.46:13.0:1
#000000
#F5F6FB
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback