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 3 REVIEW 4 FIX

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

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

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.

Link & Button Quality

Action

4 issue(s) across 78 links and 7 buttons

REVIEW

4 issue(s) across 78 links and 7 buttons

4 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://www.ingentaconnect.com/about/publishermenu ("More"); https://www.ingentaconnect.com/about/researchermenu ("More"); https://www.ingentaconnect.com/about/librarianmenu ("More"); https://www.ingenta.com/products/content-management/ ("Click here")

9 link(s) open in new tab without warning

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

Got: https://www.youtube.com/channel/UC_SZbvpUXbs-j953YF9qpYQ; https://twitter.com/ingentaconnect; https://www.linkedin.com/company/ingenta; https://www.youtube.com/channel/UC_SZbvpUXbs-j953YF9qpYQ; https://twitter.com/ingentaconnect; https://www.linkedin.com/company/ingenta; https://www.ingenta.com; https://www.crossref.org; https://www.projectcounter.org

65 link(s) with descriptive text

78 links

0 empty

4 generic text

9 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.youtube.com/channel/UC_SZbvp…	youtube	new tab	Add '(opens in new tab)' to text
https://twitter.com/ingentaconnect	twitter	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/ingenta	linkedIn	new tab	Add '(opens in new tab)' to text
https://www.ingentaconnect.com/about/pub…	More	generic text	Replace with descriptive text
Before: More Suggested: Publishermenu
https://www.ingentaconnect.com/about/res…	More	generic text	Replace with descriptive text
Before: More Suggested: Researchermenu
https://www.ingentaconnect.com/about/lib…	More	generic text	Replace with descriptive text
Before: More Suggested: Librarianmenu
https://www.ingenta.com/products/content…	Click here	generic text	Replace with descriptive text
Before: Click here Suggested: Content Management
https://www.youtube.com/channel/UC_SZbvp…	Youtube	new tab	Add '(opens in new tab)' to text
https://twitter.com/ingentaconnect	twitter	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/ingenta	linkedIn	new tab	Add '(opens in new tab)' to text
https://www.ingenta.com	ingenta company logo	new tab	Add '(opens in new tab)' to text
https://www.crossref.org	Crossref logo	new tab	Add '(opens in new tab)' to text
https://www.projectcounter.org	Project Counter logo	new tab	Add '(opens in new tab)' to text

72 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

https://www.ingentaconnect.com/about/publishermenu ("More"); https://www.ingentaconnect.com/about/researchermenu ("More"); https://www.ingentaconnect.com/about/librarianmenu ("More"); https://www.ingenta.com/products/content-management/ ("Click here")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://www.youtube.com/channel/UC_SZbvpUXbs-j953YF9qpYQ; https://twitter.com/ingentaconnect; https://www.linkedin.com/company/ingenta; https://www.youtube.com/channel/UC_SZbvpUXbs-j953YF9qpYQ; https://twitter.com/ingentaconnect; https://www.linkedin.com/company/ingenta; https://www.ingenta.com; https://www.crossref.org; https://www.projectcounter.org

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

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found: Ingenta Connect ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

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

20 pass 10 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Get your content not…	4.04:1	3.0:1	#000000	#1D70B5	Pass
h2 33 million annual pa…	4.04:1	3.0:1	#000000	#1D70B5	Pass
h2 195 countries	4.04:1	3.0:1	#000000	#1D70B5	Pass
h2 1.6 million users	4.04:1	3.0:1	#000000	#1D70B5	Pass
h3 For Publishers	4.04:1	3.0:1	#000000	#1D70B5	Pass
h3 For Researchers	4.04:1	3.0:1	#000000	#1D70B5	Pass
h3 For Librarians	4.04:1	3.0:1	#000000	#1D70B5	Pass
h3 What's new	4.04:1	3.0:1	#000000	#1D70B5	Pass
h3 Getting online is as…	4.04:1	3.0:1	#000000	#1D70B5	Pass
title Home: Ingenta Connec…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to main content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Browse By section	8.42:1	4.5:1	#000000	#73AAD3	Pass
span Toggle navigation	6.78:1	4.5:1	#000000	#079DD4	Pass
span Shopping Cart	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span login	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a About	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Contact	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Help	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Cart	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span youtube	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.

Landmark Structure

8 landmarks

PASS

8 landmarks

<main> landmark present

3 <nav> landmark(s) found

1 of 3 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link present

Page Structure — as a screen reader sees it

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

Heading Hierarchy

11 headings, 1 skip(s)

PASS

11 headings, 1 skip(s)

Single H1 present

Heading level skipped: H3 → H6 (missing H4)

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

H1 Get your content noticed
H2 33 million annual page views
H2 195 countries
H2 1.6 million users
H3 For Publishers
H3 For Researchers
H3 For Librarians
H3 What's new
H3 Getting online is as easy as 1-2-3!
H3 Sign-in
H6 Cookie Policy skipped

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

A+

Alt Text Quality

All 11 images OK

PASS

All 11 images OK

11 image(s) with good alt text

11 images 11 good alt text

All images have appropriate alt text.

Form Accessibility

1 of 5 controls have issues

PASS

1 of 5 controls have issues

1 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="submit">

4 control(s) properly labeled

5 controls

4 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#search-value1	text	Search	none
#username	text	Username:	for/id
#password	password	Password:	for/id
#remember	checkbox	Remember Login	for/id
input	submit	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /css/connect/print.css

Print Stylesheet ✓ Print Optimized

Print stylesheet /css/connect/print.css ✓Inline @media print Not detected ✗

A+

Lighthouse Accessibility Audits

Score 98/100 — 1 failing, 25 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.

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
Cookie Policy `body.ingenta > aside.mainCookiesPopUp > h6`

These are opportunities to improve keyboard navigation in your application.

○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

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

●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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

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

●Links are distinguishable without relying on color.

●Links have a discernible name

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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○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

○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

○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

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

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Elements with visible text labels have matching accessible names.

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