Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 5 REVIEW 6 FIX

Landmark Structure

Action

1 landmarks

FIX

1 landmarks

No <main> landmark found

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

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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

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

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #ffffff

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 ModePartial Dark Mode

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 ✗

Lighthouse Accessibility Audits

Action

Score 69/100 — 7 failing, 17 passed

FIX

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.

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
Private tickets are just between you and your customers, but Public tickets are… `ul.cf > li > div.content > p`
(public tickets are optional) `li > div.content > p > small`
Connect your Envato Market account to provide your customers with a one-click s… `ul.cf > li > div.content > p`
Envato Market `div.content > p > strong > a`
one-click solution `li > div.content > p > em`
Easy Digital Downloads `div.content > p > strong > a`
Themely Marketplace `div.content > p > strong > a`
Freemius `div.content > p > strong > a`
Create an unlimited number of articles and assigned them to one or more categor… `ul.cf > li > div.content > p`
Branding is important, which is why with Ticksy you can choose a custom subdoma… `ul.cf > li > div.content > p`
Stay in the loop. Email notifications are sent out for each new ticket & reply.… `ul.cf > li > div.content > p`
(you can enable and disable specific notifications) `li > div.content > p > small`
Speed is extremely important when it comes to support, which is why Ticksy boas… `ul.cf > li > div.content > p`
You can display your system in several different languages. Your support agents… `ul.cf > li > div.content > p`
English (US & UK), Spanish, French, Italian, Norwegian, Estonian, Dutch, & Chin… `li > div.content > p > small`
Every comment can be "liked" by both the support agents and your customers, pro… `ul.cf > li > div.content > p`
You can define a list of email addresses that your customers can use in order t… `ul.cf > li > div.content > p`
this article `li > div.content > p > a`
If you'd like to ask your customers for multiple details when they submit a tic… `ul.cf > li > div.content > p`
Help your customers at the office or at home, at the airport with your tablet, … `div#content > div#desk > div.shell > p`
GET STARTED `div.shell > div > a.get-started > span`
Support: https://support.ticksy.com `li > div.content > p > small`
https://support.ticksy.com `div.content > p > small > a`
Phone Number: +1-208-481-8061 `li > div.content > p > small`
Got It! `div.moove-gdpr-info-bar-container > div.moove-gdpr-info-bar-content > div.moove-gdpr-button-holder > button.mgbutton`

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
li > div.content > p > img.ticksy-emoticon `li > div.content > p > img.ticksy-emoticon`
div.shell > ul.cf > li > img `div.shell > ul.cf > li > img`
div.shell > ul.cf > li > img `div.shell > ul.cf > li > img`

The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.no-js `html.no-js`

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.features-row > ul.cf > li > iframe `div.features-row > ul.cf > li > iframe`

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
div#header > div.shell > h1#logo > a `div#header > div.shell > h1#logo > a`

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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.no-js `html.no-js`

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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●All heading elements contain content.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○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

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

○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

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

○No element has a `[tabindex]` value greater than 0

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

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

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

Alt Text Quality

Action

4 of 5 images have issues

REVIEW

4 of 5 images have issues

4 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image(s) with good alt text

5 images 1 good alt text 4 missing

Issue	Count
missing	4 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

Link & Button Quality

1 issue(s) across 21 links and 9 buttons

REVIEW

1 issue(s) across 21 links and 9 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://ticksy.com

10 link(s) open in new tab without warning

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

Got: http://support.ticksy.com/; http://market.envato.com/; https://easydigitaldownloads.com/; https://marketplace.themely.com; https://freemius.com/; https://ticksy.com/updates/new-feature-email-piping; https://cr3ativ.com; http://www.themepunch.com; https://ticksy.com/privacy-policy/; https://wordpress.org/plugins/gdpr-cookie-compliance/

10 link(s) with descriptive text

21 links

1 empty

0 generic text

10 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://ticksy.com	(empty)	empty	Add link text or aria-label
http://support.ticksy.com/	Need Help?	new tab	Add '(opens in new tab)' to text
http://market.envato.com/	Envato Market	new tab	Add '(opens in new tab)' to text
https://easydigitaldownloads.com/	Easy Digital Downloads	new tab	Add '(opens in new tab)' to text
https://marketplace.themely.com	Themely Marketplace	new tab	Add '(opens in new tab)' to text
https://freemius.com/	Freemius	new tab	Add '(opens in new tab)' to text
https://ticksy.com/updates/new-feature-e…	this article	new tab	Add '(opens in new tab)' to text
https://cr3ativ.com	Visit Cr3ativ.com	new tab	Add '(opens in new tab)' to text
http://www.themepunch.com	Visit ThemePunch.com	new tab	Add '(opens in new tab)' to text
https://ticksy.com/privacy-policy/	Cookie Policy	new tab	Add '(opens in new tab)' to text
https://wordpress.org/plugins/gdpr-cooki…	Powered by GDPR Cookie Compl…	new tab	Add '(opens in new tab)' to text

19 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://ticksy.com

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

http://support.ticksy.com/; http://market.envato.com/; https://easydigitaldownloads.com/; https://marketplace.themely.com; https://freemius.com/; https://ticksy.com/updates/new-feature-email-piping; https://cr3ativ.com; http://www.themepunch.com; https://ticksy.com/privacy-policy/; https://wordpress.org/plugins/gdpr-cookie-compliance/

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

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

Favicon & Branding

16 icon(s) detected

REVIEW

16 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 4 fail WCAG AA

REVIEW

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

16 pass 4 fail WCAG AA

h1 Help desks for

2.63:1

#000000

#0C5B51

needs 3.0:1 (large text)

32px · above the fold

h2 Loaded.

2.63:1

#000000

#0C5B51

needs 3.0:1 (large text)

24px · above the fold

a Pricing & Signup

2.63:1

#000000

#0C5B51

needs 4.5:1 (normal text)

16px · top of page (header area)

a Contact

2.63:1

#000000

#0C5B51

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Help desks for	2.63:1	3.0:1	#000000	#0C5B51	Fail
h2 Loaded.	2.63:1	3.0:1	#000000	#0C5B51	Fail
h2 Ticksy works where	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 work.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Private & Public Tic…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Envato & Other Integ…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Knowledgebase	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Company Branded	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Live & Email Notific…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Time-Saving Features	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Multilingual	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Social & Interactive	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Email Piping	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Custom fields	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 TICKSY	21.00:1	3.0:1	#000000	#FFFFFF	Pass
a Account	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Updates	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Need Help?	10.41:1	4.5:1	#000000	#9DBDB9	Pass
a Pricing & Signup	2.63:1	4.5:1	#000000	#0C5B51	Fail
a Contact	2.63:1	4.5:1	#000000	#0C5B51	Fail

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.

Heading Hierarchy

15 headings

PASS

15 headings

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 (empty)
H1 Help desks for happy customers.,Envato authors.,freelancers.,business owners.,educators. duplicate H1
H2 Loaded. Not bloated.
H3 Private & Public Tickets
H3 Envato & Other Integrations
H3 Knowledgebase
H3 Company Branded
H3 Live & Email Notifications
H3 Time-Saving Features
H3 Multilingual
H3 Social & Interactive
H3 Email Piping
H3 Custom fields
H2 Ticksy works where you work.
H3 TICKSY

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#moove_gdpr_strict_cookies	checkbox	Enable or Disable Cookies	none
#moove_gdpr_performance_cookies	checkbox	Enable or Disable Cookies	none

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