Kilotest: Issues reported for Disability Rights Oregon

About the Disability Rights Oregon page

• URL: https://www.droregon.org/
• Tested by job o81 on 2026-04-03 at 12:00

Issues reported

Summary

11 tools reported issues (Accessibility Checker + Alfa + ASLint + Axe + Editoria11y + Html Checker API + HTML CodeSniffer + QualWeb + Testaro + WallyAX + WAVE)

67 issues were reported (11 highest, 11 high, 11 low, 34 lowest priority)

Details

Highest priority

ID not unique

• Why it matters: User may be pointed to the wrong item
• Related WCAG standard: 4.1.1
• Reported by 6 tools (Alfa + ASLint + Axe + Html Checker API + HTML CodeSniffer + WallyAX)
• Where was the issue found?

link not named

• Why it matters: User cannot get help understanding what a link points to
• Related WCAG standard: 2.4.4
• Reported by 4 tools (Accessibility Checker + Alfa + Axe + QualWeb)
• Where was the issue found?

contrast poor

• Why it matters: Content is difficult to understand
• Related WCAG standard: 1.4.3
• Reported by 4 tools (Axe + HTML CodeSniffer + WallyAX + WAVE)
• Where was the issue found?

svg image not named

• Why it matters: User cannot get help understanding an image
• Related WCAG standard: 1.1.1
• Reported by 2 tools (Accessibility Checker + ASLint)
• Where was the issue found?

image link not named

• Why it matters: User cannot get help understanding what a link points to
• Related WCAG standard: 2.4.4
• Reported by 2 tools (QualWeb + WAVE)
• Where was the issue found?

attribute invalid

• Why it matters: Item behaves improperly
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Html Checker API)
• Where was the issue found?

attribute value invalid

• Why it matters: Item behaves improperly
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Html Checker API)
• Where was the issue found?

parent invalid

• Why it matters: User cannot properly operate an item
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Html Checker API)
• Where was the issue found?

attribute missing

• Why it matters: Item behaves improperly
• Related WCAG standard: 4.1.2
• Reported by 1 tool (Html Checker API)
• Where was the issue found?

target empty

• Why it matters: Item is displayed improperly
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Html Checker API)
• Where was the issue found?

focus indication poor

• Why it matters: Keyboard-only user cannot choose an item to operate
• Related WCAG standard: 2.4.7
• Reported by 1 tool (Testaro)
• Where was the issue found?

High priority

font small

• Why it matters: Text is difficult to read
• Related WCAG standard: 1.4
• Reported by 3 tools (ASLint + Testaro + WAVE)
• Where was the issue found?

code obsolete

• Why it matters: Document contains code that is no longer standard
• Related WCAG standard: 4.1
• Reported by 1 tool (Accessibility Checker)
• Where was the issue found?

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 tool (Accessibility Checker)
• Where was the issue found?

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 tool (Axe)
• Where was the issue found?

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 tool (Editoria11y)
• Where was the issue found?

meta invalid

• Why it matters: Document fails to include needed data
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Html Checker API)
• Where was the issue found?

CSS invalid

• Why it matters: Document cannot be properly displayed
• Related WCAG standard: 4.1
• Reported by 1 tool (Html Checker API)
• Where was the issue found?

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 tool (QualWeb)
• Where was the issue found?

input has placeholder instead of name

• Why it matters: User cannot get reliable help on what information to enter in a form item
• Related WCAG standard: 4.1.2
• Reported by 1 tool (Testaro)
• Where was the issue found?

element beyond display when focused

• Why it matters: Keyboard-only user cannot navigate properly to the operable items
• Related WCAG standard: 1.4.10
• Reported by 1 tool (Testaro)
• Where was the issue found?

hover indication poor

• Why it matters: User cannot explore the document reliably with a mouse
• Related WCAG standard: 3.3.2
• Reported by 1 tool (Testaro)
• Where was the issue found?

Low priority

heading level skipped

• Why it matters: Helper misdescribes the document
• Related WCAG standard: 1.3.1
• Reported by 5 tools (Alfa + Axe + Editoria11y + Html Checker API + WAVE)
• Where was the issue found?

heading structure illogical

• Why it matters: Helper misdescribes the document
• Related WCAG standard: 1.3.1
• Reported by 2 tools (ASLint + HTML CodeSniffer)
• Where was the issue found?

link href missing

• Why it matters: Helper cannot properly explain a link to a user
• Related WCAG standard: 1.3.1
• Reported by 2 tools (ASLint + Testaro)
• Where was the issue found?

links named identically

• Why it matters: User cannot get help differentiating links
• Related WCAG standard: 2.4.4
• Reported by 2 tools (QualWeb + Testaro)
• Where was the issue found?

not exactly 1 h1 heading

• Why it matters: User cannot understand the topic of the document
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Html Checker API)
• Where was the issue found?

line height low

• Why it matters: Text is difficult to read
• Related WCAG standard: 1.4.8
• Reported by 1 tool (Testaro)
• Where was the issue found?

link indication poor

• Why it matters: User cannot differentiate a link from plain text
• Related WCAG standard: 1.3.3
• Reported by 1 tool (Testaro)
• Where was the issue found?

duplicate attribute

• Why it matters: Browser processes the document improperly
• Related WCAG standard: 4.1.1
• Reported by 1 tool (Testaro)
• Where was the issue found?

heading names repeated

• Why it matters: User cannot differentiate parts of the document
• Related WCAG standard: 1.3.1
• Reported by 1 tool (WallyAX)
• Where was the issue found?

image alt long

• Why it matters: Helper gives a user an overly verbose explanation of an image
• Related WCAG standard: 1.1.1
• Reported by 1 tool (WAVE)
• Where was the issue found?

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 tool (WAVE)
• Where was the issue found?

Lowest priority

text contrast not testable

• Why it matters: Text may be difficult to read
• Related WCAG standard: 1.4.3
• Reported by 3 tools (Alfa + HTML CodeSniffer + QualWeb)
• Where was the issue found?

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 tools (ASLint + HTML CodeSniffer + Testaro)
• Where was the issue found?

text contrast improvable

• Why it matters: Content is not easy to understand
• Related WCAG standard: 1.4.6
• Reported by 3 tools (HTML CodeSniffer + QualWeb + WallyAX)
• Where was the issue found?

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 tools (Accessibility Checker + Alfa)
• Where was the issue found?

role redundant

• Why it matters: Document includes unnecessary code
• Related WCAG standard: 4.1.2
• Reported by 2 tools (Accessibility Checker + Html Checker API)
• Where was the issue found?

target small

• Why it matters: User cannot reliably choose an item to click or tap
• Related WCAG standard: 2.5.5
• Reported by 2 tools (Alfa + Testaro)
• Where was the issue found?

hr misused

• Why it matters: User cannot get help on the nature of segments of the document
• Related WCAG standard: 1.3.1
• Reported by 2 tools (ASLint + Testaro)
• 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
• Related WCAG standard: 1.4.10
• Reported by 2 tools (HTML CodeSniffer + WallyAX)
• Where was the issue found?

button name not visible

• Why it matters: User cannot get help explaining a button
• Related WCAG standard: 4.1.2
• Reported by 1 tool (ASLint)
• Where was the issue found?

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 tool (ASLint)
• Where was the issue found?

labeling risky

• Why it matters: User may misunderstand a form control
• Related WCAG standard: 3.3.2
• Reported by 1 tool (ASLint)
• Where was the issue found?

tabindex redundant

• Why it matters: Revision risks interfering with navigation by a keyboard-only user
• Related WCAG standard: 1.3.1
• Reported by 1 tool (ASLint)
• Where was the issue found?

image dubiously named

• Why it matters: Helper may describe an image inadequately
• Related WCAG standard: 1.1.1
• Reported by 1 tool (ASLint)
• Where was the issue found?

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 tool (Axe)
• Where was the issue found?

type redundant

• Why it matters: Document includes unnecessary code
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Html Checker API)
• Where was the issue found?

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 tool (Html Checker API)
• Where was the issue found?

article 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 tool (Html Checker API)
• Where was the issue found?

SVG version not 1.1

• Why it matters: Item prevents testing image for accessibility
• Related WCAG standard: 4.1
• Reported by 1 tool (Html Checker API)
• Where was the issue found?

image dubiously marked decorative

• Why it matters: Helper ignores an image that is apparently informative
• Related WCAG standard: 1.1.1
• Reported by 1 tool (HTML CodeSniffer)
• Where was the issue found?

nav links better as list?

• Why it matters: User cannot get help recognizing a list of navigation links
• Related WCAG standard: 1.3.1
• Reported by 1 tool (HTML CodeSniffer)
• Where was the issue found?

overflow hidden?

• Why it matters: User may be unable to enlarge the text for readability
• Related WCAG standard: 1.4.4
• Reported by 1 tool (QualWeb)
• Where was the issue found?

image link text suspect

• Why it matters: Keyboard-only user may misunderstand the effect of following a link
• Related WCAG standard: 2.4.4
• Reported by 1 tool (QualWeb)
• Where was the issue found?

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 tool (QualWeb)
• Where was the issue found?

all-capital text

• Why it matters: Text is difficult to read
• Related WCAG standard: 3.1.5
• Reported by 1 tool (Testaro)
• Where was the issue found?

large visible-element count

• Why it matters: User cannot easily find items in the document
• Related WCAG standard: 2.4
• Reported by 1 tool (Testaro)
• Where was the issue found?

text distortion

• Why it matters: Text is difficult to read
• Related WCAG standard: 3.1.5
• Reported by 1 tool (Testaro)
• Where was the issue found?

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 tool (Testaro)
• Where was the issue found?

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 tool (Testaro)
• Where was the issue found?

z-index not zero

• Why it matters: User cannot predict the effect of clicking
• Related WCAG standard: 1.4
• Reported by 1 tool (Testaro)
• Where was the issue found?

hovering changes content

• Why it matters: User cannot explore the document reliably with a mouse
• Related WCAG standard: 3.2.5
• Reported by 1 tool (Testaro)
• Where was the issue found?

event not keyboard-triggerable?

• Why it matters: Keyboard-only user may be unable to perform an action
• Related WCAG standard: 2.1.1
• Reported by 1 tool (WallyAX)
• Where was the issue found?

image name redundant

• Why it matters: Helper repeats the explanation of an image
• Related WCAG standard: 1.1.1
• Reported by 1 tool (WAVE)
• 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 document
• Related WCAG standard: 1.3.1
• Reported by 1 tool (WAVE)
• Where was the issue found?

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 tool (WAVE)
• Where was the issue found?