Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 3 REVIEW 6 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-kfwsgw

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

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

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://webofscience.com/site.webmanifest contains invalid JSON. Browsers cannot parse it.

Got: https://webofscience.com/site.webmanifest

Manifest contains invalid JSON.

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.

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

Action

4 landmarks

REVIEW

4 landmarks

No <main> landmark found

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

1 <nav> landmark(s) found

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

Link & Button Quality

Action

4 issue(s) across 12 links and 8 buttons

REVIEW

4 issue(s) across 12 links and 8 buttons

1 link(s) with generic text

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

Got: https://webofscience.zendesk.com/hc/en-us/articles/20011617329425-Registering… ("Click here")

6 link(s) open in new tab without warning

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

Got: //clarivate.com/legal/privacy-statement/; https://support.clarivate.com/ScientificandAcademicResearch/s/Product-or-tech…; http://clarivate.com/; http://wokinfo.com/terms; https://clarivate.com/legal/privacy-statement/; https://clarivate.com/legal/cookie-policy/

3 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.share-btn (#219 on page); button.share-btn (#232 on page); button.share-btn (#257 on page)

5 link(s) with descriptive text

12 links

0 empty

1 generic text

6 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
https://webofscience.zendesk.com/hc/en-u…	Click here	generic text	Replace with descriptive text
Before: Click here Suggested: 20011617329425 Registering And Signing In To The Web Of Science#H 01k209wp4sjak2a3xa0wc1sznz
//clarivate.com/legal/privacy-statement/	Privacy Statement	new tab	Add '(opens in new tab)' to text
https://support.clarivate.com/Scientific…	Contact us	new tab	Add '(opens in new tab)' to text
http://clarivate.com/	© 2026 Clarivate	new tab	Add '(opens in new tab)' to text
http://wokinfo.com/terms	Terms of use	new tab	Add '(opens in new tab)' to text
https://clarivate.com/legal/privacy-stat…	Privacy statement	new tab	Add '(opens in new tab)' to text
https://clarivate.com/legal/cookie-polic…	Cookie policy	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

10 links and buttons have descriptive text

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

https://webofscience.zendesk.com/hc/en-us/articles/20011617329425-Registering… ("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.

//clarivate.com/legal/privacy-statement/; https://support.clarivate.com/ScientificandAcademicResearch/s/Product-or-tech…; http://clarivate.com/; http://wokinfo.com/terms; https://clarivate.com/legal/privacy-statement/; https://clarivate.com/legal/cookie-policy/

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

Icon-only buttons need an aria-label so screen readers can announce them.

button.share-btn (#219 on page); button.share-btn (#232 on page); button.share-btn (#257 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Color Contrast (Screenshot)

Action

20 text elements analyzed, 1 fail WCAG AA

REVIEW

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

19 pass 1 fail WCAG AA

title Clarivate

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Sign in to continue …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Sign in to your prof…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Institutional Sign I…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Clarivate	1.00:1	4.5:1	#000000	#000000	Fail
option English	21.00:1	4.5:1	#000000	#FFFFFF	Pass
option عربى	21.00:1	4.5:1	#000000	#FFFFFF	Pass
option Español	21.00:1	4.5:1	#000000	#FFFFFF	Pass
option 日本語	21.00:1	4.5:1	#000000	#FFFFFF	Pass
option 한국어	21.00:1	4.5:1	#000000	#FFFFFF	Pass
option Português	21.00:1	4.5:1	#000000	#FFFFFF	Pass
option Русский	21.00:1	4.5:1	#000000	#FFFFFF	Pass
option 简体中文	21.00:1	4.5:1	#000000	#FFFFFF	Pass
option 繁体中文	21.00:1	4.5:1	#000000	#FFFFFF	Pass
strong Welcome!	21.00:1	3.0:1	#000000	#FFFFFF	Pass
a Sign in	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Register	21.00:1	4.5:1	#000000	#FFFFFF	Pass
mat-label Email address	21.00:1	4.5:1	#000000	#FFFFFF	Pass
mat-label Password	21.00:1	4.5:1	#000000	#FFFFFF	Pass
mat-icon visibility	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Forgot Password?	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.

A+

Heading Hierarchy

3 headings

PASS

3 headings

Single H1 present

H1 Sign in to continue with Web of Science
H2 Sign in to your profile
H3 Institutional Sign In

A+

Alt Text Quality

All 2 images OK

PASS

All 2 images OK

2 image(s) with good alt text

2 images 2 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
select	select	language	aria-label
#mat-input-1	input	Email address	for/id
#mat-input-0	password	Password	for/id

A+

Lighthouse Accessibility Audits

Score 95/100 — 2 failing, 29 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.

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
Institutional Sign In `app-shibboleth-login.ng-star-inserted > div.shibboleth-login-form > form.ng-untouched > h3.shibbo-header-txt`

These are opportunities to improve the legibility of your content.

Best practices

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.unauth-page--wos `html.unauth-page--wos`

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

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

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●Select elements have associated label elements.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●ARIA input fields have accessible names

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

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

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○Elements with `role="dialog"` or `role="alertdialog"` 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

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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Skip links are focusable.

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

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