Site Report

This tab shows accessibility issues, indicating problems for older users, people with disabilities or accessibility needs. Automated testing cannot detect all accessibility issues, so should be used alongside human testing.

Level	WCAG 2.1	Section 508 - 2017	Key
A			Pages with level A issues are unusable for some people
AA			Pages with level AA issues are very difficult to use
AAA			Pages with level AAA issues can be difficult to use

Priority	Description and URL	Guideline and Line#	Count
Level A 10 issues on 8 pages
	`"` in an unquoted attribute value. Probable causes: Attributes running together or a URL query string in an unquoted attribute value.	HTML5 WCAG 2.1 A 4.1.1 Section 508 (2017) A 4.1.1	1 pages

	https://www.cbdessence.net/	Line 929 942
	All `onclick` handlers should have an equivalent `onkeyup` or `onkeydown` handler.	WCAG 2.1 A F54 Section 508 (2017) A F54	1 pages
	Some users are unable to use a mouse, so use the keyboard instead. Add an equivalent keyboard event handler to help these users.
	https://www.cbdessence.net/	Line 566 601 633 668 700 ...
	`alt` text should not be an image file name.	WCAG 2.1 A F30 Section 508 (2017) A F30	2 pages
	Change the `alt` text to a description of the image.
	`alt='product_1'` `alt='product_sm_2'` `alt='product_sm_3'` `alt='product_sm_4'` `alt='product_sm_5'` https://www.cbdessence.net/	Line 570 605 637 672 704
	`alt='DSC_6671'` https://www.cbdessence.net/about-us/	Line 761
	`alt` text should not contain placeholders like 'picture' or 'spacer'.	WCAG 2.1 A F30 Section 508 (2017) A F30	2 pages
	For purely decorative images and spacers use `alt=''`, for images of text use the text, and for other images use a description of the image. Impact on users: JAWS : Reads out placeholder text, instead of a useful image description. NVDA : Reads out placeholder text, instead of a useful image description. VoiceOver : Reads out placeholder text, instead of a useful image description.
	`alt='product_1'` `alt='product_sm_2'` `alt='product_sm_3'` `alt='product_sm_4'` `alt='product_sm_5'` https://www.cbdessence.net/	Line 570 605 637 672 704
	`alt='DSC_6671'` `alt='DSC_6671'` https://www.cbdessence.net/about-us/	Line 759 761
	Content inserted with CSS is not read by some screen readers, and not available to people who turn off style sheets.	WCAG 2.1 A F87 Section 508 (2017) A F87	8 pages
	Move the content from CSS to the HTML page so that all users can see it. Impact on users: NVDA 2019.2 IE11 Windows 10 Reading: Text inserted by CSS content property not read. NVDA 2018.4 IE11 Windows 10 Reading: Text inserted by CSS content property not read. NVDA 2017.3 IE11 Windows 10 Reading: Text inserted by CSS content property not read. NVDA 2016.2 IE11 Windows 10 Reading: Text inserted by CSS content property not read. JAWS 2019.1912.1 IE11 Windows 10 Reading: Text inserted by CSS content property not read. JAWS 2018.1811.2 IE11 Windows 10 Reading: Text inserted by CSS content property not read. JAWS 18.0.5038 IE11 Windows 10 Reading: Text inserted by CSS content property not read. JAWS 17.0.2619 IE11 Windows 10 Reading: Text inserted by CSS content property not read.
	https://www.cbdessence.net/	Line 28
	https://www.cbdessence.net/my-account/	Line 25
	https://www.cbdessence.net/my-account/?action=register	Line 25
	https://www.cbdessence.net/my-account/lost-password/	Line 25
	This issue was found on another 4 pages. The trial version is limited to showing issues on 4 pages.
	Duplicate `id` - the same ID is used on more than one element.	HTML5 WCAG 2.1 A 4.1.1 Section 508 (2017) A 4.1.1	8 pages

	`id=username` `id=username` `id=password` `id=password` `id=woocommerce-login-nonce` https://www.cbdessence.net/	Line 271 278 281 2632 2639 ...
	`id=username` `id=username` `id=password` `id=password` `id=woocommerce-login-nonce` https://www.cbdessence.net/my-account/	Line 303 307 312 499 503 ...
	`id=username` `id=username` `id=password` `id=password` `id=woocommerce-login-nonce` https://www.cbdessence.net/my-account/?action=register	Line 303 307 312 499 503 ...
	`id=username` `id=username` `id=password` `id=password` `id=woocommerce-login-nonce` https://www.cbdessence.net/my-account/lost-password/	Line 303 307 312 831 835 ...
	This issue was found on another 4 pages. The trial version is limited to showing issues on 4 pages.
	Each `a` element must contain text or an `img` with an `alt` attribute.	WCAG 2.1 A F89 Section 508 (2017) A F89	8 pages
	A link name allows screen readers to voice what the links does. If there is no link text or the `alt` text is blank, screen readers have nothing to read, so read out the URL instead. To add a name do one of the following: Add text between the `a` element start and end tags Add an `aria-label` attribute Add an `aria-labelledby` attribute Add an `img alt` attribute if the link contains an `img` element
	https://www.cbdessence.net/	Line 1374 1440 1857
	https://www.cbdessence.net/my-account/	Line 657 944
	https://www.cbdessence.net/my-account/?action=register	Line 657 944
	https://www.cbdessence.net/my-account/lost-password/	Line 574 862
	This issue was found on another 4 pages. The trial version is limited to showing issues on 4 pages.
	Removing the underline from links makes it hard for color-blind users to see them.	WCAG 2.1 A F73 Section 508 (2017) A F73	1 pages
	Remove the `text-decoration:none` property from your link styles, or add other style attributes in addition to color changes to make links visible without color vision.
	https://www.cbdessence.net/	Line 865 915 965 1273 2136 ...
	The visual label must appear in the accessible name of links and controls.	WCAG 2.1 A F96 Section 508 (2017) A F96	1 pages
	People who use speech control rely on being able to select elements using the visual label displayed on screen. If this isn't part of the accessible name, they can't select elements by name.
	Visual label: `Add to cart` not in `Add “CBD Pro LifeStyle All Purpose Lotion 2 oz / 600 mg” to your cart` https://www.cbdessence.net/	Line 1011
	Use semantic markup like `strong` instead of using the CSS `font-weight` property.	WCAG 2.1 A F2 Section 508 (2017) A F2	1 pages
	Use the `strong` element instead of the `span` element for bold text.
	https://www.cbdessence.net/	Line 1317 1386 1452 1519 2142 ...
Level AA 6 issues on 8 pages
	Do not use the `meta viewport` tag to disable zoom.	WCAG 2.1 AA 1.4.4 Section 508 (2017) AA 1.4.4	8 pages
	Setting `user-scalable=no` or `maximum-scale` to less than 2.0 prevents zooming small text to make it readable. Note that iOS 10+ ignores this setting.
	https://www.cbdessence.net/	Line 5
	https://www.cbdessence.net/my-account/	Line 5
	https://www.cbdessence.net/my-account/?action=register	Line 5
	https://www.cbdessence.net/my-account/lost-password/	Line 5
	This issue was found on another 4 pages. The trial version is limited to showing issues on 4 pages.
	Ensure that text and background colors have enough contrast.	WCAG 2.1 AA 1.4.3 Section 508 (2017) AA 1.4.3	1 pages
	Some users find it hard to read light gray text on a white background, dark gray text on a black background and white text on a red background. The contrast ratio should be 3.0 or more for 18 point text, or larger The contrast ratio should be 3.0 or more for 14 point bold text, or larger The contrast ratio should be 4.5 or more for all other text
	The text color to background color contrast ratio is: 4.48 with `color: rgb(119,119,119);background-color: rgb(255,255,255);font-size: 10.50pt;font-weight: 400;` 4.48 with `color: rgb(119,119,119);background-color: rgb(255,255,255);font-size: 8.75pt;font-weight: 400;` 4.25 with `color: rgb(119,119,119);background-color: rgb(249,249,249);font-size: 10.50pt;font-weight: 400;` 4.25 with `color: rgb(119,119,119);background-color: rgb(249,249,249);font-size: 10.50pt;font-weight: 400;` 4.29 with `color: rgb(119,119,119);background-color: rgb(250,250,250);font-size: 10.50pt;font-weight: 400;` https://www.cbdessence.net/	Line 137 1111 1894 1899 1926 ...
	Form field labels should be unique on a page, or be close to text providing context.	WCAG 2.1 AA 2.4.6 Section 508 (2017) AA 2.4.6	7 pages
	Form fields with the same label need extra context (such as a heading) to explain the differences between the fields.
	Label used: `Username or email Username or email` `Username or email Username or email` `Remember me` `Remember me` `Log in` https://www.cbdessence.net/cart/	Line 299 308 314 861 876 ...
	Label used: `Username or email Username or email Username or email ` `Username or email Username or email Username or email ` `Username or email Username or email Username or email *` `Remember me` `Remember me` https://www.cbdessence.net/my-account/	Line 303 318 499 514 913 ...
	Label used: `Username or email Username or email Username or email ` `Username or email Username or email Username or email ` `Username or email Username or email Username or email *` `Remember me` `Remember me` https://www.cbdessence.net/my-account/?action=register	Line 303 318 499 514 913 ...
	Label used: `Username or email Username or email` `Username or email Username or email` `Remember me` `Remember me` `Log in` https://www.cbdessence.net/my-account/lost-password/	Line 303 312 318 831 846 ...
	This issue was found on another 3 pages. The trial version is limited to showing issues on 4 pages.
	The CSS outline or border style on this element makes it difficult or impossible to see the dotted link focus outline.	WCAG 2.1 AA F78 Section 508 (2017) AA F78	4 pages
	Change the style to avoid obscuring the focus outline around focusable elements. Using a border or outline style that obscures the focus ring causes problems for keyboard-only users in: Chrome (obscures the focus indicator on links, buttons, dropdowns and range controls) Firefox (obscures the focus indicator on links) Internet Explorer (obscures the focus indicator on links, buttons and range controls) Internet Explorer does not support the `outline-offset:` property, so using this does not reliably avoid focus outline overlap.
	https://www.cbdessence.net/	Line 37 817 861 911 960 ...
	https://www.cbdessence.net/about-us/	Line 36
	https://www.cbdessence.net/best-cbd-reviews/	Line 36
	https://www.cbdessence.net/how-sezzle-works/	Line 36
	Use relative units in CSS property values when zoom is disabled by meta viewport.	WCAG 2.1 AA 1.4.4 Section 508 (2017) AA 1.4.4	8 pages
	Either allow the user to zoom content using pinch-zoom by removing `user-scalable=no` from the meta viewport tag (easiest), or allow the user to increase text size by using relative units like `em` and not absolute units like `px` and `pt`
	https://www.cbdessence.net/	Line 37 81 149 153
	https://www.cbdessence.net/my-account/	Line 70 188 193 233 245 ...
	https://www.cbdessence.net/my-account/?action=register	Line 70 188 193 233 245 ...
	https://www.cbdessence.net/my-account/lost-password/	Line 70 188 193 233 245 ...
	This issue was found on another 4 pages. The trial version is limited to showing issues on 4 pages.
	User interface controls must have a contrast ratio of at least 3:1 against adjacent colors.	WCAG 2.1 1.4.11	1 pages
	If the control has a visible edge, make sure this has sufficient contrast against the area outside the control.
	The contrast ratio between the control edge and surrounding area is: 1.26 1.26 https://www.cbdessence.net/	Line 2124 2128
	Expand all 16 issues

Site Report

Level A

Level AA