Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 REVIEW 5 FIX

404 Error Page

Action

HTTP 421, bare page

FIX

HTTP 421, bare page

Unexpected status code: HTTP 421

Expected HTTP 404 but received 421. This may confuse search engine crawlers.

Got: HTTP 421

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 421 ✗Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

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

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #1a212b

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 ModePartial Dark Mode

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 ✗

Link & Button Quality

2 issue(s) across 103 links and 32 buttons

REVIEW

2 issue(s) across 103 links and 32 buttons

2 link(s) with generic text

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

Got: /ai.html ("LEARN MORE"); /ceo-corner.html ("READ MORE")

4 link(s) open in new tab without warning

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

Got: https://www.linkedin.com/company/educational-testing-service-ets; https://twitter.com/etsinsights?lang=en; https://cookiepedia.co.uk/giving-consent-to-cookies; https://www.onetrust.com/products/cookie-consent/

97 link(s) with descriptive text

103 links

0 empty

2 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/ai.html	LEARN MORE	generic text	Replace with descriptive text
Before: LEARN MORE Suggested: Ai.Html
/ceo-corner.html	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Ceo Corner.Html
https://www.linkedin.com/company/educati…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://twitter.com/etsinsights?lang=en	X	new tab	Add '(opens in new tab)' to text
https://cookiepedia.co.uk/giving-consent…	More information about your pr…	new tab	Add '(opens in new tab)' to text
https://www.onetrust.com/products/cookie…	Powered by OneTrust Opens in a…	new tab	Add '(opens in new tab)' to text

129 links and buttons have descriptive text

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

/ai.html ("LEARN MORE"); /ceo-corner.html ("READ MORE")

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.linkedin.com/company/educational-testing-service-ets; https://twitter.com/etsinsights?lang=en; https://cookiepedia.co.uk/giving-consent-to-cookies; https://www.onetrust.com/products/cookie-consent/

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

Favicon & Branding

Action

5 icon(s) detected

REVIEW

5 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 Harnessing AI to Advance Measurement, Po…

1.01:1

#000000

#010102

needs 3.0:1 (large text)

32px · bottom of viewport

h2 We measure proficiency to help learners,…

1.01:1

#000000

#010102

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Discover AI at ETS

1.01:1

#000000

#010102

needs 3.0:1 (large text)

24px · bottom of viewport · over background image/gradient

h2 Our assessment products

1.01:1

#000000

#010102

needs 3.0:1 (large text)

24px · bottom of viewport

h2 ETS Solutions

1.01:1

#000000

#010102

needs 3.0:1 (large text)

24px · bottom of viewport

h2 ETS Research Institute

1.01:1

#000000

#010102

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Our latest research

1.01:1

#000000

#010102

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Sign up for ETS updates

1.01:1

#000000

#010102

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Privacy Preference Center

1.01:1

#000000

#010102

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Your Privacy

1.01:1

#000000

#010102

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Performance Cookies

1.01:1

#000000

#010102

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Targeting Cookies

1.01:1

#000000

#010102

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Functional Cookies

1.01:1

#000000

#010102

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Strictly Necessary Cookies

1.01:1

#000000

#010102

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Cookie List

1.01:1

#000000

#010102

needs 3.0:1 (large text)

19px · bottom of viewport

title ETS | Global education and talent soluti…

1.10:1

#000000

#0D1015

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

1.10:1

#000000

#0D1015

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to footer

1.09:1

#000000

#0A0F12

needs 4.5:1 (normal text)

16px · top of page (header area)

span Contact

1.11:1

#000000

#0A1216

needs 4.5:1 (normal text)

16px · top of page (header area)

span Login

1.13:1

#000000

#0C1419

needs 4.5:1 (normal text)

16px · above the fold

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Harnessing AI to Adv…	1.01:1	3.0:1	#000000	#010102	Fail
h2 We measure proficien…	1.01:1	3.0:1	#000000	#010102	Fail
h2 Discover AI at ETS	1.01:1	3.0:1	#000000	#010102	Fail
h2 Our assessment produ…	1.01:1	3.0:1	#000000	#010102	Fail
h2 ETS Solutions	1.01:1	3.0:1	#000000	#010102	Fail
h2 ETS Research Institu…	1.01:1	3.0:1	#000000	#010102	Fail
h2 Our latest research	1.01:1	3.0:1	#000000	#010102	Fail
h2 Sign up for ETS upda…	1.01:1	3.0:1	#000000	#010102	Fail
h2 Privacy Preference C…	1.01:1	3.0:1	#000000	#010102	Fail
h3 Your Privacy	1.01:1	3.0:1	#000000	#010102	Fail
h3 Performance Cookies	1.01:1	3.0:1	#000000	#010102	Fail
h3 Targeting Cookies	1.01:1	3.0:1	#000000	#010102	Fail
h3 Functional Cookies	1.01:1	3.0:1	#000000	#010102	Fail
h3 Strictly Necessary C…	1.01:1	3.0:1	#000000	#010102	Fail
h3 Cookie List	1.01:1	3.0:1	#000000	#010102	Fail
title ETS \| Global educati…	1.10:1	4.5:1	#000000	#0D1015	Fail
a Skip to main content	1.10:1	4.5:1	#000000	#0D1015	Fail
a Skip to footer	1.09:1	4.5:1	#000000	#0A0F12	Fail
span Contact	1.11:1	4.5:1	#000000	#0A1216	Fail
span Login	1.13:1	4.5:1	#000000	#0C1419	Fail

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+

Landmark Structure

15 landmarks

PASS

15 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

33 headings

PASS

33 headings

Single H1 present

H1 E.T.S.— Harnessing AI to Advance Measurement, Power Progress
H2 We measure proficiency to help learners, leaders and organizations build a better future.
H3 Assessment Products
H3 ETS Solutions
H3 ETS Research Institute
H2 Discover AI at ETS
H2 Our assessment products
H3 TOEFL®
H3 Praxis®
H3 TOEIC®
H3 GRE®
H2 ETS Solutions
H3 Credentialing
H3 Talent & Workforce
H3 Partnership
H2 ETS Research Institute
H2 Our latest research
H3 Charting the Future of Assessments
H3 A New Vision for Skills-Based Assessment
H3 Best Practices for Constructed-Response Scoring
H2 Sign up for ETS updates
H2 Privacy Preference Center
H3 Your Privacy
H3 Performance Cookies
H3 Targeting Cookies
H3 Functional Cookies
H3 Strictly Necessary Cookies
H4 Your Privacy
H4 Performance Cookies
H4 Targeting Cookies
H4 Functional Cookies
H4 Strictly Necessary Cookies
H3 Cookie List

A+

Alt Text Quality

All 17 images OK

PASS

All 17 images OK

2 image(s) with alt text over 125 characters

1 decorative image(s) correctly marked

14 image(s) with good alt text

17 images 14 good alt text 1 decorative

Issue	Count
too long	2 image(s)

A+

Form Accessibility

All 10 controls labeled

PASS

All 10 controls labeled

10 control(s) properly labeled

10 controls

10 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#search-input-qixpee1	text	What are you looking for?	for/id
#search-input-sw6over	text	What are you looking for?	for/id
#ot-group-id-C0002	checkbox	Performance Cookies	for/id
#ot-group-id-C0004	checkbox	Targeting Cookies	for/id
#ot-group-id-C0003	checkbox	Functional Cookies	for/id
#vendor-search-handler	text	Cookie list search	aria-label
#select-all-hosts-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-leg-handler	checkbox	checkbox label	for/id
#chkbox-id	checkbox	checkbox label	for/id

Lighthouse Accessibility Audits

Score 93/100 — 3 failing, 26 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.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav.c-global-nav__container > ul.c-global-nav__container-list > li.c-global-nav__right-item > a.c-global-nav__register-item `nav.c-global-nav__container > ul.c-global-nav__container-list > li.c-global-nav__right-item > a.c-global-nav__register-item`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Legal `div.c-global-footer__utility-nav > ul > li > a`
Privacy & Security `div.c-global-footer__utility-nav > ul > li > a`
ETS Trademarks `div.c-global-footer__utility-nav > ul > li > a`
Consumer Health Data Privacy Policy `div.c-global-footer__utility-nav > ul > li > a`
Title VI Compliance Statement `div.c-global-footer__utility-nav > ul > li > a`
Cookies Settings `div.c-global-footer__utility-nav > ul > li > button#ot-sdk-btn`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
LEARN ABOUT AI AT ETS `div.c-lead-gen-breaker > div.c-lead-gen-breaker__content > div.c-lead-gen-breaker__action > a.e-cta`

○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

●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

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

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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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

○Identical links have the same purpose.

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