Issues reported for City of Portland May 1st update from Council Vice President Clark
About the page
- URL: https://content.govdelivery.com/accounts/ORPORTLAND_ENT/bulletins/41547e4
- Tested 188 days ago on 2026-05-06 at 19:31 by job
260506T1911-9bg - Rule engines: 10 called, 10 able to test, violations reported by 10
- Results: 878 violations, 147 violators, 50 issues
- Download the full technical report (JSON)
History
This is the only available report about the page.
Issues reported
Highest priority: 6
-
contrast poor
- Why it matters: Content is difficult to understand
- Priority: highest
- Related WCAG standard: 1.4.3
- Reported by 1 rule engine (Axe)
- Results: 1 violation, 1 violator
-
attribute missing
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Html Checker API)
- Results: 1 violation, 1 violator
-
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
-
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: 3 violations, 3 violators
-
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: 8 violations, 8 violators
-
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
High priority: 9
-
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 4 rule engines (ASLint + Html Checker API + HTML CodeSniffer + Testaro)
- Results: 176 violations, 70 violators
-
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 3 rule engines (Accessibility Checker + ASLint + Editoria11y)
- Results: 32 violations, 26 violators
-
font small
- Why it matters: Text is difficult to read
- Priority: high
- Related WCAG standard: 1.4
- Reported by 2 rule engines (ASLint + Testaro)
- Results: 9 violations, 9 violators
-
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: 29 violations, 29 violators
-
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
-
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
-
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: 60 violations, 30 violators
-
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: 17 violations, 17 violators
-
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
Low priority: 12
-
heading level skipped
- Why it matters: Helper misdescribes the page
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 5 rule engines (Alfa + Axe + Editoria11y + Html Checker API + WAVE)
- Results: 5 violations, 2 violators
-
link indication poor
- Why it matters: User cannot differentiate a link from plain text
- Priority: low
- Related WCAG standard: 1.3.3
- Reported by 3 rule engines (Alfa + Axe + Testaro)
- Results: 58 violations, 39 violators
-
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 3 rule engines (ASLint + Html Checker API + Testaro)
- Results: 3 violations, 2 violators
-
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: 68 violations, 34 violators
-
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: 65 violations, 11 violators
-
semantic properties represented with styles
- Why it matters: User cannot get help to fully understand the text
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (HTML CodeSniffer + Testaro)
- Results: 3 violations, 2 violators
-
font size absolute
- Why it matters: User cannot adjust the text size for readability
- Priority: low
- Related WCAG standard: 1.4.4
- Reported by 1 rule engine (Alfa)
- Results: 58 violations, 4 violators
-
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: 1 violation, 1 violator
-
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: 29 violations, 17 violators
-
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: 15 violations, 15 violators
-
links named identically
- Why it matters: User cannot get help differentiating links
- Priority: low
- Related WCAG standard: 2.4.4
- Reported by 1 rule engine (Testaro)
- Results: 1 violation, 1 violator
-
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: 36 violations, 36 violators
Lowest priority: 23
-
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: 43 violations, 17 violators
-
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 3 rule engines (Accessibility Checker + Alfa + Axe)
- Results: 5 violations, 4 violators
-
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: 41 violations, 21 violators
-
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: 2 violations, 1 violator
-
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: 34 violations, 34 violators
-
image dubiously named
- Why it matters: Helper may describe an image inadequately
- Priority: lowest
- Related WCAG standard: 1.1.1
- Reported by 2 rule engines (ASLint + WAVE)
- Results: 2 violations, 2 violators
-
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: 2 violations, 2 violators
-
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: 1 violation, 1 violator
-
heading located in table
- Why it matters: Complex relationships in a table may confuse a user
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Editoria11y)
- Results: 4 violations, 2 violators
-
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: 2 violations, 2 violators
-
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 (HTML CodeSniffer)
- Results: 2 violations, 2 violators
-
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: 18 violations, 18 violators
-
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: 1 violation, 1 violator
-
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: 2 violations, 2 violators
-
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: 5 violations, 5 violators
-
all-italic text
- Why it matters: Text is difficult to read
- Priority: lowest
- Related WCAG standard: 3.1.5
- Reported by 1 rule engine (Testaro)
- Results: 1 violation, 1 violator
-
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
-
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: 9 violations, 9 violators
-
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: 3 violations, 1 violator
-
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: 3 violations, 3 violators
-
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: 1 violation, 1 violator
-
image name redundant
- Why it matters: Helper repeats the explanation of an image
- Priority: lowest
- Related WCAG standard: 1.1.1
- Reported by 1 rule engine (WAVE)
- Results: 1 violation, 1 violator
-
title attribute redundant
- Why it matters: Helper repeats the explanation of an item
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (WAVE)
- Results: 1 violation, 1 violator
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 City of Portland May 1st update from Council Vice President Clark web page. Describe them and propose a plan to resolve the genuine defects.