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 17 issues on 33 pages
	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.diligent.com/news	Line 593
	Clickable controls should be keyboard accessible.	WCAG 2.1 A F15 Section 508 (2017) A F15	3 pages
	Add `tabindex=0` to allow keyboard users to tab to the control.
	https://www.diligent.com/company/about-us	Line 1726
	https://www.diligent.com/solutions/modern-audit	Line 1361
	https://www.diligent.com/solutions/modern-risk	Line 1474
	Clickable controls should have an ARIA role.	WCAG 2.1 A F54 Section 508 (2017) A F54	3 pages
	Controls that respond to clicks should be given an ARIA role such as `role=button` or `role=link`.
	https://www.diligent.com/company/about-us	Line 1726
	https://www.diligent.com/solutions/modern-audit	Line 1361
	https://www.diligent.com/solutions/modern-risk	Line 1474
	Decorative and spacer images must have a null `alt` attribute.	WCAG 2.1 A F38 Section 508 (2017) A F38	1 pages
	Images used for decoration only should have `alt=''` or `role=presentation` so they can be ignored by screen readers. Impact on users: JAWS : Reads out redundant `alt` text. NVDA : Reads out redundant `alt` text. VoiceOver : Reads out redundant `alt` text.
	https://www.diligent.com/404Page	Line 1677
	Don't use CSS animations that run for more than 5 seconds without giving the user a way to turn them off.	WCAG 2.1 A 2.2.2 Section 508 (2017) A 2.2.2	2 pages
	Reduce the duration of the animation to less than 5 seconds (works on all devices) or use the @media (prefers-reduced-motion) media query to turn them off (works in Chrome, Firefox and Safari).
	`animation-duration: 6000ms` https://www.diligent.com/industries/industries/higher-education	Line 968
	`animation-duration: 6000ms` https://www.diligent.com/industries/industries/non-profit	Line 988
	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	2 pages

	`id=demo-link` `id=demo-link` https://www.diligent.com/news	Line 695 1926
	`id=content` `id=content` https://www.diligent.com/support	Line 943 957
	Each `a` element must contain text or an `img` with an `alt` attribute.	WCAG 2.1 A F89 Section 508 (2017) A F89	2 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.diligent.com/news	Line 1107 1343 1434 1495 1581 ...
	https://www.diligent.com/support	Line 1050
	Identify row and column headers in data tables using `th` elements, and mark layout tables with `role=presentation`.	WCAG 2.1 A F91 Section 508 (2017) A F91	2 pages
	Data tables allow screen reader users to understand column and row relationships. Layout tables read cells as a series of unrelated paragraphs with no tabular structure. Without `th` or `role`, screen readers apply heuristics to decide whether a table is a layout table or data table. These heuristics vary greatly between screen readers, and are affected by browser being used, window size, and font size (so the outcome is very unpredictable without `th` or `role`). If a data table has headers marked up using `td`, then change these to `th`. If a data table has no headers, add `th` elements describing each row and/or column. If the table is only used for layout add `role=presentation` to the `table` element. Impact on users: JAWS Reading: Treats tables without `th` and `role` as layout tables if the table contains cells above or below certain pixel sizes. This measurement is affected by browser window size, browser font size, and the browser used. NVDA Reading: Applies a layout table heuristic to tables without `th` and `role` which varies depending on the browser used and on the window size in some circumstances. VoiceOver Reading: Uses a sophisticated heuristic on tables without `th` and `role`, which is similar (but not identical) to the heuristic used by NVDA with Firefox.
	https://www.diligent.com/industries/industries/higher-education	Line 1015 1165
	https://www.diligent.com/industries/industries/non-profit	Line 1035 1200
	`img` elements must have an accessible name.	WCAG 2.1 A F65 Section 508 (2017) A F65	1 pages
	Add an `alt` attribute describing the image, which screen readers voice instead of the image. Spacer images and purely decorative images should use `alt=""`. Do not use `alt` text containing only spaces since that's voiced as an unlabeled image. Impact on users: NVDA 2019.2 Chrome 79 Windows 10 Reading: Image unlabeled. NVDA 2019.2 FF68 Windows 10 Reading: Image ignored. NVDA 2019.2 IE11 Windows 10 Reading: Image ignored. NVDA 2018.4 Chrome 73 Windows 10 Reading: Image ignored. NVDA 2018.4 FF60 Windows 10 Reading: Image ignored. NVDA 2018.4 IE11 Windows 10 Reading: Image ignored. JAWS 2019.1912.1 Chrome 79 Windows 10 Reading: Image unlabeled. JAWS 2019.1912.1 FF68 Windows 10 Reading: Image ignored. JAWS 2019.1912.1 IE11 Windows 10 Reading: Image ignored. JAWS 2018.1811.2 Chrome 73 Windows 10 Reading: Image ignored. JAWS 2018.1811.2 FF60 Windows 10 Reading: Image ignored. JAWS 2018.1811.2 IE11 Windows 10 Reading: Image ignored. VoiceOver macOS 10.14 Safari 13.0 macOS 10.14.6 Reading: Image filename read out. VoiceOver macOS 10.13 Safari 12.1 macOS 10.13.6 Reading: Image filename read out. VoiceOver macOS 10.12 Safari 10.1.2 macOS 10.12.6 Reading: Image filename read out. VoiceOver iOS 12.4 Safari iOS 12.4 iOS 12.4.1 Touch: Image filename read out. VoiceOver iOS 11.4 Safari iOS 11.4 iOS 11.4.1 Touch: Image filename read out. VoiceOver iOS 10.3 Safari iOS 10.3 iOS 10.3 Touch: Image filename read out.
	https://www.diligent.com/news	Line 1109 1344 1435 1496 1582 ...
	Link uses general text like 'Click Here' with no surrounding text explaining link purpose.	WCAG 2.1 A F63 Section 508 (2017) A F63	28 pages
	Screen reader users use text around links to help understand what the link does. If the link text is very general, and there's no surrounding text, there's no way to work out what the link does. Either use a descriptive link label (which helps all users) or add an `aria-label` or `aria-describedby` to the link (which helps screen reader users).
	Link text: `READ MORE` `DOWNLOAD` `DOWNLOAD` https://www.diligent.com/	Line 1765 1827 1856
	Link text: `READ MORE` https://www.diligent.com/solutions/modern-governance	Line 1756
	Link text: `Learn More` `READ MORE` `READ MORE` `READ MORE` `READ MORE` https://www.diligent.com/solutions/modern-governance/board-and-leadership-collaboration	Line 1623 1682 1711 1737 1766 ...
	Link text: `Learn More` `READ MORE` `READ MORE` `READ MORE` `READ MORE` https://www.diligent.com/solutions/modern-governance/entity-and-subsidiary-management	Line 1587 1649 1678 1709 1740 ...
	This issue was found on another 24 pages. The trial version is limited to showing issues on 4 pages.
	`object` elements must have an accessible name.	WCAG 2.1 A 1.1.1 Section 508 (2017) A 1.1.1	1 pages
	Add an accessible name using `aria-label` or `aria-labelledby` attributes.
	https://www.diligent.com/solutions/modern-governance/compensation-and-governance-intel	Line 1725
	`object` elements should contain fallback content.	WCAG 2.1 A 1.1.1 Section 508 (2017) A 1.1.1	1 pages
	Place fallback content inside the `object` element, which is displayed when objects are disabled or unsupported (e.g. when Flash and plugins are displayed on mobile devices). For example: `<object>Alternative text content</object>`
	https://www.diligent.com/solutions/modern-governance/compensation-and-governance-intel	Line 1725
	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	24 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: `LEARN MORE` `LEARN MORE` https://www.diligent.com/solutions/modern-governance	Line 1527 1552
	Link text: `LEARN MORE` `LEARN MORE` https://www.diligent.com/solutions/modern-governance/board-and-leadership-collaboration	Line 1546 1571
	Link text: `LEARN MORE` `LEARN MORE` `LEARN MORE` `LEARN MORE` https://www.diligent.com/solutions/modern-governance/compensation-and-governance-intel	Line 1540 1565 1590 1615
	Link text: `LEARN MORE` `LEARN MORE` https://www.diligent.com/solutions/modern-governance/entity-and-subsidiary-management	Line 1537 1562
	This issue was found on another 20 pages. The trial version is limited to showing issues on 4 pages.
	The element `button` must not appear as a descendant of the `a` element.	HTML5 WCAG 2.1 A 4.1.1 Section 508 (2017) A 4.1.1	1 pages

	https://www.diligent.com/news	Line 697 1928
	The element `main` must not appear as a descendant of the `main` element.	HTML5 WCAG 2.1 A 4.1.1 Section 508 (2017) A 4.1.1	1 pages

	https://www.diligent.com/support	Line 958
	The element `main` must not appear as a descendant of the `section` element.	HTML5 WCAG 2.1 A 4.1.1 Section 508 (2017) A 4.1.1	2 pages

	https://www.diligent.com/news	Line 1944
	https://www.diligent.com/support	Line 958
	The interactive element `button` must not appear as a descendant of the `a` element.	HTML5 WCAG 2.1 A 4.1.1 Section 508 (2017) A 4.1.1	1 pages

	https://www.diligent.com/news	Line 697 1928
Level AA 2 issues on 52 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	52 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.diligent.com/	Line 300
	https://www.diligent.com/404Page	Line 455
	https://www.diligent.com/solutions	Line 296
	https://www.diligent.com/solutions/modern-governance	Line 318
	This issue was found on another 48 pages. The trial version is limited to showing issues on 4 pages.
	Headings should not be empty.	WCAG 2.1 AA G130 Section 508 (2017) AA G130	3 pages
	Add text to the heading, or `alt` text if the heading contains an image. Screen readers read out page headings, allowing users to quickly skip to a section, but some older screen readers do not ignore empty headings.
	https://www.diligent.com/ccpa	Line 916
	https://www.diligent.com/company/about-us	Line 1043 1102 1161
	https://www.diligent.com/support	Line 994
Level AAA 3 issues on 53 pages
	Avoid specifying a new window as the target of a link with `target=_blank`.	WCAG 2.1 AAA F22	53 pages
	Displaying new windows without warning can be very confusing to non-sighted and mobile users. Some screen readers and mobile devices give very little indication a new tab or window has opened. If you cannot avoid displaying a new window, insert a warning into the link text like the following: "opens in a new window".
	https://www.diligent.com/	Line 859 2095 2103 2111 2119 ...
	https://www.diligent.com/404Page	Line 1414 1503 1515 1527 1539 ...
	https://www.diligent.com/solutions	Line 855 1145 1153 1161 1169 ...
	https://www.diligent.com/solutions/modern-governance	Line 877 973 2020 2028 2036 ...
	This issue was found on another 49 pages. The trial version is limited to showing issues on 4 pages.
	Link uses general text like 'Click Here' which doesn't explain link purpose.	WCAG 2.1 AAA F84	28 pages
	Screen reader users often tab from one link to the next, or use the 'Next Link' command. Moving between links labelled 'click here' sounds like 'Click here, tab, click here, tab, click here'. Change the link text, or add an `aria-label`, so the link makes sense when read without the surrounding text.
	Link text: `READ MORE` https://www.diligent.com/	Line 1765
	Link text: `READ MORE` https://www.diligent.com/solutions/modern-governance	Line 1756
	Link text: `Learn More` `READ MORE` `READ MORE` `READ MORE` `READ MORE` https://www.diligent.com/solutions/modern-governance/board-and-leadership-collaboration	Line 1623 1682 1711 1737 1766 ...
	Link text: `Learn More` `READ MORE` `READ MORE` `READ MORE` `READ MORE` https://www.diligent.com/solutions/modern-governance/entity-and-subsidiary-management	Line 1587 1649 1678 1709 1740 ...
	This issue was found on another 24 pages. The trial version is limited to showing issues on 4 pages.
	Several links on a page share the same link text, but go to different destinations.	WCAG 2.1 AAA 2.4.9	24 pages
	Make the link text unique for each target, or add additional text using aria-label.
	Link text: `LEARN MORE` `LEARN MORE` https://www.diligent.com/solutions/modern-governance	Line 1527 1552
	Link text: `LEARN MORE` `LEARN MORE` https://www.diligent.com/solutions/modern-governance/board-and-leadership-collaboration	Line 1546 1571
	Link text: `LEARN MORE` `LEARN MORE` `LEARN MORE` `LEARN MORE` https://www.diligent.com/solutions/modern-governance/compensation-and-governance-intel	Line 1540 1565 1590 1615
	Link text: `LEARN MORE` `LEARN MORE` https://www.diligent.com/solutions/modern-governance/entity-and-subsidiary-management	Line 1537 1562
	This issue was found on another 20 pages. The trial version is limited to showing issues on 4 pages.
	Expand all 22 issues

Site Report

Level A

Level AA

Level AAA