Scan results for belkbot.com

Accessible

Congratulations! Your webpage is accessible with a score above 85. We’d love to work with you to help close any remaining accessibility gaps.

accessWidget is detected on the website
#
Element
Relevant
Successes
Failures
Score
1
The alt attribute is used to provide a text alternative for images. It is not meant to be used on elements other than images and therefore will not be read using screen-readers.
Yes
4
0
100

Code snapshots of successful elements

  • 1 
                <img elementtiming="nbf-header-logo-desktop" src="//images.squarespace-cdn.com/content/v1/68eea14c6cb28d11b6d0c1ca/ae453c66-7d44-42bf-a953-e03bbf017492/Belkbot+-+transparent+logo.png?format=1500w" alt="Belkbot Solutions" style="display:block" fetchpr...
  • 2 
                <img elementtiming="nbf-header-logo-desktop" src="//images.squarespace-cdn.com/content/v1/68eea14c6cb28d11b6d0c1ca/ae453c66-7d44-42bf-a953-e03bbf017492/Belkbot+-+transparent+logo.png?format=1500w" alt="Belkbot Solutions" style="display:block" fetchpr...
  • 3 
                <img data-stretch="false" data-src="https://images.squarespace-cdn.com/content/v1/68eea14c6cb28d11b6d0c1ca/74f3234c-b594-44eb-9515-a1661e464091/favicon.png" data-image="https://images.squarespace-cdn.com/content/v1/68eea14c6cb28d11b6d0c1ca/74f3234c-b...
  • 4 
                <img data-stretch="false" data-src="https://images.squarespace-cdn.com/content/v1/68eea14c6cb28d11b6d0c1ca/4e61af2a-c1da-4740-a103-a50e134332e9/bot.png" data-image="https://images.squarespace-cdn.com/content/v1/68eea14c6cb28d11b6d0c1ca/4e61af2a-c1da-...
#
Element
Relevant
Successes
Failures
Score
2
If content remains visible on the screen but assigned aria-hidden="true", it will be excluded from the accessibility tree. As a result, screen reader users will not have access to the same information as sighted users.
Yes
168
0
100

Code snapshots of successful elements

  • 1 
                <div id="siteWrapper" class="clearfix site-wrapper"> <div id="floatingCart" class="floating-cart hidden> <a href="/cart" class="icon icon--stroke icon--fill icon--cart sqs-custom-cart sqs-template-integrated-shopping-cart" data-test="continue-to-cart...
  • 2 
                <header data-test="header" id="header" class=" black header theme-col--primary " data-section-theme="black" data-controller="Header" data-current-styles="{ &quot;layout&quot;: &quot;navRight&quot;, &quot;action&quot;: { &quot;href&quot;: &quot;/appoi...
  • 3 
                <div class="header-announcement-bar-wrapper"> <style> @supports (-webkit-backdrop-filter: none) or (backdrop-filter: none) { .header-blur-background { } } </style> <div class="header-border" data-header-style="dynamic" data-header-border="false" data...
  • 4 
                <div class="header-inner container--fluid header-mobile-layout-logo-left-nav-right header-layout-nav-right " data-test="header-inner"> <!-- Background --> <div class="header-background theme-bg--primary"></div> <div class="header-display-desktop" dat...
  • 5 
                <div class="header-display-desktop" data-content-field="site-title"> <!-- Social --> <!-- Title and nav wrapper --> <div class="header-title-nav-wrapper"> <!-- Title --> <div class="header-title preSlide slideIn" data-animation-role="header-element" ...
  • 6 
                <div class="header-title-nav-wrapper"> <!-- Title --> <div class="header-title preSlide slideIn" data-animation-role="header-element" style="transition-timing-function: ease; transition-duration: 0.8s; transition-delay: 0s;"> <div class="header-title...
  • 7 
                <div class="header-title preSlide slideIn" data-animation-role="header-element" style="transition-timing-function: ease; transition-duration: 0.8s; transition-delay: 0s;"> <div class="header-title-logo"> <a href="/" data-animation-role="header-elemen...
  • 8 
                <div class="header-title-logo"> <a href="/" data-animation-role="header-element" class="preSlide slideIn" style="transition-timing-function: ease; transition-duration: 0.8s; transition-delay: 0.0122449s;" data-custom-button-processed="true"> <img ele...
  • 9 
                <a href="/" data-animation-role="header-element" class="preSlide slideIn" style="transition-timing-function: ease; transition-duration: 0.8s; transition-delay: 0.0122449s;" data-custom-button-processed="true"> <img elementtiming="nbf-header-logo-desk...
  • 10 
                <img elementtiming="nbf-header-logo-desktop" src="//images.squarespace-cdn.com/content/v1/68eea14c6cb28d11b6d0c1ca/ae453c66-7d44-42bf-a953-e03bbf017492/Belkbot+-+transparent+logo.png?format=1500w" alt="Belkbot Solutions" style="display:block" fetchpr...
#
Element
Relevant
Successes
Failures
Score
3
When elements are visually hidden but still exposed to assistive technology, screen reader users may encounter content that should not be available in the current interface. This can obscure the current state of the page and lead to confusion about what information or controls are available.
Yes
103
0
100

Code snapshots of successful elements

  • 1 
                <div id="floatingCart" class="floating-cart hidden> <a href="/cart" class="icon icon--stroke icon--fill icon--cart sqs-custom-cart sqs-template-integrated-shopping-cart" data-test="continue-to-cart" aria-label="0 items in cart" tabindex="-1" data-cus...
  • 2 
                <a href="/cart" class="icon icon--stroke icon--fill icon--cart sqs-custom-cart sqs-template-integrated-shopping-cart" data-test="continue-to-cart" aria-label="0 items in cart" tabindex="-1" data-custom-button-processed="true"> <span class="Cart-inner...
  • 3 
                <span class="Cart-inner" style="display: block;"> <svg class="icon icon--cart" width="144" height="125" viewBox="0 0 144 125"> <path d="M4.69551 0.000432948C2.10179 0.000432948 0 2.09856 0 4.68769C0 7.27686 2.10183 9.37496 4.69551 9.37496H23.43C31.20...
  • 4 
                <svg class="icon icon--cart" width="144" height="125" viewBox="0 0 144 125"> <path d="M4.69551 0.000432948C2.10179 0.000432948 0 2.09856 0 4.68769C0 7.27686 2.10183 9.37496 4.69551 9.37496H23.43C31.2022 28.5892 38.8567 47.8378 46.5654 67.089L39.4737 ...
  • 5 
                <div class="legacy-cart icon-cart-quantity"> <span class="sqs-cart-quantity" style="display: block;">0</span> </div>
  • 6 
                <span class="sqs-cart-quantity" style="display: block;">0</span>
  • 7 
                <svg style="display:none" viewBox="0 0 22 22" xmlns="http://www.w3.org/2000/svg"> <symbol id="circle"> <path d="M11.5 17C14.5376 17 17 14.5376 17 11.5C17 8.46243 14.5376 6 11.5 6C8.46243 6 6 8.46243 6 11.5C6 14.5376 8.46243 17 11.5 17Z" fill="none"><...
  • 8 
                <div class="sqs-announcement-bar-dropzone"></div>
  • 9 
                <div class="header-actions header-actions--right" aria-hidden="true"> <div class="showOnMobile"> </div> <div class="showOnDesktop"> </div> </div>
  • 10 
                <div class="showOnMobile"> </div>
#
Element
Relevant
Successes
Failures
Score
4
Screen reader users may find it difficult to distinguish between links when the purpose of each link cannot be determined from its text alone or together with its immediate context.
Yes
14
0
100

Code snapshots of successful elements

  • 1 
                <a href="https://accessibe.com/blog/knowledgebase/screen-reader-guide" target="_blank" rel="noopener" tabindex="-1" class="acsb-sr-only" style="position: absolute; width: 200px; height: 1px; margin-top: -1px; z-index: -1; border: 0px; top: 0px; left:...
  • 2 
                <a href="/" data-animation-role="header-element" class="preSlide slideIn" style="transition-timing-function: ease; transition-duration: 0.8s; transition-delay: 0.0122449s;" data-custom-button-processed="true"> <img elementtiming="nbf-header-logo-desk...
  • 3 
                <a href="/services" data-animation-role="header-element" class="preSlide slideIn data-custom-button-processed="true"> Services </a>
  • 4 
                <a href="/case-studies-4AO0p" data-animation-role="header-element" class="preSlide slideIn data-custom-button-processed="true"> Case Studies </a>
  • 5 
                <a href="/about" data-animation-role="header-element" class="preSlide slideIn data-custom-button-processed="true"> About </a>
  • 6 
                <a href="/contact" data-animation-role="header-element" class="preSlide slideIn data-custom-button-processed="true"> Contact </a>
  • 7 
                <a href="/contact" class="sqs-block-button-element--medium sqs-button-element--primary sqs-block-button-element data-initialized="true" style=";background-color:#ffffff!important;color:#000000!important;" data-custom-button-processed="true"> Schedule...
  • 8 
                <a href="/home" class="acsb-contrast" style=";background-color:#ffffff!important;color:#000000!important;" data-custom-button-processed="true">home</a>
  • 9 
                <a href="/services" class="acsb-contrast" style=";background-color:#ffffff!important;color:#000000!important;" data-custom-button-processed="true">services</a>
  • 10 
                <a href="/about" class="acsb-contrast" style=";background-color:#ffffff!important;color:#000000!important;" data-custom-button-processed="true">about</a>
#
Element
Relevant
Successes
Failures
Score
5
Activating navigation links enables users to navigate to a different page within the site. Links that do not contain visible text or labeled images should be assigned labels that inform screen reader users of their destination.
Yes
15
0
100

Code snapshots of successful elements

  • 1 
                <a href="https://accessibe.com/blog/knowledgebase/screen-reader-guide" target="_blank" rel="noopener" tabindex="-1" class="acsb-sr-only" style="position: absolute; width: 200px; height: 1px; margin-top: -1px; z-index: -1; border: 0px; top: 0px; left:...
  • 2 
                <a href="/" data-animation-role="header-element" class="preSlide slideIn" style="transition-timing-function: ease; transition-duration: 0.8s; transition-delay: 0.0122449s;" data-custom-button-processed="true"> <img elementtiming="nbf-header-logo-desk...
  • 3 
                <a href="/services" data-animation-role="header-element" class="preSlide slideIn data-custom-button-processed="true"> Services </a>
  • 4 
                <a href="/case-studies-4AO0p" data-animation-role="header-element" class="preSlide slideIn data-custom-button-processed="true"> Case Studies </a>
  • 5 
                <a href="/about" data-animation-role="header-element" class="preSlide slideIn data-custom-button-processed="true"> About </a>
  • 6 
                <a href="/contact" data-animation-role="header-element" class="preSlide slideIn data-custom-button-processed="true"> Contact </a>
  • 7 
                <a href="/contact" class="sqs-block-button-element--medium sqs-button-element--primary sqs-block-button-element data-initialized="true" style=";background-color:#ffffff!important;color:#000000!important;" data-custom-button-processed="true"> Schedule...
  • 8 
                <a href="/services" class="acsb-contrast" style=";background-color:#ffffff!important;color:#000000!important;" data-custom-button-processed="true" aria-label="View Our Services">View Our Services</a>
  • 9 
                <a href="/home" class="acsb-contrast" style=";background-color:#ffffff!important;color:#000000!important;" data-custom-button-processed="true">home</a>
  • 10 
                <a href="/services" class="acsb-contrast" style=";background-color:#ffffff!important;color:#000000!important;" data-custom-button-processed="true">services</a>
#
Element
Relevant
Successes
Failures
Score
6
Main navigation elements should have role navigation to ensure that screen readers can identify them as navigation regions.
Yes
Pass
-
100

Code snapshots of successful elements

  • 1 
                <div class="header-nav-wrapper" role="navigation" aria-label="Header Menu"> <nav class="header-nav-list" aria-label="Main Menu"> <div class="header-nav-item header-nav-item--collection"> <a href="/services" data-animation-role="header-element" class=...
#
Element
Relevant
Successes
Failures
Score
7
Screen readers rely on accurate tagging and labeling to provide necessary context. If an element that does not contain navigation links is tagged as a navigation landmark, screen reader users may lose orientation and find the page's structure difficult to understand.
Yes
Pass
-
100

Code snapshots of successful elements

  • 1 
                <div class="header-nav-wrapper" role="navigation" aria-label="Header Menu"> <nav class="header-nav-list" aria-label="Main Menu"> <div class="header-nav-item header-nav-item--collection"> <a href="/services" data-animation-role="header-element" class=...
#
Element
Relevant
Successes
Failures
Score
8
The main landmark represents the primary content of a page. It should include only content unique to that page and must remain separate from repeated elements, such as navigation, header, or footer.
Yes
Pass
-
100

Code snapshots of successful elements

  • 1 
                <main id="page" class="container" role="main"> <article class="sections" id="sections" data-page-sections="698b898c2af8bd75feeecb79" role="presentation"> <section data-test="page-section" data-section-theme="black" class="page-section full-bleed-sect...
#
Element
Relevant
Successes
Failures
Score
9
Incorrectly tagging the main landmark may cause screen reader users to misunderstand where the primary content begins or ends, leading to confusion and inefficient navigation.
Yes
Pass
-
100

Code snapshots of successful elements

  • 1 
                <main id="page" class="container" role="main"> <article class="sections" id="sections" data-page-sections="698b898c2af8bd75feeecb79" role="presentation"> <section data-test="page-section" data-section-theme="black" class="page-section full-bleed-sect...
#
Element
Relevant
Successes
Failures
Score
10
Images require a text alternative when the image conveys meaningful content or serves a functional purpose. If the image is decorative, it must be hidden from assistive technology.
Yes
Pass
-
100

Code snapshots of successful elements

  • 1 
                <img elementtiming="nbf-header-logo-desktop" src="//images.squarespace-cdn.com/content/v1/68eea14c6cb28d11b6d0c1ca/ae453c66-7d44-42bf-a953-e03bbf017492/Belkbot+-+transparent+logo.png?format=1500w" alt="Belkbot Solutions" style="display:block" fetchpr...
#
Element
Relevant
Successes
Failures
Score
11
Text alternatives must provide accurate descriptions of the image. Incorrect text alternatives, such as filenames or other placeholder values, may cause screen reader users to either miss essential information or hear unnecessary content that disrupts navigation.
Yes
Pass
-
100

Code snapshots of successful elements

  • 1 
                <img elementtiming="nbf-header-logo-desktop" src="//images.squarespace-cdn.com/content/v1/68eea14c6cb28d11b6d0c1ca/ae453c66-7d44-42bf-a953-e03bbf017492/Belkbot+-+transparent+logo.png?format=1500w" alt="Belkbot Solutions" style="display:block" fetchpr...
#
Element
Relevant
Successes
Failures
Score
12
When non-graphical elements are marked up as images, screen reader users may misunderstand the intended purpose of the content.
Yes
Pass
-
100

Code snapshots of successful elements

  • 1 
                <img elementtiming="nbf-header-logo-desktop" src="//images.squarespace-cdn.com/content/v1/68eea14c6cb28d11b6d0c1ca/ae453c66-7d44-42bf-a953-e03bbf017492/Belkbot+-+transparent+logo.png?format=1500w" alt="Belkbot Solutions" style="display:block" fetchpr...
#
Element
Relevant
Successes
Failures
Score
13
Aria labels should describe elements that don't have proper text, like icons and field labels. It should not be used to override element texts. Screen reader users need to receive the exact text as visually on the screen, with more context if it is ambiguous. An exception applies to landmarks such as nav or other landmarks: here, ARIA labels can provide additional context or clarification.
Yes
Pass
-
100

Code snapshots of successful elements

  • 1 
                <a href="/services" class="acsb-contrast" style=";background-color:#ffffff!important;color:#000000!important;" data-custom-button-processed="true" aria-label="View Our Services">View Our Services</a>
#
Element
Relevant
Successes
Failures
Score
14
An empty list will still be announced by screen readers, which may confuse users, leaving them unsure if the list is empty or an issue prevents the screen reader from announcing the list items.
Yes
Pass
-
100

Code snapshots of successful elements

  • 1 
                <ul class="slides slides--initialized" style=" min-height: 0vh; "><li class=" slide list-item " style="padding: 2%; transform: translate3d(0px, 0px, 0px);" data-is-card-enabled="false"> <div class="slide-content list-item-card-background " style=" wi...
#
Element
Relevant
Successes
Failures
Score
15
Specifying a default page language ensures screen readers apply the correct pronunciation rules, voices, and braille output. Without it, screen readers may guess the language incorrectly, causing mispronunciations, confusion, and reduced comprehension for users.
Yes
Pass
-
100

Code snapshots of successful elements

  • 1 
                <html xmlns:og="http://opengraphprotocol.org/schema/" xmlns:fb="http://www.facebook.com/2008/fbml" lang="en-US" class="yui3-js-enabled wf-aileron-n4-active wf-aileron-n6-active wf-aileron-n7-active js flexbox canvas canvastext webgl no-touch hashchan...
#
Element
Relevant
Successes
Failures
Score
16
The meta viewport should allow scalability, typically with width=device-width, initial-scale=1, so text can be resized up to 200% without loss of functionality. Using user-scalable=no or maximum-scale=1 prevents users from enlarging content, making it difficult for people with low vision to read or interact.
Yes
Pass
-
100

Code snapshots of successful elements

  • 1 
                <meta name="viewport" content="width=device-width, initial-scale=1">
#
Element
Relevant
Successes
Failures
Score
17
A missing page title makes it difficult for screen reader users and sighted users with multiple tabs open to identify the page, reducing orientation and usability.
Yes
Pass
-
100

Code snapshots of successful elements

  • 1 
                <title>Belkbot Solutions | Salesforce Consulting</title>
#
Element
Relevant
Successes
Failures
Score
18
Screen readers rely heavily on page titles to announce the purpose of a page. If titles aren’t descriptive, users with low or no vision may not understand the context until they start navigating the page.
Yes
Pass
-
100

Code snapshots of successful elements

  • 1 
                <title>Belkbot Solutions | Salesforce Consulting</title>
#
Element
Relevant
Successes
Failures
Score
19
Breadcrumb navigation regions are essential for user orientation. If not appropriately tagged, screen reader users will not know that such an option exists on the page and will face more difficulties browsing around.
No
0
0
#
Element
Relevant
Successes
Failures
Score
20
Elements with emphasis importance should have the emphasis role. If not, screen reader users may not understand the emphasis of the text.
No
0
0
#
Element
Relevant
Successes
Failures
Score
21
An iframe needs a label that describes its purpose to screen reader users.
No
0
0
#
Element
Relevant
Successes
Failures
Score
22
Ambiguous links like "Learn More", "Shop Now" and "Start Here" are often used as a call to action. However, screen-reader users, while using link navigation, do not interact with content above or below the link and therefore don't have the same context as to what they will learn more about.
No
0
0
#
Element
Relevant
Successes
Failures
Score
23
Using role="application" is generally discouraged because it disables standard screen reader modes and forces users into an application mode. This removes familiar navigation shortcuts, such as heading or landmark navigation, and requires them to interact in ways they may not expect.
No
0
0
#
Element
Relevant
Successes
Failures
Score
24
Discounted prices often appear next to the original and distinguished with visual cues like strikethroughs or color changes. Both prices must also be conveyed by screen readers in a way that enables users to differentiate between the values, ensuring they can understand when a discount is applied.
No
0
0
#
Element
Relevant
Successes
Failures
Score
25
Elements with strong importance should have the strong role. If not, screen reader users may not understand the importance of the text.
No
0
0
#
Element
Relevant
Successes
Failures
Score
26
Buttons that do not contain visible text should be assigned labels that inform screen reader users of their purpose.
No
0
0
#
Element
Relevant
Successes
Failures
Score
27
If interactive elements cannot be identified as buttons, screen reader users may not realize the element is actionable, which can stop them from submitting forms, opening dialogs, or performing other intended actions.
No
0
0
#
Element
Relevant
Successes
Failures
Score
28
A sticky footer remains anchored to the bottom of the screen while the rest of the page content can be scrolled. If it is not offset from interactive elements, it can overlap and obscure the item in focus.
No
0
0
#
Element
Relevant
Successes
Failures
Score
29
Activating anchor links enables users to navigate to a different section within the same page by scrolling and moving keyboard focus. Anchor links that do not contain visible text or labeled images should be assigned labels that inform screen reader users of their destination.
No
0
0
#
Element
Relevant
Successes
Failures
Score
30
Visual cues are often used by sighted users to indicate which link represents the current page within a set of links. This information should be made available to screen reader users by assigning aria-current='page' to the link.
No
0
0
#
Element
Relevant
Successes
Failures
Score
31
In most cases, using role=menu on navigation elements within a web page can negatively impact screen reader users, especially those using JAWS. The attribute should be used for menu types that function like those found in desktop applications.
No
0
0
#
Element
Relevant
Successes
Failures
Score
32
In most cases, using role=menubar on navigation elements within a web page can negatively impact screen reader users, especially those using JAWS. The attribute should be used for menu types that function like those found in desktop applications.
No
0
0
#
Element
Relevant
Successes
Failures
Score
33
In most cases, using ARIA menu roles within a web page can negatively impact screen reader users, especially those using JAWS. role="menuitem" should be used for menu items in menu types that function like those found in desktop applications.
No
0
0
#
Element
Relevant
Successes
Failures
Score
34
Interactive elements that trigger additional content should only have relationship and state ARIA attributes, such as aria-expanded and aria-controls, if they have interactive roles, such as button, tab, combobox and in rarer cases, link.
No
0
0
#
Element
Relevant
Successes
Failures
Score
35
Make sure that no element has an autofocus attribute.
No
0
0
#
Element
Relevant
Successes
Failures
Score
36
Screen readers rely on properly coded and associated labels to announce the purpose of a form field. A checkbox control without an identifiable label may prevent screen reader users from completing the form.
No
0
0
#
Element
Relevant
Successes
Failures
Score
37
Interacting with form controls shouldn't automatically submit a form or cause any other change in context without notifying the user in advance. Form controls that cause a context change on input can disorient a user, since the behavior is not expected.
No
0
0
#
Element
Relevant
Successes
Failures
Score
38
Adding type="submit" to a control that submits a form ensures that screen readers users expect a change of context when they activate the control.
No
0
0
#
Element
Relevant
Successes
Failures
Score
39
Screen readers rely on properly coded and associated labels to announce the purpose of a form field. A radio control without an identifiable label may prevent screen reader users from completing the form.
No
0
0
#
Element
Relevant
Successes
Failures
Score
40
If a field is marked as required only through visual cues, but lacks the required attribute or aria-required="true", screen readers will not announce it as mandatory. As a result, users may experience unnecessary delays or confusion when trying to submit the form.
No
0
0
#
Element
Relevant
Successes
Failures
Score
41
Using an <article> tag on content that is not self-contained and that cannot stand on its own outside the context of the page, such as a blog post, news story, or forum entry, causes screen readers to announce misleading information about the purpose the content in relation to the main subject of the page.
No
0
0
#
Element
Relevant
Successes
Failures
Score
42
A breadcrumb region presents a trail of links showing the user’s current page in relation to higher-level pages on a site. Without a label, it may be announced by screen reades simply as "navigation", making it hard to distinguish from other navigation regions on the page.
No
0
0
#
Element
Relevant
Successes
Failures
Score
43
A page typically presents one central subject, so a single main landmark establishes the boundaries of the primary content for screen reader users. Multiple main landmarks create uncertainty about the scope, leading to confusion and difficulty navigating the page.
No
0
0
#
Element
Relevant
Successes
Failures
Score
44
Screen reader users rely on landmarks to quickly access important regions of a page. Defining a form as a search landmark ensures that users can quickly recognize and navigate to the search form.
No
0
0
#
Element
Relevant
Successes
Failures
Score
45
Functional images presented using CSS background or background-image properties should be marked up using role="img" so that they can be identified as images by screen reader users.
No
0
0
#
Element
Relevant
Successes
Failures
Score
46
Smaller graphics used as decorative or complementary elements, such as icons, and that do not provide additional information will often add unnecessary clutter to a screen reader user's browsing experience.
No
0
0
#
Element
Relevant
Successes
Failures
Score
47
A sticky header remains anchored to the top of the screen while the rest of the page content can be scrolled. If it is not offset from interactive elements, it can overlap and obscure the item in focus.
No
0
0
#
Element
Relevant
Successes
Failures
Score
48
A <meta> element with http-equiv="refresh" is sometimes used to automatically redirect users after a time delay. These timed changes can interrupt and disorient users who rely on assistive technology
No
0
0
#
Element
Relevant
Successes
Failures
Score
49
A slider should be operable with a single pointer
No
0
0
#
Element
Relevant
Successes
Failures
Score
50
A tablist without role="tablist" is not announced as a group of related tabs, which prevents screen reader users from recognizing the structure and purpose of the component. This makes it harder to navigate between tabs and understand that the controls belong to a single set.
No
0
0
#
Element
Relevant
Successes
Failures
Score
51
Applying role="tablist" to an element without tabs misleads screen reader users by suggesting a group of tabs that does not exist.
No
0
0
#
Element
Relevant
Successes
Failures
Score
52
Custom tabs must be explicitly defined for screen readers since there are no native HTML tab elements. Without assigning role="tab" to the interactive elements, assistive technology will not identify them as tabs, preventing users from understanding their function or navigating them as part of a tab interface.
No
0
0
#
Element
Relevant
Successes
Failures
Score
53
Applying role="tab" to an element that is not part of a functioning tab interface misleads screen reader users by presenting it as a tab without a corresponding panel.
No
0
0
#
Element
Relevant
Successes
Failures
Score
54
The role="tabpanel" identifies an element as the content region of a tab interface. Without this role, panels are exposed only by their native role (such as a generic div or a named section) and screen reader users may not perceive them as part of the tab structure.
No
0
0
#
Element
Relevant
Successes
Failures
Score
55
Applying role="tabpanel" to an element without a corresponding tab misleads screen reader users by announcing it as tab content, even though no controlling tab exists.
No
0
0
#
Element
Relevant
Successes
Failures
Score
56
If a column header is not marked up with the correct role or scope, screen reader users cannot determine which header applies to each cell.
No
0
0
#
Element
Relevant
Successes
Failures
Score
57
If a table header cell is empty, screen reader users may only hear a generic label such as “column 3” or nothing at all. This makes it harder to understand what each column or row represents.
No
0
0
#
Element
Relevant
Successes
Failures
Score
58
When a layout table is marked up with HTML elements like <table> or <tr>, or assigned table ARIA roles, screen readers announce a data table structure with rows, columns, and headers, even though the table is only used for page layout.
No
0
0
#
Element
Relevant
Successes
Failures
Score
59
Nested tables are often misinterpreted by screen readers, making it hard for users to follow the intended structure and meaning of the data.
No
0
0
#
Element
Relevant
Successes
Failures
Score
60
If a table row header is not marked up with the correct role or scope, screen reader users cannot determine which header applies to each cell.
No
0
0
WCAG Best Practices (Not included in score)
#
Element
Relevant
Successes
Failures
Score
1
The contentinfo region, typically represented by the <footer> element, is found at the end of each page and provides screen reader users with information about the website, such as copyright, contact details, legal information, and navigation links.
Yes
Pass
-
100

Code snapshots of successful elements

  • 1 
                <footer class="sections" id="footer-sections" data-footer-sections="" role="contentinfo"> <section data-test="page-section" data-section-theme="black" class="page-section full-bleed-section layout-engine-section background-width--full-bleed section-h...
#
Element
Relevant
Successes
Failures
Score
2
When a region without global site information is tagged as a contentinfo landmark, screen reader users may be misled about its purpose and expect website-level details, such as copyright or contact information.
Yes
Pass
-
100

Code snapshots of successful elements

  • 1 
                <footer class="sections" id="footer-sections" data-footer-sections="" role="contentinfo"> <section data-test="page-section" data-section-theme="black" class="page-section full-bleed-section layout-engine-section background-width--full-bleed section-h...
#
Element
Relevant
Successes
Failures
Score
3
Assigning a valid ISO language value to the <html> lang attribute ensures that screen readers use the correct pronunciation rules, browsers apply proper spell-checking and translation, and search engines index the content in the appropriate language.
Yes
Pass
-
100

Code snapshots of successful elements

  • 1 
                <html xmlns:og="http://opengraphprotocol.org/schema/" xmlns:fb="http://www.facebook.com/2008/fbml" lang="en-US" class="yui3-js-enabled wf-aileron-n4-active wf-aileron-n6-active wf-aileron-n7-active js flexbox canvas canvastext webgl no-touch hashchan...
#
Element
Relevant
Successes
Failures
Score
4
Providing a meta viewport to control layout and scaling on mobile devices
Yes
Pass
-
100

Code snapshots of successful elements

  • 1 
                <meta name="viewport" content="width=device-width, initial-scale=1">
#
Element
Relevant
Successes
Failures
Score
5
If an element’s aria-describedby attribute points to an id that does not exist or is not valid, assistive technologies will not convey the intended description, causing users to miss important context.
No
0
0
#
Element
Relevant
Successes
Failures
Score
6
Since aria-labelledby relies on valid id references, screen readers can only announce the label if the target exists. If the id is missing or invalid, the label will not be conveyed, causing users to miss important context.
No
0
0
#
Element
Relevant
Successes
Failures
Score
7
Figure elements are often incorrectly used to display images on the screen. Incorrectly using the figure tag, without providing a proper figcaption, adds unnecessary clutter to the screen reader user's experience.
No
0
0
#
Element
Relevant
Successes
Failures
Score
8
The title attribute is announced inconsistently across screen readers and browsers, making it unreliable for labeling interactive controls. Because many users may never hear the content, reliance on the attribute risks loss of information. Instead, it should be used to provide extra help text in addition to a valid label.
No
0
0
#
Element
Relevant
Successes
Failures
Score
9
The element’s aria-controls points to an id that does not exist, or is not valid, breaking the link between the controlling element and the content it manages.
No
0
0
#
Element
Relevant
Successes
Failures
Score
10
It's good practice to warn users about the expected behavior when activating a link triggers an image to appear.
No
0
0
#
Element
Relevant
Successes
Failures
Score
11
It's good practice to warn users about the expected behavior when activating a link triggers a mail application.
No
0
0
#
Element
Relevant
Successes
Failures
Score
12
It's good practice to warn users about the expected behavior when activating a link triggers a PDF reader.
No
0
0
#
Element
Relevant
Successes
Failures
Score
13
Each page should normally include only one contentinfo landmark (usually the site footer) to keep landmark navigation simple and predictable. Additional contentinfo landmarks are permitted when clearly justified, but they must each have a unique accessible label.
No
0
0