Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

1 PASS 7 REVIEW 5 FIX

Favicon & Branding

Action

3 icon(s) detected

FIX

3 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

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

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

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

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

5 landmarks

REVIEW

5 landmarks

<main> landmark present

3 <nav> landmark(s) found

2 of 3 <nav> elements are unlabeled

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

No banner (header) landmark

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

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

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

Heading Hierarchy

14 headings

REVIEW

14 headings

No H1 heading found

Every page should have one H1 that describes the page content.

1 hidden heading(s) (aria-hidden)

H2 IE 11 Not Supported
H2 Privacy Preference Center
H2 Privacy Preference Center hidden
H3 Your Privacy
H3 Targeting Cookies
H3 Functional Cookies
H3 Essential Cookies
H3 Performance Cookies
H4 Your Privacy
H4 Targeting Cookies
H4 Functional Cookies
H4 Essential Cookies
H4 Performance Cookies
H3 Cookie List

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Alt Text Quality

16 of 43 images have issues

REVIEW

16 of 43 images have issues

16 image(s) with filename as alt text

1 image(s) with alt text over 125 characters

26 image(s) with good alt text

43 images 26 good alt text 16 generic

Issue	Count
filename	16 image(s)
too long	1 image(s)

Form Accessibility

Action

3 of 12 controls have issues

REVIEW

3 of 12 controls have issues

2 control(s) without accessible label

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

Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response">; <input type="submit">

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="email" name="email" id="email-06b81b2f-bbd7-4ece-a4df-478531f217f9">

9 control(s) properly labeled

12 controls

9 labeled

1 placeholder only

2 unlabeled

Control	Type	Label	Method
#gsc-i-id1	text	search	aria-label
#ot-group-id-C0004	checkbox	Targeting Cookies	for/id
#ot-group-id-C0003	checkbox	Functional Cookies	for/id
#ot-group-id-C0002	checkbox	Performance 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
#email-06b81b2f-bbd7-4ece-a4df-478531f217f9	email	(Email*)	placeholder only
#g-recaptcha-response	textarea	(none)	none
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

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Link & Button Quality

2 issue(s) across 225 links and 28 buttons

REVIEW

2 issue(s) across 225 links and 28 buttons

1 link(s) with generic text

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

Got: https://webinars.govtech.com/Flexible-Tech-Strategies-for-Uncertain-Terrain-1… ("Read More")

23 link(s) open in new tab without warning

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

Got: https://webinars.govtech.com/?promo_code=topnav; https://www.erepublic.com/brands/govtech/?__hstc=59400946.63ff311902e90ba19df…; https://newsletters.govtech.com/; https://erepublic.my.salesforce-sites.com/ContactUs/; https://webinars.govtech.com/?promo_code=topnav; https://www.erepublic.com/brands/govtech/?__hstc=59400946.63ff311902e90ba19df…; https://newsletters.govtech.com/; https://erepublic.my.salesforce-sites.com/ContactUs/; https://events.govtech.com/ISAC-Annual-Meeting?promo_code=homepage; https://events.govtech.com/Alabama-Public-Sector-Cybersecurity-Summit?promo_c… (+13 more)

1 button(s) with no accessible text

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

Got: button.GoogleDfpMobileAd-close (#1288 on page)

201 link(s) with descriptive text

225 links

0 empty

1 generic text

23 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://webinars.govtech.com/?promo_code…	Webinars	new tab	Add '(opens in new tab)' to text
https://www.erepublic.com/brands/govtech…	Advertise	new tab	Add '(opens in new tab)' to text
https://newsletters.govtech.com/	Newsletters	new tab	Add '(opens in new tab)' to text
https://erepublic.my.salesforce-sites.co…	Contact	new tab	Add '(opens in new tab)' to text
https://webinars.govtech.com/?promo_code…	Webinars	new tab	Add '(opens in new tab)' to text
https://www.erepublic.com/brands/govtech…	Advertise	new tab	Add '(opens in new tab)' to text
https://newsletters.govtech.com/	Newsletters	new tab	Add '(opens in new tab)' to text
https://erepublic.my.salesforce-sites.co…	Contact	new tab	Add '(opens in new tab)' to text
https://events.govtech.com/ISAC-Annual-M…	ISAC Annual Summit 2026	new tab	Add '(opens in new tab)' to text
https://events.govtech.com/Alabama-Publi…	Alabama Public Sector Cybersec…	new tab	Add '(opens in new tab)' to text
https://events.govtech.com/New-Hampshire…	New Hampshire Digital Governme…	new tab	Add '(opens in new tab)' to text
https://webinars.govtech.com/Rebuilding-…	How Technology Helped Los Ange…	new tab	Add '(opens in new tab)' to text
https://webinars.govtech.com/Secure-Coll…	Secure Collaboration for Moder…	new tab	Add '(opens in new tab)' to text
https://webinars.govtech.com/The-Invisib…	The Invisible Risk: Exposing S…	new tab	Add '(opens in new tab)' to text
https://webinars.govtech.com/Flexible-Te…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Flexible Tech Strategies For Uncertain Terrain 144356.Html?Promo Code=Gt Webinar Web Homemodule
https://newsletters.govtech.com/?promo_c…	SUBSCRIBE	new tab	Add '(opens in new tab)' to text
https://twitter.com/govtechnews	twitter	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/GovernmentT…	youtube	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/governmenttechn…	facebook	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/governm…	linkedin	new tab	Add '(opens in new tab)' to text
https://erepublic.my.salesforce-sites.co…	Do Not Sell My Personal Inform…	new tab	Add '(opens in new tab)' to text
https://www.erepublic.com/privacy/?__hst…	Privacy & AI	new tab	Add '(opens in new tab)' to text
https://www.govtech.com/cpsai	Center for Public Sector AI	new tab	Add '(opens in new tab)' to text
https://www.onetrust.com/solutions/conse…	Powered by OneTrust Opens in a…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

228 links and buttons have descriptive text

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

https://webinars.govtech.com/Flexible-Tech-Strategies-for-Uncertain-Terrain-1… ("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://webinars.govtech.com/?promo_code=topnav; https://www.erepublic.com/brands/govtech/?__hstc=59400946.63ff311902e90ba19df…; https://newsletters.govtech.com/; https://erepublic.my.salesforce-sites.com/ContactUs/; https://webinars.govtech.com/?promo_code=topnav; https://www.erepublic.com/brands/govtech/?__hstc=59400946.63ff311902e90ba19df…; https://newsletters.govtech.com/; https://erepublic.my.salesforce-sites.com/ContactUs/; https://events.govtech.com/ISAC-Annual-Meeting?promo_code=homepage; https://events.govtech.com/Alabama-Public-Sector-Cybersecurity-Summit?promo_c… (+13 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.GoogleDfpMobileAd-close (#1288 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

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 11 fail WCAG AA

REVIEW

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

9 pass 11 fail WCAG AA

h2 IE 11 Not Supported

1.66:1

#000000

#333333

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Privacy Preference Center

1.66:1

#000000

#333333

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Privacy Preference Center

1.66:1

#000000

#333333

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Your Privacy

1.66:1

#000000

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Targeting Cookies

1.66:1

#000000

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Functional Cookies

1.66:1

#000000

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Essential Cookies

1.66:1

#000000

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Performance Cookies

1.66:1

#000000

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Cookie List

1.66:1

#000000

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

title Government Technology State & Local Arti…

1.39:1

#000000

#132934

needs 4.5:1 (normal text)

16px · top of page (header area)

span News

1.39:1

#000000

#132934

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 IE 11 Not Supported	1.66:1	3.0:1	#000000	#333333	Fail
h2 Privacy Preference C…	1.66:1	3.0:1	#000000	#333333	Fail
h2 Privacy Preference C…	1.66:1	3.0:1	#000000	#333333	Fail
h3 Your Privacy	1.66:1	3.0:1	#000000	#333333	Fail
h3 Targeting Cookies	1.66:1	3.0:1	#000000	#333333	Fail
h3 Functional Cookies	1.66:1	3.0:1	#000000	#333333	Fail
h3 Essential Cookies	1.66:1	3.0:1	#000000	#333333	Fail
h3 Performance Cookies	1.66:1	3.0:1	#000000	#333333	Fail
h3 Cookie List	1.66:1	3.0:1	#000000	#333333	Fail
title Government Technolog…	1.39:1	4.5:1	#000000	#132934	Fail
span News	1.39:1	4.5:1	#000000	#132934	Fail
a Analytics	8.80:1	4.5:1	#000000	#A1A9AE	Pass
a Artificial Intellige…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Civic Innovation	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Cloud & Computing	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Cybersecurity	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Lohrmann on Cybersec…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Education	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Election Technology	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Emerging Tech	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.

Lighthouse Accessibility Audits

Score 92/100 — 2 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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.Page-body > bsp-mobile-ad.GoogleDfpMobileAd > button.GoogleDfpMobileAd-close `body.Page-body > bsp-mobile-ad.GoogleDfpMobileAd > button.GoogleDfpMobileAd-close`

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.

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
ARTIFICIAL INTELLIGENCE `div.PromoC > div.PromoC-content > div.Promo-category > a.Link`
JUSTICE & PUBLIC SAFETY `div.PromoC > div.PromoC-content > div.Promo-category > a.Link`
K-12 EDUCATION `div.PromoC > div.PromoC-content > div.Promo-category > a.Link`
HIGHER EDUCATION `div.PromoC > div.PromoC-content > div.Promo-category > a.Link`
HIGHER EDUCATION `div.PromoC > div.PromoC-content > div.Promo-category > a.Link`
SPONSORED `div.PromoC > div.PromoC-content > div.Promo-category > div.Promo-sponsored-title`
WORKFORCE & PEOPLE `div.PromoC > div.PromoC-content > div.Promo-category > a.Link`
CYBERSECURITY `div.PromoC > div.PromoC-content > div.Promo-category > a.Link`
K-12 EDUCATION `div.PromoC > div.PromoC-content > div.Promo-category > a.Link`
BUDGET & FINANCE `div.PromoC > div.PromoC-content > div.Promo-category > a.Link`
EDUCATION `div.PromoC > div.PromoC-content > div.Promo-category > a.Link`
HIGHER EDUCATION `div.PromoC > div.PromoC-content > div.Promo-category > a.Link`

These are opportunities to improve the legibility of your content.

○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

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

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

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

●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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○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

○Heading elements appear in a sequentially-descending order

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○`<input type="image">` elements have `[alt]` text

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

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

○Identical links have the same purpose.

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