Issues reported for Portland State University Jordan Schnitzer Museum of Art home

About the page

URL: https://www.pdx.edu/museum-of-art/
Tested 192 days ago on 2026-05-03 at 05:17 by job 260503T0433-01z
Rule engines: 10 called, 9 able to test, violations reported by 9
Results: 609 violations, 287 violators, 64 issues
Download the full technical report (JSON)

History

This is the only available report about the page.

Request a retest

Issues reported

Highest priority: 15

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: 9 violations, 4 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 + Alfa + Axe)
- Results: 3 violations, 3 violators
Where was the issue found?
image 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 2 rule engines (ASLint + Editoria11y)
- Results: 4 violations, 4 violators
Where was the issue found?
internal link broken
- Why it matters: User cannot reach a promised page location
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (ASLint + HTML CodeSniffer)
- Results: 6 violations, 6 violators
Where was the issue found?
no role-required name
- Why it matters: User cannot get help understanding an item
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Accessibility Checker)
- Results: 1 violation, 1 violator
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?
aria attribute invalid
- Why it matters: Item behavior violates user expectations
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Axe)
- Results: 1 violation, 1 violator
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: 4 violations, 4 violators
Where was the issue found?
text in Private Use Area
- Why it matters: User cannot read all of the text
- Priority: highest
- Related WCAG standard: 3.1.3
- Reported by 1 rule engine (Html Checker API)
- Results: 1 violation, 1 violator
Where was the issue found?
sizes 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: 12 violations, 6 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: 11 violations, 11 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?
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: 3 violations, 3 violators
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: 6 violations, 6 violators
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?

High priority: 11

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 8 rule engines (Accessibility Checker + Alfa + ASLint + Axe + Editoria11y + Html Checker API + HTML CodeSniffer + QualWeb)
- Results: 8 violations, 2 violators
Where was the issue found?
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: 20 violations, 15 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: 1 violation, 1 violator
Where was the issue found?
role invalid
- Why it matters: User cannot get help on the nature of an item
- Priority: high
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Accessibility Checker)
- 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: 10 violations, 10 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 1 rule engine (Html Checker API)
- Results: 13 violations, 7 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?
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: 10 violations, 10 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: 2 violations, 2 violators
Where was the issue found?
element beyond display when focused
- Why it matters: Keyboard-only user cannot navigate properly to the operable items
- Priority: high
- Related WCAG standard: 1.4.10
- Reported by 1 rule engine (Testaro)
- Results: 2 violations, 2 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: 3 violations, 3 violators
Where was the issue found?

Low priority: 8

link indication poor
- Why it matters: User cannot differentiate a link from plain text
- Priority: low
- Related WCAG standard: 1.3.3
- Reported by 2 rule engines (Alfa + Testaro)
- Results: 16 violations, 16 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?
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: 21 violations, 10 violators
Where was the issue found?
link incomplete
- Why it matters: User may fail to reach a promised location
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 1 violation, 1 violator
Where was the issue found?
label types incompatible
- Why it matters: User cannot get reliable help on the topics of form items
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Testaro)
- Results: 2 violations, 2 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 1 rule engine (Testaro)
- Results: 4 violations, 4 violators
Where was the issue found?
duplicate attribute
- Why it matters: Browser processes the page improperly
- Priority: low
- Related WCAG standard: 4.1
- 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: 57 violations, 57 violators
Where was the issue found?

Lowest priority: 30

text contrast improvable
- Why it matters: Content is not easy to understand
- Priority: lowest
- Related WCAG standard: 1.4.6
- Reported by 4 rule engines (Alfa + ASLint + Axe + HTML CodeSniffer)
- Results: 118 violations, 65 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: 30 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?
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 2 rule engines (Alfa + Testaro)
- Results: 41 violations, 41 violators
Where was the issue found?
all-italic text
- Why it matters: Text is difficult to read
- Priority: lowest
- Related WCAG standard: 3.1.5
- Reported by 2 rule engines (ASLint + Testaro)
- Results: 2 violations, 2 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 2 rule engines (Editoria11y + HTML CodeSniffer)
- Results: 3 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 (Editoria11y + Testaro)
- Results: 34 violations, 33 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 1 rule engine (Accessibility Checker)
- Results: 1 violation, 1 violator
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: 8 violations, 4 violators
Where was the issue found?
false aria-hidden value risky
- Why it matters: User may be misled by erroneously hidden or revealed page content
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- Results: 2 violations, 2 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: 4 violations, 3 violators
Where was the issue found?
fieldset missing?
- Why it matters: User may be unable to get help recognizing a group of related form items
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- Results: 3 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: 6 violations, 6 violators
Where was the issue found?
tabindex redundant
- Why it matters: Revision risks interfering with navigation by a keyboard-only user
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- Results: 2 violations, 2 violators
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: 2 violations, 2 violators
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: 2 violations, 2 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: 34 violations, 34 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?
ordered list not coded as such?
- Why it matters: User may be unable to get help on whether a list is ordered
- Priority: lowest
- Related WCAG standard: 1.3.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: 1 violation, 1 violator
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 1 rule engine (HTML CodeSniffer)
- Results: 17 violations, 17 violators
Where was the issue found?
image link text suspect
- Why it matters: Keyboard-only user may misunderstand the effect of following a link
- Priority: lowest
- Related WCAG standard: 2.4.4
- Reported by 1 rule engine (QualWeb)
- Results: 1 violation, 1 violator
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: 4 violations, 4 violators
Where was the issue found?
container size unit not percentage
- Why it matters: User may be unable to see all of an item without scrolling in both dimensions
- Priority: lowest
- Related WCAG standard: 1.4.10
- Reported by 1 rule engine (QualWeb)
- Results: 1 violation, 1 violator
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?
double br use dubious
- Why it matters: User may be unable to get help to fully understand the text
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Testaro)
- Results: 1 violation, 1 violator
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: 10 violations, 10 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: 4 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: 18 violations, 18 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: 9 violations, 9 violators
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 Portland State University Jordan Schnitzer Museum of Art home web page. Describe them and propose a plan to resolve the genuine defects.

Issues reported for Portland State University Jordan Schnitzer Museum of Art home

About the page

History

Issues reported

ID not unique

contrast poor

image link not named

internal link broken

no role-required name

descendant missing

aria attribute invalid

attribute value invalid

text in Private Use Area

sizes attribute invalid

parent invalid

ancestor and descendant roles incompatible

attribute invalid

ID empty

Tab-focusable elements wrong

heading empty

visible label not in name

code obsolete

role invalid

tab-opening link action unstated

attribute obsolete

code invalid

box size absolute

element focusability and operability conflict

element beyond display when focused

hover indication poor

link indication poor

link href missing

links named identically

link incomplete

label types incompatible

line height low

duplicate attribute

focus indication improvable

text contrast improvable

tab-opening link action unstated?

role redundant

target small

all-italic text

heading-like styles dubious

all-capital text

content beyond landmarks

item makes testing inconclusive

false aria-hidden value risky

button name not visible

fieldset missing?

custom button keyboard-inoperable?

tabindex redundant

link destination not URL

image dubiously named

type redundant

image dubiously marked decorative

ordered list not coded as such?

position sticky

text contrast not testable

image link text suspect

label location dubious

container size unit not percentage

large visible-element count

double br use dubious

role assigned instead of implicit

inconsistent heading, link, or button styles

title attribute invalid

z-index not zero

What you can do

Do it yourself

Use artificial intelligence