Issues reported for University of Oregon home

About the page

URL: https://www.uoregon.edu/
Tested 90 days ago on 2026-08-12 at 21:29 by job 260812T2127-8n6
Rule engines: 10 called, 10 able to test, violations reported by 9
Results: 1488 violations, 685 violators, 72 issues
Download the full technical report (JSON)

History

This is the only available report about the page.

Request a retest

Issues reported

Highest priority: 17

contrast poor
- Why it matters: Content is difficult to understand
- Priority: highest
- Related WCAG standard: 1.4.3
- Reported by 3 rule engines (Alfa + Axe + HTML CodeSniffer)
- Results: 89 violations, 82 violators
Where was the issue found?
ID not unique
- Why it matters: User may be pointed to the wrong item
- Priority: highest
- Related WCAG standard: 4.1
- Reported by 3 rule engines (ASLint + Html Checker API + HTML CodeSniffer)
- Results: 70 violations, 56 violators
Where was the issue found?
region not named
- Why it matters: User cannot get help surveying the parts of the page
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 2 rule engines (Accessibility Checker + Alfa)
- Results: 2 violations, 2 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 2 rule engines (Alfa + QualWeb)
- Results: 7 violations, 7 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 2 rule engines (HTML CodeSniffer + WAVE)
- Results: 6 violations, 3 violators
Where was the issue found?
parent 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: 4 violations, 1 violator
Where was the issue found?
dialog not named
- Why it matters: User cannot get help explaining a pop-up window
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (ASLint)
- Results: 1 violation, 1 violator
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: 42 violations, 42 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: 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: 1 violation, 1 violator
Where was the issue found?
attribute invalid
- Why it matters: Item behaves improperly
- 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?
presentation element has child
- Why it matters: Keyboard-only user cannot reach an item intended to be reachable
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 3 violations, 3 violators
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?
link element invalid
- 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?
link not named
- Why it matters: User cannot get help understanding what a link points to
- Priority: highest
- Related WCAG standard: 2.4.4
- Reported by 1 rule engine (HTML CodeSniffer)
- 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?
menu items missing
- Why it matters: User cannot reach promised menu items
- 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: 26 violations, 14 violators
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 2 rule engines (ASLint + Html Checker API)
- Results: 11 violations, 7 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 2 rule engines (ASLint + WAVE)
- Results: 4 violations, 4 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: 2 violations, 2 violators
Where was the issue found?
contentinfos 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: 2 violations, 2 violators
Where was the issue found?
negative text-indent
- Why it matters: Helper may hide content from a user
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (ASLint)
- Results: 9 violations, 9 violators
Where was the issue found?
form submission button missing
- Why it matters: User cannot easily submit a form
- Priority: high
- Related WCAG standard: 3.2.2
- Reported by 1 rule engine (ASLint)
- Results: 1 violation, 1 violator
Where was the issue found?
table headers missing
- Why it matters: User cannot get help on relationships in a table
- Priority: high
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- Results: 3 violations, 3 violators
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: 2 violations, 2 violators
Where was the issue found?
CSS invalid
- Why it matters: Page cannot be properly displayed
- 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?
invalid CSS at-rule
- Why it matters: Page cannot be properly displayed in particular contexts
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker API)
- Results: 2 violations, 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?
link element href or image srcset missing
- Why it matters: User cannot reach a promised location
- 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?
link element href missing
- Why it matters: User cannot reach a promised location
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 1 violation, 1 violator
Where was the issue found?
table not marked as such
- Why it matters: Helper misinforms a user about whether items are cells of a table
- Priority: high
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (QualWeb)
- Results: 3 violations, 3 violators
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: 40 violations, 40 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: 19 violations, 19 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: 6 violations, 6 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: 16 violations, 16 violators
Where was the issue found?

Low priority: 11

table misused
- Why it matters: Helper misinforms a user about whether items are cells of a table
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 3 rule engines (QualWeb + Testaro + WAVE)
- Results: 12 violations, 6 violators
Where was the issue found?
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: 170 violations, 163 violators
Where was the issue found?
link href missing
- Why it matters: Helper cannot properly explain a link to a user
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (ASLint + Testaro)
- Results: 2 violations, 2 violators
Where was the issue found?
multiple contentinfos
- Why it matters: User cannot get help on how some of the page is organized
- Priority: low
- Related WCAG standard: 1.3.6
- Reported by 2 rule engines (Axe + QualWeb)
- Results: 3 violations, 2 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: 47 violations, 30 violators
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?
cell headers ambiguous?
- Why it matters: User may be unable to get help on relationships in a table
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (QualWeb)
- Results: 6 violations, 3 violators
Where was the issue found?
table embedded in table
- Why it matters: User cannot get help on relationships in a table
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (QualWeb)
- Results: 1 violation, 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: 5 violations, 5 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?
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: 13 violations, 13 violators
Where was the issue found?

Lowest priority: 25

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: 447 violations, 317 violators
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 (Accessibility Checker + Alfa)
- Results: 20 violations, 20 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: 6 violations, 3 violators
Where was the issue found?
table caption missing or empty
- Why it matters: User cannot get help on the topic of a table
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (ASLint + QualWeb)
- Results: 6 violations, 6 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: 40 violations, 39 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: 59 violations, 57 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: 40 violations, 17 violators
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: 5 violations, 3 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: 1 violation, 1 violator
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: 1 violation, 1 violator
Where was the issue found?
link destination not URL
- Why it matters: Helper cannot properly explain a link to a user
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- Results: 1 violation, 1 violator
Where was the issue found?
image dubiously named
- Why it matters: Helper may describe an image inadequately
- Priority: lowest
- Related WCAG standard: 1.1.1
- Reported by 1 rule engine (ASLint)
- Results: 6 violations, 6 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: 10 violations, 10 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: 1 violation, 1 violator
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: 6 violations, 6 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: 100 violations, 100 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 1 rule engine (Testaro)
- Results: 11 violations, 11 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: 11 violations, 11 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: 14 violations, 14 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?
title attribute invalid
- Why it matters: User gets too little, too much, or repeated help explaining an item
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Testaro)
- Results: 5 violations, 5 violators
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: 36 violations, 36 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 University of Oregon home web page. Describe them and propose a plan to resolve the genuine defects.

Issues reported for University of Oregon home

About the page

History

Issues reported

contrast poor

ID not unique

region not named

descendant missing

button not named

parent missing

dialog not named

parent invalid

attribute value invalid

ID empty

attribute invalid

presentation element has child

link element misplaced

link element invalid

link not named

Tab-focusable elements wrong

menu items missing

visible label not in name

attribute obsolete

font small

navigations not distinctly named

contentinfos not distinctly named

negative text-indent

form submission button missing

table headers missing

landmarks not distinctly named

CSS invalid

invalid CSS at-rule

CSS property does not exist

link element href or image srcset missing

link element href missing

table not marked as such

box size absolute

small targets too near to each other

element focusability and operability conflict

hover indication poor

table misused

line height low

link href missing

multiple contentinfos

links named identically

heading structure illogical

cell headers ambiguous?

table embedded in table

link indication poor

page content moves spontaneously

adjacent links not combined

text contrast improvable

content beyond landmarks

role redundant

table caption missing or empty

text contrast not testable

target small

item makes testing inconclusive

button name not visible

custom button keyboard-inoperable?

labeling risky

link destination not URL

image dubiously named

links dubiously share name

type redundant

image dubiously marked decorative

position sticky

overflow hidden?

all-capital text

large visible-element count

text distortion

role assigned instead of implicit

inconsistent heading, link, or button styles

title attribute invalid

z-index not zero

noscript element not equivalent?

What you can do

Do it yourself

Use artificial intelligence