Kilotest: Issues reported for Oregon Museum of Science and Industry
About the Oregon Museum of Science and Industry page
- URL: https://omsi.edu/
- Tested 68 days ago by job
42won 2026-05-12 at 23:14
Should Kilotest retest the page?
Issues reported
Summary
10 rule engines reported issues (Accessibility Checker + Alfa + ASLint + Axe + Editoria11y + Html Checker API + HTML CodeSniffer + QualWeb + Testaro + WAVE)
75 issues were reported (22 highest, 18 high, 8 low, 27 lowest priority)
690 violators were reported
Download the full technical report
Details
Highest priority: 22
-
ID not unique
- Why it matters: User may be pointed to the wrong item
- Related WCAG standard: 4.1.1
- Reported by 5 rule engines (Alfa + ASLint + Html Checker API + HTML CodeSniffer + QualWeb)
- 20 violators were reported
-
button not named
- Why it matters: User cannot get help explaining a button
- Related WCAG standard: 4.1.2
- Reported by 5 rule engines (Alfa + Axe + HTML CodeSniffer + QualWeb + WAVE)
- 2 violators were reported
-
contrast poor
- Why it matters: Content is difficult to understand
- Related WCAG standard: 1.4.3
- Reported by 3 rule engines (Accessibility Checker + Axe + WAVE)
- 14 violators were reported
-
svg image not named
- Why it matters: User cannot get help understanding an image
- Related WCAG standard: 1.1.1
- Reported by 2 rule engines (Accessibility Checker + ASLint)
- 65 violators were reported
-
attribute invalid
- Why it matters: Item behaves improperly
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (Accessibility Checker + Html Checker API)
- 6 violators were reported
-
control not named
- Why it matters: User cannot get help on how to operate a form item
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (Accessibility Checker + WAVE)
- 2 violators were reported
-
aria attribute invalid
- Why it matters: Item behavior violates user expectations
- Related WCAG standard: 4.1.2
- Reported by 2 rule engines (Alfa + QualWeb)
- 1 violator was reported
-
figure not named
- Why it matters: User cannot get help on the topic of a figure
- Related WCAG standard: 1.1.1
- Reported by 1 rule engine (Accessibility Checker)
- 25 violators were reported
-
descendant missing
- Why it matters: Keyboard-only user cannot operate a custom tool
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Alfa)
- 1 violator was reported
-
control label invisible
- Why it matters: User cannot understand how to operate a form item
- Related WCAG standard: 2.4.6
- Reported by 1 rule engine (ASLint)
- 4 violators were reported
-
requirement invalid
- Why it matters: User may fail to get help determining whether a form item must be completed
- Related WCAG standard: 1.3.5
- Reported by 1 rule engine (ASLint)
- 1 violator was reported
-
base element missing where required
- Why it matters: Browser cannot find a needed external resource
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- 1 violator was reported
-
target empty
- Why it matters: Item is displayed improperly
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- 115 violators were reported
-
attribute value invalid
- Why it matters: Item behaves improperly
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- 7 violators were reported
-
parent invalid
- Why it matters: User cannot properly operate an item
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- 4 violators were reported
-
ancestor and descendant roles incompatible
- Why it matters: User may misunderstand or be blocked from exposure to an item
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Html Checker API)
- 1 violator was reported
-
image not named
- Why it matters: User cannot get help to know what is in an image
- Related WCAG standard: 1.1.1
- Reported by 1 rule engine (Html Checker API)
- 1 violator was reported
-
src empty
- Why it matters: Image, audio, or video to be shown cannot be found
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- 1 violator was reported
-
link element invalid
- Why it matters: Document fails to get a needed external resource
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (HTML CodeSniffer)
- 1 violator was reported
-
autocomplete missing
- Why it matters: User cannot get help entering personal information in a form
- Related WCAG standard: 1.3.5
- Reported by 1 rule engine (Testaro)
- 1 violator was reported
-
Tab-focusable elements wrong
- Why it matters: Item selections by a keyboard-only user are useless or impossible
- Related WCAG standard: 2.1.1
- Reported by 1 rule engine (Testaro)
- 1 violator was reported
-
label reference invalid
- Why it matters: User cannot get help understanding an item in a form
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (WAVE)
- 1 violator was reported
High priority: 18
-
visible label not in name
- Why it matters: User cannot get help choosing a form control to operate
- Related WCAG standard: 2.5.3
- Reported by 5 rule engines (Accessibility Checker + Alfa + Axe + HTML CodeSniffer + QualWeb)
- 35 violators were reported
-
heading empty
- Why it matters: User cannot get help on the topic of a part of the document
- Related WCAG standard: 2.4.6
- Reported by 4 rule engines (ASLint + Html Checker API + HTML CodeSniffer + WAVE)
- 4 violators were reported
-
code obsolete
- Why it matters: Document contains code that is no longer standard
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Accessibility Checker)
- 3 violators were reported
-
navigations not distinctly named
- Why it matters: User cannot get help on how some of the document is organized
- Related WCAG standard: 1.3.6
- Reported by 1 rule engine (Accessibility Checker)
- 3 violators were reported
-
label empty
- Why it matters: User cannot get help on the topics of form items
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- 1 violator was reported
-
landmarks not distinctly named
- Why it matters: User cannot get help on how some of the document is organized
- Related WCAG standard: 1.3.6
- Reported by 1 rule engine (Axe)
- 1 violator was reported
-
tab-opening link action unstated
- Why it matters: Following a link opens a new window, surprising a user
- Related WCAG standard: 3.2.5
- Reported by 1 rule engine (Editoria11y)
- 1 violator was reported
-
DOCTYPE invalid
- Why it matters: Browser processes the document improperly
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- 1 violator was reported
-
meta invalid
- Why it matters: Document fails to include needed data
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- 2 violators were reported
-
CSS invalid
- Why it matters: Document cannot be properly displayed
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker API)
- 1 violator was reported
-
attribute obsolete
- Why it matters: Document includes obsolete code that the browser may fail to process
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker API)
- 6 violators were reported
-
code invalid
- Why it matters: Invalid code in the document may prevent a helper from working
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker API)
- 4 violators were reported
-
element closure invalid
- Why it matters: Document contains invalid code
- Related WCAG standard: 4.1.1
- Reported by 1 rule engine (Html Checker API)
- 1 violator was reported
-
box size absolute
- Why it matters: User cannot enlarge the content of an item for readability
- Related WCAG standard: 1.4.4
- Reported by 1 rule engine (QualWeb)
- 3 violators were reported
-
small targets too near to each other
- Why it matters: User cannot reliably choose an item to click or tap
- Related WCAG standard: 2.5.8
- Reported by 1 rule engine (Testaro)
- 16 violators were reported
-
element focusability and operability conflict
- Why it matters: Keyboard-only user cannot operate an item
- Related WCAG standard: 2.1.1
- Reported by 1 rule engine (Testaro)
- 11 violators were reported
-
hover indication poor
- Why it matters: User cannot explore the document reliably with a mouse
- Related WCAG standard: 3.3.2
- Reported by 1 rule engine (Testaro)
- 13 violators were reported
-
font small
- Why it matters: Text is difficult to read
- Related WCAG standard: 1.4
- Reported by 1 rule engine (WAVE)
- 6 violators were reported
Low priority: 8
-
heading structure illogical
- Why it matters: Helper misdescribes the document
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (ASLint + HTML CodeSniffer)
- 3 violators were reported
-
links named identically
- Why it matters: User cannot get help differentiating links
- Related WCAG standard: 2.4.4
- Reported by 2 rule engines (QualWeb + Testaro)
- 25 violators were reported
-
heading heads nothing
- Why it matters: Helper misdescribes the document
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Alfa)
- 1 violator was reported
-
line height low
- Why it matters: Text is difficult to read
- Related WCAG standard: 1.4.8
- Reported by 1 rule engine (Testaro)
- 144 violators were reported
-
link indication poor
- Why it matters: User cannot differentiate a link from plain text
- Related WCAG standard: 1.3.3
- Reported by 1 rule engine (Testaro)
- 54 violators were reported
-
page content moves spontaneously
- Why it matters: Motion-sensitive user may suffer harm
- Related WCAG standard: 2.2.2
- Reported by 1 rule engine (Testaro)
- 1 violator was reported
-
focus indication improvable
- Why it matters: Keyboard-only user cannot easily choose an item to operate
- Related WCAG standard: 2.4.7
- Reported by 1 rule engine (Testaro)
- 44 violators were reported
-
adjacent links not combined
- Why it matters: Keyboard-only user expends extra effort to skip a link
- Related WCAG standard: 2.4.4
- Reported by 1 rule engine (WAVE)
- 1 violator was reported
Lowest priority: 27
-
text contrast improvable
- Why it matters: Content is not easy to understand
- Related WCAG standard: 1.4.6
- Reported by 5 rule engines (Alfa + ASLint + Axe + HTML CodeSniffer + QualWeb)
- 110 violators were reported
-
tab-opening link action unstated?
- Why it matters: Following a link opens a new window, possibly surprising a user
- Related WCAG standard: 3.2.5
- Reported by 3 rule engines (ASLint + HTML CodeSniffer + Testaro)
- 9 violators were reported
-
role redundant
- Why it matters: Document includes unnecessary code
- Related WCAG standard: 4.1.2
- Reported by 2 rule engines (Accessibility Checker + Html Checker API)
- 2 violators were reported
-
aria attribute redundant
- Why it matters: Document includes unnecessary code
- Related WCAG standard: 4.1.2
- Reported by 2 rule engines (Accessibility Checker + Html Checker API)
- 1 violator was reported
-
content beyond landmarks
- Why it matters: User cannot get help on how some of the document is organized
- Related WCAG standard: 1.3.6
- Reported by 2 rule engines (Alfa + Axe)
- 2 violators were reported
-
all-capital text
- Why it matters: Text is difficult to read
- Related WCAG standard: 3.1.5
- Reported by 2 rule engines (Alfa + Testaro)
- 9 violators were reported
-
link name vague
- Why it matters: User may misunderstand what a link points to
- Related WCAG standard: 2.4.4
- Reported by 2 rule engines (ASLint + WAVE)
- 19 violators were reported
-
text contrast not testable
- Why it matters: Text may be difficult to read
- Related WCAG standard: 1.4.3
- Reported by 2 rule engines (HTML CodeSniffer + QualWeb)
- 61 violators were reported
-
target small
- Why it matters: User cannot reliably choose an item to click or tap
- Related WCAG standard: 2.5.5
- Reported by 1 rule engine (Alfa)
- 23 violators were reported
-
item makes testing inconclusive
- Why it matters: Item prevents a conclusive accessibility test
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Alfa)
- 1 violator was reported
-
button name not visible
- Why it matters: User cannot get help explaining a button
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (ASLint)
- 8 violators were reported
-
custom button keyboard-inoperable?
- Why it matters: Custom item may prevent a keyboard-only user from operating it
- Related WCAG standard: 2.1.1
- Reported by 1 rule engine (ASLint)
- 7 violators were reported
-
labeling risky
- Why it matters: User may misunderstand a form control
- Related WCAG standard: 3.3.2
- Reported by 1 rule engine (ASLint)
- 2 violators were reported
-
links dubiously share name
- Why it matters: User may be unable to get help differentiating links
- Related WCAG standard: 2.4.4
- Reported by 1 rule engine (Axe)
- 7 violators were reported
-
type redundant
- Why it matters: Document includes unnecessary code
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- 40 violators were reported
-
section heading missing
- Why it matters: User cannot understand the topic of a part of the document
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- 2 violators were reported
-
image dubiously marked decorative
- Why it matters: Helper ignores an image that is apparently informative
- Related WCAG standard: 1.1.1
- Reported by 1 rule engine (HTML CodeSniffer)
- 8 violators were reported
-
position sticky
- Why it matters: User may be unable to see needed content or may be forced to scroll in both dimensions
- Related WCAG standard: 1.4.10
- Reported by 1 rule engine (HTML CodeSniffer)
- 5 violators were reported
-
overflow hidden?
- Why it matters: User may be unable to enlarge the text for readability
- Related WCAG standard: 1.4.4
- Reported by 1 rule engine (QualWeb)
- 64 violators were reported
-
label location dubious
- Why it matters: User may fail to notice the explanation of an item in a form
- Related WCAG standard: 3.3.2
- Reported by 1 rule engine (QualWeb)
- 5 violators were reported
-
large visible-element count
- Why it matters: User cannot easily find items in the document
- Related WCAG standard: 2.4
- Reported by 1 rule engine (Testaro)
- 1 violator was reported
-
text distortion
- Why it matters: Text is difficult to read
- Related WCAG standard: 3.1.5
- Reported by 1 rule engine (Testaro)
- 25 violators were reported
-
role assigned instead of implicit
- Why it matters: User may misunderstand the purpose of an item
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Testaro)
- 15 violators were reported
-
inconsistent heading, link, or button styles
- Why it matters: User cannot easily distinguish items of different types
- Related WCAG standard: 3.2.4
- Reported by 1 rule engine (Testaro)
- 1 violator was reported
-
z-index not zero
- Why it matters: User cannot predict the effect of clicking
- Related WCAG standard: 1.4
- Reported by 1 rule engine (Testaro)
- 27 violators were reported
-
heading-like styles dubious
- Why it matters: User may be unable to understand the topic of a part of the document
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (WAVE)
- 5 violators were reported
-
noscript element not equivalent?
- Why it matters: User who has disabled JavaScript may be denied some content
- Related WCAG standard: 4.1
- Reported by 1 rule engine (WAVE)
- 1 violator was reported