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

1 icon(s) detected

FIX

1 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

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 Missing

✓ 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://authorize.net/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://authorize.net/manifest.json

Manifest contains invalid JSON.

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

1 issue(s) across 83 links and 21 buttons

REVIEW

1 issue(s) across 83 links and 21 buttons

13 link(s) open in new tab without warning

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

Got: https://login.authorize.net; https://partner.authorize.net/widget/widget/RINT/SPA; https://support.authorize.net/; https://usa.visa.com; https://www.cybersource.com; https://www.facebook.com/Authorize.Net; https://www.youtube.com/user/AuthorizeNet; https://x.com/AuthorizeNet; https://www.linkedin.com/company/authorize-net/; https://www.visa.com/privacy (+3 more)

1 button(s) with no accessible text

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

Got: button.next-arrow (#272 on page)

70 link(s) with descriptive text

83 links

0 empty

0 generic text

13 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://login.authorize.net	Merchants	new tab	Add '(opens in new tab)' to text
https://partner.authorize.net/widget/wid…	Partners	new tab	Add '(opens in new tab)' to text
/payments/phone-payments.html	virtual-terminal	img no alt	Add alt attribute to the image
/payments/echeck.html	echeck	img no alt	Add alt attribute to the image
https://support.authorize.net/	Support Center	new tab	Add '(opens in new tab)' to text
/sign-up/become-a-partner/become-a-resel…	virtual-terminal	img no alt	Add alt attribute to the image
/resources/reseller-directory.html	Cybersource Home	img no alt	Add alt attribute to the image
https://usa.visa.com	Visa	new tab	Add '(opens in new tab)' to text
https://www.cybersource.com	Cybersource	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/Authorize.Net	Facebook	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/AuthorizeNe…	YouTube	new tab	Add '(opens in new tab)' to text
https://x.com/AuthorizeNet	X	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/authori…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.visa.com/privacy	Privacy notice	new tab	Add '(opens in new tab)' to text
https://usa.visa.com/legal/global-privac…	Your privacy rights	new tab	Add '(opens in new tab)' to text
https://www.visa.com/cookie-notice	Cookie Notice. (External link,…	new tab	Add '(opens in new tab)' to text
https://www.visa.com/cookie-notice	Visa Cookie Notice (External l…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

90 links and buttons have descriptive text

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

https://login.authorize.net; https://partner.authorize.net/widget/widget/RINT/SPA; https://support.authorize.net/; https://usa.visa.com; https://www.cybersource.com; https://www.facebook.com/Authorize.Net; https://www.youtube.com/user/AuthorizeNet; https://x.com/AuthorizeNet; https://www.linkedin.com/company/authorize-net/; https://www.visa.com/privacy (+3 more)

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.next-arrow (#272 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

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 7 fail WCAG AA

REVIEW

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

13 pass 7 fail WCAG AA

h2 Smart for businesses, smart for partners

2.49:1

#2B6AFD

#BCBFC7

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Make payments a growth engine for your b…

2.49:1

#2B6AFD

#BCBFC7

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Learn how payments work

2.49:1

#2B6AFD

#BCBFC7

needs 3.0:1 (large text)

24px · bottom of viewport

title Credit card payment processor, online pa…

2.38:1

#000000

#1434CB

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to login

2.38:1

#000000

#1434CB

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to content

2.38:1

#000000

#1434CB

needs 4.5:1 (normal text)

16px · top of page (header area)

p Payments and services

2.38:1

#000000

#1434CB

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Welcome to the new	11.42:1	3.0:1	#000000	#BCBFC7	Pass
h1 Authorize.net	11.42:1	3.0:1	#000000	#BCBFC7	Pass
h2 Smart for businesses…	2.49:1	3.0:1	#2B6AFD	#BCBFC7	Fail
h2 See how we’ve reim…	11.42:1	3.0:1	#000000	#BCBFC7	Pass
h2 Make payments a grow…	2.49:1	3.0:1	#2B6AFD	#BCBFC7	Fail
h2 Accept the payment t…	11.42:1	3.0:1	#000000	#BCBFC7	Pass
h2 Award-winning suppor…	11.42:1	3.0:1	#000000	#BCBFC7	Pass
h2 Learn how payments w…	2.49:1	3.0:1	#2B6AFD	#BCBFC7	Fail
h2 Ready to start accep…	11.42:1	3.0:1	#000000	#BCBFC7	Pass
h2 Company	11.42:1	3.0:1	#000000	#BCBFC7	Pass
h3 New features, built …	11.42:1	3.0:1	#000000	#BCBFC7	Pass
h3 Take, request, and f…	11.42:1	3.0:1	#000000	#BCBFC7	Pass
h3 Not sure about somet…	11.42:1	3.0:1	#000000	#BCBFC7	Pass
h3 Workspaces that stay…	11.42:1	3.0:1	#000000	#BCBFC7	Pass
h3 Tools to stop fraud …	11.42:1	3.0:1	#000000	#BCBFC7	Pass
h3 Partner with us	11.42:1	3.0:1	#000000	#BCBFC7	Pass
title Credit card payment …	2.38:1	4.5:1	#000000	#1434CB	Fail
a Skip to login	2.38:1	4.5:1	#000000	#1434CB	Fail
a Skip to content	2.38:1	4.5:1	#000000	#1434CB	Fail
p Payments and service…	2.38:1	4.5:1	#000000	#1434CB	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

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

Heading Hierarchy

26 headings, 1 skip(s)

PASS

26 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

H1 Welcome to the new Authorize.net
H2 Smart for businesses, smart for partners
H2 See how we’ve reimagined Authorize.net
H3 New features, built for speed
H3 Take, request, and find payments
H3 Not sure about something? Ask Anet
H3 Workspaces that stay connected
H3 Tools to stop fraud fast
H2 Make payments a growth engine for your business
H4 Online payments skipped
H4 Smartphone payments
H4 In person with a card reader
H4 Over the phone
H4 eCheck
H4 Simple Checkout
H2 Accept the payment types your customers prefer
H2 Award-winning support
H2 Learn how payments work
H3 Partner with us
H4 Become a reseller partner
H4 Find a reseller
H2 Ready to start accepting payments?
H2 Company
H2 Payments
H2 Resources
H2 Connect

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 33 images OK

PASS

All 33 images OK

16 decorative image(s) correctly marked

17 image(s) with good alt text

33 images 17 good alt text 16 decorative

All images have appropriate alt text.

Form Accessibility

1 of 7 controls have issues

PASS

1 of 7 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="checkbox" id="country-selector-toggle">

6 control(s) properly labeled

7 controls

6 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
q	text	Search through site content	aria-label
#menu-toggle	checkbox	MENU	for/id
#wscr_drawer_consent_opt_1	checkbox	Consent for: Strictly necessary	for/id
#wscr_drawer_consent_opt_2	checkbox	Consent for: Site experience	for/id
#wscr_drawer_consent_opt_3	checkbox	Consent for: Performance and operation	for/id
#wscr_drawer_consent_opt_4	checkbox	Consent for: Marketing, personalization and advertising	for/id
#country-selector-toggle	checkbox	(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

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 | Authorize.net ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

Lighthouse Accessibility Audits

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

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Payments and services Accept and manage payments. Explore payment solutions … `div.root > div.aem-Grid > div.header > header`
Authorize.net Home `div.aem-Grid > div.header > header > div.logo`
Company About us Blog Visa Cybersource Payments Online payments Mobile p… `body > div.root > div.aem-Grid > div.footer`
About us `div.column > div.link > p > a`
Blog `div.column > div.link > p > a`
Visa `div.column > div.link > p > a.external`
Cybersource `div.column > div.link > p > a.external`
Online payments `div.column > div.link > p > a`
Mobile payments `div.column > div.link > p > a`
eCheck payments `div.column > div.link > p > a`
Virtual point of sale `div.column > div.link > p > a`
Our features `div.column > div.link > p > a`
How payments work `div.column > div.link > p > a`
Become a reseller `div.column > div.link > p > a`
Sitemap `div.column > div.link > p > a`
Facebook `div.column > div.link > p > a.external`
YouTube `div.column > div.link > p > a.external`
X `div.column > div.link > p > a.external`
LinkedIn `div.column > div.link > p > a.external`
Authorize.net Home `div.menu > div.bottom > div.logo > a`
United States `div.column > div.country-selector > div.dropdown-countries > a`
UK/Europe `div.column > div.country-selector > div.dropdown-countries > a`
Australia `div.column > div.country-selector > div.dropdown-countries > a`
Privacy notice `div.column > div.link > p > a.external`
Terms of use `div.column > div.link > p > a`
Intellectual property rights `div.column > div.link > p > a`
Cookie policy `div.column > div.link > p > a`
Data Processing Agreement `div.column > div.link > p > a`
Your privacy rights `div.column > div.link > p > a.external`

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
Online payments `div.contentWell > div#cw-242956191 > div.text > h4`

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

●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

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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Skip links are focusable.

●Document has a main landmark.

●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

○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

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

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

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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