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 9 issues on 8 pages
	All `fieldset` elements should be labeled with `legend` elements.	WCAG 2.1 A H71 Section 508 (2017) A H71	8 pages
	The first child element inside a `fieldset` must be a `legend` element, which provides a label or description for the group. `legend` elements in other positions may be ignored.
	https://loginspage.com/	Line 607
	https://loginspage.com/login/	Line 1094
	https://loginspage.com/login-page/	Line 1094
	https://loginspage.com/student-portal/	Line 539
	This issue was found on another 4 pages. The trial version is limited to showing issues on 4 pages.
	An element with `role=menuitem` must be contained in, or owned by, an element with `role=menu` or `role=menubar`	HTML5 WCAG 2.1 A 4.1.1 Section 508 (2017) A 4.1.1	2 pages

	https://loginspage.com/chymall-sairui-account-login-guide/	Line 661 683 705
	https://loginspage.com/my-cra-account-login-portal/	Line 721 743 765
	Bad value for attribute `role`.	HTML5 WCAG 2.1 A 4.1.2 Section 508 (2017) A 4.1.2	2 pages
	The `role` attribute changes how screen readers voice content. Invalid values can result in content being misread.
	This ARIA role is not allowed on this element. `role=menuitem` `role=menuitem` `role=menuitem` https://loginspage.com/chymall-sairui-account-login-guide/	Line 661 683 705
	This ARIA role is not allowed on this element. `role=menuitem` `role=menuitem` `role=menuitem` https://loginspage.com/my-cra-account-login-portal/	Line 721 743 765
	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	2 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://loginspage.com/chymall-sairui-account-login-guide/	Line 107
	https://loginspage.com/my-cra-account-login-portal/	Line 107
	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=featured-thumbnail` `id=featured-thumbnail` `id=featured-thumbnail` `id=featured-thumbnail` `id=featured-thumbnail` https://loginspage.com/	Line 334 334 334 410 486 ...
	`id=featured-thumbnail` `id=featured-thumbnail` `id=featured-thumbnail` `id=featured-thumbnail` `id=featured-thumbnail` https://loginspage.com/login/	Line 338 338 338 415 492 ...
	`id=featured-thumbnail` `id=featured-thumbnail` `id=featured-thumbnail` `id=featured-thumbnail` `id=featured-thumbnail` https://loginspage.com/login-page/	Line 338 338 338 415 492 ...
	`id=featured-thumbnail` `id=featured-thumbnail` `id=featured-thumbnail` `id=featured-thumbnail` https://loginspage.com/student-portal/	Line 338 338 417 498
	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://loginspage.com/	Line 102 105 108
	https://loginspage.com/login/	Line 170 177 184
	https://loginspage.com/login-page/	Line 170 177 184
	https://loginspage.com/student-portal/	Line 166 173 180
	This issue was found on another 4 pages. The trial version is limited to showing issues on 4 pages.
	HTML form control has no accessible name.	WCAG 2.1 A F68 Section 508 (2017) A F68	2 pages
	A label (or name) linked to the control allows screen readers to voice the label correctly when reading the control. To add a label do one of the following: Use a `label` element with the `for` attribute set to the ID of the form control Wrap a `label` element around the form control Add a `title` attribute Add an `aria-label` attribute Add an `aria-labelledby` attribute
	https://loginspage.com/chymall-sairui-account-login-guide/	Line 979
	https://loginspage.com/my-cra-account-login-portal/	Line 1047
	Several links on a page share the same link text and surrounding context, but go to different destinations.	WCAG 2.1 A F63 Section 508 (2017) A F63	4 pages
	Make the link text unique for each target page (which helps all users) or add an `aria-label` or `aria-describedby` to the link (which helps screen reader users).
	Link text: `No Comments` `No Comments` https://loginspage.com/	Line 175 446
	Link text: `No Comments` `No Comments` https://loginspage.com/author/loginspage/	Line 333 718
	Link text: `No Comments` `No Comments` https://loginspage.com/login/	Line 329 793
	Link text: `No Comments` `No Comments` https://loginspage.com/login-page/	Line 329 793
	The visual label must appear in the accessible name of links and controls.	WCAG 2.1 A F96 Section 508 (2017) A F96	8 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: `[Continue Reading...]` not in `MY CRA Account Login Guide – Steps To Sign Into Canada Revenue Agency Account` `[Continue Reading...]` not in `Steps To Log In To Your ATB Personal Account – Follow This ATB Login Guide` `[Continue Reading...]` not in `ATB Prosper Account Login Guide – Steps To Sign-In To Your ATB Prosper Login Portal` `[Continue Reading...]` not in `Home Bargains Login Guide – Steps To Sign-In To Home Bargains UK Account` `[Continue Reading...]` not in `India Post Agent Login Guide – Steps Sign-In To India Post Online Portal As Agent` https://loginspage.com/	Line 207 250 293 335 378 ...
	Visual label: `Logins Page` not in `Steps To Login To Your Account` `[Continue Reading...]` not in `MY CRA Account Login Guide – Steps To Sign Into Canada Revenue Agency Account` `[Continue Reading...]` not in `Steps To Log In To Your ATB Personal Account – Follow This ATB Login Guide` `[Continue Reading...]` not in `ATB Prosper Account Login Guide – Steps To Sign-In To Your ATB Prosper Login Portal` `[Continue Reading...]` not in `Home Bargains Login Guide – Steps To Sign-In To Home Bargains UK Account` https://loginspage.com/login/	Line 358 435 512 589 1274 ...
	Visual label: `Logins Page` not in `Steps To Login To Your Account` `[Continue Reading...]` not in `MY CRA Account Login Guide – Steps To Sign Into Canada Revenue Agency Account` `[Continue Reading...]` not in `Steps To Log In To Your ATB Personal Account – Follow This ATB Login Guide` `[Continue Reading...]` not in `ATB Prosper Account Login Guide – Steps To Sign-In To Your ATB Prosper Login Portal` `[Continue Reading...]` not in `Home Bargains Login Guide – Steps To Sign-In To Home Bargains UK Account` https://loginspage.com/login-page/	Line 358 435 512 589 1274 ...
	Visual label: `Logins Page` not in `Steps To Login To Your Account` `[Continue Reading...]` not in `UEW Student Portal Login Guide – How to Sign-In To UEW (OSIS Student Information Portal)` `[Continue Reading...]` not in `MyCCP Login Guide – How To Sign-In To MyCCP Portal Online` `[Continue Reading...]` not in `UCC Student Login Portal – Sign-In To University Of Cape Coast Student Account` https://loginspage.com/student-portal/	Line 358 437 518 719
	This issue was found on another 4 pages. The trial version is limited to showing issues on 4 pages.
Level AA 2 issues on 8 pages
	Ensure that text and background colors have enough contrast.	WCAG 2.1 AA 1.4.3 Section 508 (2017) AA 1.4.3	8 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: 2.32 with `color: rgb(170,170,170);background-color: rgb(255,255,255);font-size: 12pt;font-weight: 500;` 4.10 with `color: rgb(126,125,125);background-color: rgb(255,255,255);font-size: 10.50pt;font-weight: 500;` 4.10 with `color: rgb(126,125,125);background-color: rgb(255,255,255);font-size: 10.50pt;font-weight: 500;` 4.48 with `color: rgb(119,119,119);background-color: rgb(255,255,255);font-size: 9.75pt;font-weight: 500;` 4.48 with `color: rgb(119,119,119);background-color: rgb(255,255,255);font-size: 9.75pt;font-weight: 500;` https://loginspage.com/	Line 86 89 168 691 694 ...
	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: 9.75pt;font-weight: 500;` 4.48 with `color: rgb(119,119,119);background-color: rgb(255,255,255);font-size: 9.75pt;font-weight: 500;` 4.48 with `color: rgb(119,119,119);background-color: rgb(255,255,255);font-size: 9.75pt;font-weight: 500;` 4.48 with `color: rgb(119,119,119);background-color: rgb(255,255,255);font-size: 9.75pt;font-weight: 500;` 4.48 with `color: rgb(119,119,119);background-color: rgb(255,255,255);font-size: 9.75pt;font-weight: 500;` https://loginspage.com/login/	Line 143 148 153 158 163 ...
	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: 9.75pt;font-weight: 500;` 4.48 with `color: rgb(119,119,119);background-color: rgb(255,255,255);font-size: 9.75pt;font-weight: 500;` 4.48 with `color: rgb(119,119,119);background-color: rgb(255,255,255);font-size: 9.75pt;font-weight: 500;` 4.48 with `color: rgb(119,119,119);background-color: rgb(255,255,255);font-size: 9.75pt;font-weight: 500;` 4.48 with `color: rgb(119,119,119);background-color: rgb(255,255,255);font-size: 9.75pt;font-weight: 500;` https://loginspage.com/login-page/	Line 143 148 153 158 163 ...
	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: 9.75pt;font-weight: 500;` 4.48 with `color: rgb(119,119,119);background-color: rgb(255,255,255);font-size: 9.75pt;font-weight: 500;` 4.48 with `color: rgb(119,119,119);background-color: rgb(255,255,255);font-size: 9.75pt;font-weight: 500;` 4.48 with `color: rgb(119,119,119);background-color: rgb(255,255,255);font-size: 9.75pt;font-weight: 500;` 4.48 with `color: rgb(119,119,119);background-color: rgb(255,255,255);font-size: 9.75pt;font-weight: 500;` https://loginspage.com/student-portal/	Line 139 144 149 154 159 ...
	This issue was found on another 4 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	8 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://loginspage.com/	Line 51
	https://loginspage.com/login/	Line 88
	https://loginspage.com/login-page/	Line 88
	https://loginspage.com/student-portal/	Line 88
	This issue was found on another 4 pages. The trial version is limited to showing issues on 4 pages.
	Expand all 11 issues

Site Report

Level A

Level AA