Issues reported for Oregon Museum of Science and Industry home

About the page

URL: https://omsi.edu/
Tested 182 days ago on 2026-05-12 at 23:15 by job 260512T2314-42w
Rule engines: 10 called, 10 able to test, violations reported by 10
Results: 1287 violations, 686 violators, 76 issues
Download the full technical report (JSON)

History

This is the only available report about the page.

Request a retest

Issues reported

Highest priority: 22

ID not unique
- Why it matters: User may be pointed to the wrong item
- Priority: highest
- Related WCAG standard: 4.1
- Reported by 5 rule engines (Alfa + ASLint + Html Checker API + HTML CodeSniffer + QualWeb)
- Results: 39 violations, 20 violators
Where was the issue found?
button not named
- Why it matters: User cannot get help explaining a button
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 5 rule engines (Alfa + Axe + HTML CodeSniffer + QualWeb + WAVE)
- Results: 5 violations, 2 violators
Where was the issue found?
contrast poor
- Why it matters: Content is difficult to understand
- Priority: highest
- Related WCAG standard: 1.4.3
- Reported by 3 rule engines (Accessibility Checker + Axe + WAVE)
- Results: 15 violations, 14 violators
Where was the issue found?
aria attribute invalid
- Why it matters: Item behavior violates user expectations
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 3 rule engines (Alfa + Html Checker API + QualWeb)
- Results: 3 violations, 2 violators
Where was the issue found?
svg image not named
- Why it matters: User cannot get help understanding an image
- Priority: highest
- Related WCAG standard: 1.1.1
- Reported by 2 rule engines (Accessibility Checker + ASLint)
- Results: 65 violations, 65 violators
Where was the issue found?
attribute invalid
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (Accessibility Checker + Html Checker API)
- Results: 7 violations, 6 violators
Where was the issue found?
control not named
- Why it matters: User cannot get help on how to operate a form item
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (Accessibility Checker + WAVE)
- Results: 2 violations, 2 violators
Where was the issue found?
figure not named
- Why it matters: User cannot get help on the topic of a figure
- Priority: highest
- Related WCAG standard: 1.1.1
- Reported by 1 rule engine (Accessibility Checker)
- Results: 25 violations, 25 violators
Where was the issue found?
descendant missing
- Why it matters: Keyboard-only user cannot operate a custom tool
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Alfa)
- Results: 1 violation, 1 violator
Where was the issue found?
control label invisible
- Why it matters: User cannot understand how to operate a form item
- Priority: highest
- Related WCAG standard: 2.4.6
- Reported by 1 rule engine (ASLint)
- Results: 4 violations, 4 violators
Where was the issue found?
requirement invalid
- Why it matters: User may fail to get help determining whether a form item must be completed
- Priority: highest
- Related WCAG standard: 1.3.5
- Reported by 1 rule engine (ASLint)
- Results: 1 violation, 1 violator
Where was the issue found?
base element missing where required
- Why it matters: Browser cannot find a needed external resource
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- Results: 1 violation, 1 violator
Where was the issue found?
target empty
- Why it matters: Item is displayed improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- Results: 115 violations, 115 violators
Where was the issue found?
attribute value invalid
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- Results: 2 violations, 2 violators
Where was the issue found?
parent invalid
- Why it matters: User cannot properly operate an item
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- Results: 4 violations, 4 violators
Where was the issue found?
ancestor and descendant roles incompatible
- Why it matters: User may misunderstand or be blocked from exposure to an item
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Html Checker API)
- Results: 1 violation, 1 violator
Where was the issue found?
ID empty
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- Results: 5 violations, 5 violators
Where was the issue found?
image not named
- Why it matters: User cannot get help to know what is in an image
- Priority: highest
- Related WCAG standard: 1.1.1
- Reported by 1 rule engine (Html Checker API)
- Results: 1 violation, 1 violator
Where was the issue found?
link element misplaced
- Why it matters: Page fails to get a needed external resource
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 1 violation, 1 violator
Where was the issue found?
autocomplete missing
- Why it matters: User cannot get help entering personal information in a form
- Priority: highest
- Related WCAG standard: 1.3.5
- Reported by 1 rule engine (Testaro)
- Results: 1 violation, 1 violator
Where was the issue found?
Tab-focusable elements wrong
- Why it matters: Item selections by a keyboard-only user are useless or impossible
- Priority: highest
- Related WCAG standard: 2.1.1
- Reported by 1 rule engine (Testaro)
- Results: 1 violation, 1 violator
Where was the issue found?
label reference invalid
- Why it matters: User cannot get help understanding an item in a form
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (WAVE)
- Results: 1 violation, 1 violator
Where was the issue found?

High priority: 19

visible label not in name
- Why it matters: User cannot get help choosing a form control to operate
- Priority: high
- Related WCAG standard: 2.5.3
- Reported by 5 rule engines (Accessibility Checker + Alfa + Axe + HTML CodeSniffer + QualWeb)
- Results: 85 violations, 35 violators
Where was the issue found?
heading empty
- Why it matters: User cannot get help on the topic of a part of the page
- Priority: high
- Related WCAG standard: 2.4.6
- Reported by 4 rule engines (ASLint + Html Checker API + HTML CodeSniffer + WAVE)
- Results: 4 violations, 3 violators
Where was the issue found?
code obsolete
- Why it matters: Page contains code that is no longer standard
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Accessibility Checker)
- Results: 3 violations, 3 violators
Where was the issue found?
navigations not distinctly named
- Why it matters: User cannot get help on how some of the page is organized
- Priority: high
- Related WCAG standard: 1.3.6
- Reported by 1 rule engine (Accessibility Checker)
- Results: 3 violations, 3 violators
Where was the issue found?
label empty
- Why it matters: User cannot get help on the topics of form items
- Priority: high
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- Results: 1 violation, 1 violator
Where was the issue found?
landmarks not distinctly named
- Why it matters: User cannot get help on how some of the page is organized
- Priority: high
- Related WCAG standard: 1.3.6
- Reported by 1 rule engine (Axe)
- Results: 1 violation, 1 violator
Where was the issue found?
tab-opening link action unstated
- Why it matters: Following a link opens a new window, surprising a user
- Priority: high
- Related WCAG standard: 3.2.5
- Reported by 1 rule engine (Editoria11y)
- Results: 1 violation, 1 violator
Where was the issue found?
DOCTYPE invalid
- Why it matters: Browser processes the page improperly
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker API)
- Results: 1 violation, 1 violator
Where was the issue found?
meta element duplicated
- Why it matters: Browser may process the page incorrectly
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker API)
- Results: 1 violation, 1 violator
Where was the issue found?
meta X-UA-Compatible incomplete
- Why it matters: Internet Explorer may display the page incorrectly
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker API)
- Results: 1 violation, 1 violator
Where was the issue found?
CSS property does not exist
- Why it matters: Page cannot be properly displayed
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker API)
- Results: 1 violation, 1 violator
Where was the issue found?
attribute obsolete
- Why it matters: Page includes obsolete code that the browser may fail to process
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker API)
- Results: 12 violations, 6 violators
Where was the issue found?
code invalid
- Why it matters: Invalid code in the page may prevent a helper from working
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker API)
- Results: 4 violations, 4 violators
Where was the issue found?
element closure invalid
- Why it matters: Page contains invalid code
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker API)
- Results: 1 violation, 1 violator
Where was the issue found?
box size absolute
- Why it matters: User cannot enlarge the content of an item for readability
- Priority: high
- Related WCAG standard: 1.4.4
- Reported by 1 rule engine (QualWeb)
- Results: 3 violations, 3 violators
Where was the issue found?
small targets too near to each other
- Why it matters: User cannot reliably choose an item to click or tap
- Priority: high
- Related WCAG standard: 2.5.8
- Reported by 1 rule engine (Testaro)
- Results: 16 violations, 16 violators
Where was the issue found?
element focusability and operability conflict
- Why it matters: Keyboard-only user cannot operate an item
- Priority: high
- Related WCAG standard: 2.1.1
- Reported by 1 rule engine (Testaro)
- Results: 11 violations, 11 violators
Where was the issue found?
hover indication poor
- Why it matters: User cannot explore the page reliably with a mouse
- Priority: high
- Related WCAG standard: 2.4
- Reported by 1 rule engine (Testaro)
- Results: 13 violations, 13 violators
Where was the issue found?
font small
- Why it matters: Text is difficult to read
- Priority: high
- Related WCAG standard: 1.4
- Reported by 1 rule engine (WAVE)
- Results: 6 violations, 6 violators
Where was the issue found?

Low priority: 8

line height low
- Why it matters: Text is difficult to read
- Priority: low
- Related WCAG standard: 1.4.8
- Reported by 2 rule engines (Alfa + Testaro)
- Results: 146 violations, 145 violators
Where was the issue found?
links named identically
- Why it matters: User cannot get help differentiating links
- Priority: low
- Related WCAG standard: 2.4.4
- Reported by 2 rule engines (QualWeb + Testaro)
- Results: 36 violations, 25 violators
Where was the issue found?
heading heads nothing
- Why it matters: Helper misdescribes the page
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Alfa)
- Results: 1 violation, 1 violator
Where was the issue found?
heading structure illogical
- Why it matters: Helper misdescribes the page
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 2 violations, 1 violator
Where was the issue found?
link indication poor
- Why it matters: User cannot differentiate a link from plain text
- Priority: low
- Related WCAG standard: 1.3.3
- Reported by 1 rule engine (Testaro)
- Results: 54 violations, 54 violators
Where was the issue found?
page content moves spontaneously
- Why it matters: Motion-sensitive user may suffer harm
- Priority: low
- Related WCAG standard: 2.2.2
- Reported by 1 rule engine (Testaro)
- Results: 1 violation, 1 violator
Where was the issue found?
focus indication improvable
- Why it matters: Keyboard-only user cannot easily choose an item to operate
- Priority: low
- Related WCAG standard: 2.4.7
- Reported by 1 rule engine (Testaro)
- Results: 44 violations, 44 violators
Where was the issue found?
adjacent links not combined
- Why it matters: Keyboard-only user expends extra effort to skip a link
- Priority: low
- Related WCAG standard: 2.4.4
- Reported by 1 rule engine (WAVE)
- Results: 1 violation, 1 violator
Where was the issue found?

Lowest priority: 27

text contrast improvable
- Why it matters: Content is not easy to understand
- Priority: lowest
- Related WCAG standard: 1.4.6
- Reported by 5 rule engines (Alfa + ASLint + Axe + HTML CodeSniffer + QualWeb)
- Results: 132 violations, 109 violators
Where was the issue found?
tab-opening link action unstated?
- Why it matters: Following a link opens a new window, possibly surprising a user
- Priority: lowest
- Related WCAG standard: 3.2.5
- Reported by 3 rule engines (ASLint + HTML CodeSniffer + Testaro)
- Results: 15 violations, 9 violators
Where was the issue found?
role redundant
- Why it matters: Page includes unnecessary code
- Priority: lowest
- Related WCAG standard: 4.1.2
- Reported by 2 rule engines (Accessibility Checker + Html Checker API)
- Results: 4 violations, 2 violators
Where was the issue found?
aria attribute redundant
- Why it matters: Page includes unnecessary code
- Priority: lowest
- Related WCAG standard: 4.1.2
- Reported by 2 rule engines (Accessibility Checker + Html Checker API)
- Results: 2 violations, 1 violator
Where was the issue found?
content beyond landmarks
- Why it matters: User cannot get help on how some of the page is organized
- Priority: lowest
- Related WCAG standard: 1.3.6
- Reported by 2 rule engines (Alfa + Axe)
- Results: 2 violations, 2 violators
Where was the issue found?
all-capital text
- Why it matters: Text is difficult to read
- Priority: lowest
- Related WCAG standard: 3.1.5
- Reported by 2 rule engines (Alfa + Testaro)
- Results: 10 violations, 10 violators
Where was the issue found?
link name vague
- Why it matters: User may misunderstand what a link points to
- Priority: lowest
- Related WCAG standard: 2.4.4
- Reported by 2 rule engines (ASLint + WAVE)
- Results: 19 violations, 19 violators
Where was the issue found?
text contrast not testable
- Why it matters: Text may be difficult to read
- Priority: lowest
- Related WCAG standard: 1.4.3
- Reported by 2 rule engines (HTML CodeSniffer + QualWeb)
- Results: 85 violations, 61 violators
Where was the issue found?
target small
- Why it matters: User cannot reliably choose an item to click or tap
- Priority: lowest
- Related WCAG standard: 2.5.5
- Reported by 1 rule engine (Alfa)
- Results: 25 violations, 23 violators
Where was the issue found?
item makes testing inconclusive
- Why it matters: Item prevents a conclusive accessibility test
- Priority: lowest
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Alfa)
- Results: 2 violations, 1 violator
Where was the issue found?
button name not visible
- Why it matters: User cannot get help explaining a button
- Priority: lowest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (ASLint)
- Results: 8 violations, 8 violators
Where was the issue found?
custom button keyboard-inoperable?
- Why it matters: Custom item may prevent a keyboard-only user from operating it
- Priority: lowest
- Related WCAG standard: 2.1.1
- Reported by 1 rule engine (ASLint)
- Results: 7 violations, 7 violators
Where was the issue found?
labeling risky
- Why it matters: User may misunderstand a form control
- Priority: lowest
- Related WCAG standard: 3.3.2
- Reported by 1 rule engine (ASLint)
- Results: 2 violations, 2 violators
Where was the issue found?
links dubiously share name
- Why it matters: User may be unable to get help differentiating links
- Priority: lowest
- Related WCAG standard: 2.4.4
- Reported by 1 rule engine (Axe)
- Results: 7 violations, 7 violators
Where was the issue found?
type redundant
- Why it matters: Page includes unnecessary code
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- Results: 40 violations, 40 violators
Where was the issue found?
section heading missing
- Why it matters: User cannot understand the topic of a part of the page
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- Results: 2 violations, 2 violators
Where was the issue found?
image dubiously marked decorative
- Why it matters: Helper ignores an image that is apparently informative
- Priority: lowest
- Related WCAG standard: 1.1.1
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 8 violations, 8 violators
Where was the issue found?
position sticky
- Why it matters: User may be unable to see needed content or may be forced to scroll in both dimensions
- Priority: lowest
- Related WCAG standard: 1.4.10
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 5 violations, 5 violators
Where was the issue found?
overflow hidden?
- Why it matters: User may be unable to enlarge the text for readability
- Priority: lowest
- Related WCAG standard: 1.4.4
- Reported by 1 rule engine (QualWeb)
- Results: 74 violations, 64 violators
Where was the issue found?
label location dubious
- Why it matters: User may fail to notice the explanation of an item in a form
- Priority: lowest
- Related WCAG standard: 3.3.2
- Reported by 1 rule engine (QualWeb)
- Results: 5 violations, 5 violators
Where was the issue found?
large visible-element count
- Why it matters: User cannot easily find items in the page
- Priority: lowest
- Related WCAG standard: 2.4
- Reported by 1 rule engine (Testaro)
- Results: 1 violation, 1 violator
Where was the issue found?
text distortion
- Why it matters: Text is difficult to read
- Priority: lowest
- Related WCAG standard: 3.1.5
- Reported by 1 rule engine (Testaro)
- Results: 25 violations, 25 violators
Where was the issue found?
role assigned instead of implicit
- Why it matters: User may misunderstand the purpose of an item
- Priority: lowest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Testaro)
- Results: 15 violations, 15 violators
Where was the issue found?
inconsistent heading, link, or button styles
- Why it matters: User cannot easily distinguish items of different types
- Priority: lowest
- Related WCAG standard: 3.2.4
- Reported by 1 rule engine (Testaro)
- Results: 6 violations, 1 violator
Where was the issue found?
z-index not zero
- Why it matters: User cannot predict the effect of clicking
- Priority: lowest
- Related WCAG standard: 1.4
- Reported by 1 rule engine (Testaro)
- Results: 27 violations, 27 violators
Where was the issue found?
heading-like styles dubious
- Why it matters: User may be unable to understand the topic of a part of the page
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (WAVE)
- Results: 5 violations, 5 violators
Where was the issue found?
noscript element not equivalent?
- Why it matters: User who has disabled JavaScript may be denied some content
- Priority: lowest
- Related WCAG standard: 4.1
- Reported by 1 rule engine (WAVE)
- Results: 1 violation, 1 violator
Where was the issue found?

What you can do

Choose how to address these issues:

Do it yourself

Explore the issues, following the links above. Decide which issues are actual defects. Plan and implement corrections. Then retest the page.

Use artificial intelligence

Make Kilotest available to an AI assistant. Then give it a prompt like this:

Kilotest reports issues on the Oregon Museum of Science and Industry home web page. Describe them and propose a plan to resolve the genuine defects.

Issues reported for Oregon Museum of Science and Industry home

About the page

History

Issues reported

ID not unique

button not named

contrast poor

aria attribute invalid

svg image not named

attribute invalid

control not named

figure not named

descendant missing

control label invisible

requirement invalid

base element missing where required

target empty

attribute value invalid

parent invalid

ancestor and descendant roles incompatible

ID empty

image not named

link element misplaced

autocomplete missing

Tab-focusable elements wrong

label reference invalid

visible label not in name

heading empty

code obsolete

navigations not distinctly named

label empty

landmarks not distinctly named

tab-opening link action unstated

DOCTYPE invalid

meta element duplicated

meta X-UA-Compatible incomplete

CSS property does not exist

attribute obsolete

code invalid

element closure invalid

box size absolute

small targets too near to each other

element focusability and operability conflict

hover indication poor

font small

line height low

links named identically

heading heads nothing

heading structure illogical

link indication poor

page content moves spontaneously

focus indication improvable

adjacent links not combined

text contrast improvable

tab-opening link action unstated?

role redundant

aria attribute redundant

content beyond landmarks

all-capital text

link name vague

text contrast not testable

target small

item makes testing inconclusive

button name not visible

custom button keyboard-inoperable?

labeling risky

links dubiously share name

type redundant

section heading missing

image dubiously marked decorative

position sticky

overflow hidden?

label location dubious

large visible-element count

text distortion

role assigned instead of implicit

inconsistent heading, link, or button styles

z-index not zero

heading-like styles dubious

noscript element not equivalent?