Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 1 REVIEW 6 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-4vztr4

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://gotowebinar.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://gotowebinar.com/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

4 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 4 <nav> element(s)

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.

Heading Hierarchy

13 headings, 2 skip(s)

REVIEW

13 headings, 2 skip(s)

Single H1 present

Heading level skipped: H1 → H4 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Hassle-free webinar software
H4 Category-leading skipped
H4 Safety & Security
H4 Award-winning
H4 Customer Support
H4 Easy Integration
H4 With Your Tools
H2 Powering over 2.8 million global events for professionals every year.
H4 Launch with confidence skipped
H4 Launch with confidence
H4 GoTo Webinar for Education
H4 GoTo Webinar for Education
H2 Customers love GoTo Webinar

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Landmark Structure

54 landmarks

PASS

54 landmarks

<main> landmark present

4 <nav> landmark(s) found

All <nav> elements are properly labeled

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

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

Alt Text Quality

2 of 34 images have issues

PASS

2 of 34 images have issues

2 image(s) with generic alt text

1 image(s) with alt text over 125 characters

5 decorative image(s) correctly marked

26 image(s) with good alt text

34 images 26 good alt text 5 decorative 2 generic

Issue	Count
generic	2 image(s)
too long	1 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

60 links, 9 buttons — all OK

PASS

60 links, 9 buttons — all OK

11 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://support.goto.com; https://app.goto.com/meeting; https://join.gotoresolve.com/; http://app.goto.com; http://app.goto.com/meetings; https://dashboard.gotowebinar.com; https://global.gototraining.com/; https://myaccount.goto.com/products; https://support.goto.com; https://myaccount.goto.com/products (+1 more)

49 link(s) with descriptive text

60 links

0 empty

0 generic text

11 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://support.goto.com	Support	new tab	Add '(opens in new tab)' to text
https://app.goto.com/meeting	Meeting	new tab	Add '(opens in new tab)' to text
https://join.gotoresolve.com/	Resolve	new tab	Add '(opens in new tab)' to text
http://app.goto.com	GoTo Connect	new tab	Add '(opens in new tab)' to text
http://app.goto.com/meetings	GoTo Meeting	new tab	Add '(opens in new tab)' to text
https://dashboard.gotowebinar.com	GoTo Webinar	new tab	Add '(opens in new tab)' to text
https://global.gototraining.com/	GoTo Training	new tab	Add '(opens in new tab)' to text
https://myaccount.goto.com/products	Sign In	new tab	Add '(opens in new tab)' to text
https://support.goto.com	Support	new tab	Add '(opens in new tab)' to text
https://myaccount.goto.com/products	Sign In	new tab	Add '(opens in new tab)' to text
https://support.goto.com/webinar	Support	new tab	Add '(opens in new tab)' to text

58 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://support.goto.com; https://app.goto.com/meeting; https://join.gotoresolve.com/; http://app.goto.com; http://app.goto.com/meetings; https://dashboard.gotowebinar.com; https://global.gototraining.com/; https://myaccount.goto.com/products; https://support.goto.com; https://myaccount.goto.com/products (+1 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

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)

Element	Ratio	Required	FG	BG	Result
h1 Hassle-free webinar …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Powering over 2.8 mi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Customers love GoTo …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Webinar Software & V…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Contact Us	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Support	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Join	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Meeting	9.07:1	4.5:1	#000000	#89B0C4	Pass
a Webinar	9.48:1	4.5:1	#000000	#8CB4C8	Pass
a Training	9.48:1	4.5:1	#000000	#8CB4C8	Pass
a Resolve	9.61:1	4.5:1	#000000	#8FB5C8	Pass
a join.me	16.47:1	4.5:1	#000000	#D9E6EB	Pass
a Host	16.47:1	4.5:1	#000000	#D9E6EB	Pass
a GoTo Connect	16.47:1	4.5:1	#000000	#D9E6EB	Pass
a GoTo Meeting	16.47:1	4.5:1	#000000	#D9E6EB	Pass
a GoTo Webinar	16.47:1	4.5:1	#000000	#D9E6EB	Pass
a GoTo Training	16.47:1	4.5:1	#000000	#D9E6EB	Pass
a Sign In	16.47:1	4.5:1	#000000	#D9E6EB	Pass
label Products	21.00:1	4.5:1	#000000	#FFFFFF	Pass
label Pricing	21.00:1	4.5:1	#000000	#FFFFFF	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.

Lighthouse Accessibility Audits

Score 93/100 — 3 failing, 31 passed

PASS

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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
AI assistant `body > q-focus-sentinel > div`
After AI assistant `body > q-focus-sentinel > div`
AI assistant, start `div#qualified-multimodal-host > div`
AI assistant, end `div#qualified-multimodal-host > div`

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Category-leading `div.container > ul.!list-none > li#cb16e3c6-23b9-49c5-980e-7d796778465e > h4.header-400`
Launch with confidence `div#content-0 > div.flex > div > h4.header-400`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
logo `nav.mx-[15px] > div.flex > div.cursor-pointer > a.flex-shrink-0`

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.

○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

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

●`[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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements with the `role=text` attribute do not have focusable descendents.

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●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.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

○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

○Form elements have associated labels

○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.

○`[lang]` attributes have a valid value

○`<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.

○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.

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