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 1 REVIEW 6 FIX

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

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 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

2 icon(s) detected

FIX

2 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

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://oregon.gov/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://oregon.gov/manifest.json

Manifest contains invalid JSON.

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: #222222

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 ✗

Form Accessibility

Action

5 of 9 controls have issues

REVIEW

5 of 9 controls have issues

5 control(s) without accessible label

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

Got: <input type="text" name="sl" id="goog-gt-votingInputSrcLang">; <input type="text" name="tl" id="goog-gt-votingInputTrgLang">; <input type="text" name="query" id="goog-gt-votingInputSrcText">; <input type="text" name="gtrans" id="goog-gt-votingInputTrgText">; <input type="text" name="vote" id="goog-gt-votingInputVote">

4 control(s) properly labeled

9 controls

4 labeled

0 placeholder only

5 unlabeled

Control	Type	Label	Method
select	select	Language Translate Widget	aria-label
#id-2581567	search	Search	for/id
#helpfulPagePollModalFeedbackTypes	select	I'd like to submit a/an	for/id
#helpfulPagePollModalComment	textarea	How can we make this page more helpful?	for/id
#goog-gt-votingInputSrcLang	text	(none)	none
#goog-gt-votingInputTrgLang	text	(none)	none
#goog-gt-votingInputSrcText	text	(none)	none
#goog-gt-votingInputTrgText	text	(none)	none
#goog-gt-votingInputVote	text	(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+

Landmark Structure

6 landmarks

PASS

6 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

44 headings

PASS

44 headings

Single H1 present

H1 Oregon.gov
H2 Top Services
H3 Wildfire Response and Recovery
H3 Get vaccinated for COVID-19
H3 Find Jobs and Opportunities
H3 Help for Small Business Owners
H3 Unemployment Claims and Status
H3 Register to Vote in Oregon
H2 Top Links
H3 Our Government
H3 Health & Family
H3 Visit Oregon
H3 Business
H2 Looking for a State Agency?
H2 Looking for an Online Service?
H2 Featured News & Initiatives
H3 2026 edition of The Essential Rules for Oregon Courts
H3 Meet the All New Oregon Blue Book
H3 2026 edition of the Criminal Code of Oregon
H3 Election Integrity
H3 Search For Your Unclaimed Property For Free Today!
H3 Paid Leave Oregon
H2 Did you know…
H2 Latest News Stories
H3 Oregon Prepared Conference 2026 Brings Together Emergency… Management Leaders from Across the State
H3 Information About New World Screwworm
H3 Shilo gets the mobility they need to be fully independent in… their career thanks to Vocational Rehabilitation service
H2 #MyOregon
H3 Seaside, Oregon
H3 America My Love
H3 Thor's Well
H3 No Title
H3 Manzanita, Oregon
H3 Early Morning View of Brokentop
H3 Beautiful Wildflower
H3 Cool Little Creek (Oregon)
H3 Eastbank Esplanade (Willamette River, Oregon)
H2 Footer Links
H3 At Your Service
H3 Elected Officials
H3 News & Alerts
H3 How to recognize an official Oregon website
H4 Official websites use .gov
H4 Secure .gov websites use HTTPS

A+

Alt Text Quality

All 18 images OK

PASS

All 18 images OK

3 decorative image(s) correctly marked

15 image(s) with good alt text

18 images 15 good alt text 3 decorative

All images have appropriate alt text.

A+

Link & Button Quality

411 links, 40 buttons — all OK

PASS

411 links, 40 buttons — all OK

1 link(s) open in new tab without warning

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

Got: https://translate.google.com

410 link(s) with descriptive text

411 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://translate.google.com	Translate	new tab	Add '(opens in new tab)' to text

450 links and buttons have descriptive text

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

https://translate.google.com

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

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Oregon.gov	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Top Services	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Top Links	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Looking for a State …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Looking for an Onlin…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Featured News & Init…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Did you know…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Latest News Stories	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 #MyOregon	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Footer Links	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Wildfire Response an…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Get vaccinated for C…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Find Jobs and Opport…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Help for Small Busin…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Unemployment Claims …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Register to Vote in …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Our Government	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Health & Family	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Visit Oregon	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Business	21.00:1	3.0: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 93/100 — 2 failing, 24 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
or-secondary-navigation > div.or-secondary-navigation-content > or-translate.notranslate > a#id_738597736 `or-secondary-navigation > div.or-secondary-navigation-content > or-translate.notranslate > a#id_738597736`
or-secondary-navigation > div.or-secondary-navigation-content > or-accessibility-options > a `or-secondary-navigation > div.or-secondary-navigation-content > or-accessibility-options > a`

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
You are currently on Slide 1 `or-featured > div > div.or-featured-indicators > a.or-active`
Jump to slide 2 `or-featured > div > div.or-featured-indicators > a`
Jump to slide 3 `or-featured > div > div.or-featured-indicators > a`
Jump to slide 4 `or-featured > div > div.or-featured-indicators > a`
Jump to slide 5 `or-featured > div > div.or-featured-indicators > a`
Jump to slide 6 `or-featured > div > div.or-featured-indicators > a`

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.

●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

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○Links are distinguishable without relying on color.

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

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