Issues reported for OpenSecrets home
About the page
- URL: https://www.opensecrets.org/
- Tested 29 days ago on 2026-10-12 at 21:08 by job
261012T2043-ayi - Rule engines: 12 called, 8 able to test, violations reported by 8
- Results: 838 violations, 544 violators, 41 issues
- Download the full technical report (JSON)
History
- 34 days ago (oldest)
- 30 days ago
- 29 days ago (latest; this report)
Issues reported
Highest priority: 16
-
image not named
- Why it matters: User cannot get help to know what is in an image
- Priority: highest
- Related WCAG standard: 1.1.1
- Reported by 7 rule engines (Alfa + Axe + Editoria11y + Html Checker API + HTML CodeSniffer + QualWeb + SureA11y)
- Results: 36 violations, 9 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 6 rule engines (Alfa + Axe + Editoria11y + HTML CodeSniffer + QualWeb + SureA11y)
- Results: 10 violations, 4 violators
-
button not named
- Why it matters: User cannot get help explaining a button
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 4 rule engines (Alfa + Axe + HTML CodeSniffer + QualWeb)
- Results: 10 violations, 7 violators
-
contrast poor
- Why it matters: Content is difficult to understand
- Priority: highest
- Related WCAG standard: 1.4.3
- Reported by 4 rule engines (Alfa + Axe + HTML CodeSniffer + SureA11y)
- Results: 18 violations, 9 violators
-
attribute invalid
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 3 rule engines (Axe + Html Checker API + SureA11y)
- Results: 5 violations, 5 violators
-
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 3 rule engines (Editoria11y + HTML CodeSniffer + QualWeb)
- Results: 3 violations, 1 violator
-
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 (Html Checker API + HTML CodeSniffer + QualWeb)
- Results: 284 violations, 260 violators
-
focusable element hidden
- Why it matters: Keyboard-only user cannot navigate properly to the operable items
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 2 rule engines (Alfa + Axe)
- Results: 24 violations, 13 violators
-
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 1 rule engine (Alfa)
- Results: 3 violations, 3 violators
-
meta charset declared too late
- Why it matters: Browser may display incorrect text
- Priority: highest
- Related WCAG standard: 4.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: 70 violations, 70 violators
-
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: 2 violations, 2 violators
-
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: 32 violations, 32 violators
-
control not named
- Why it matters: User cannot get help on how to operate a form item
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 5 violations, 5 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: 4 violations, 4 violators
-
input not named
- Why it matters: User cannot get help on what information to enter in a form item
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 4 violations, 4 violators
High priority: 12
-
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 (Axe)
- Results: 6 violations, 6 violators
-
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: 1 violation, 1 violator
-
skip method missing or invalid
- Why it matters: Keyboard-only user cannot easily reach the specific content of the page
- Priority: high
- Related WCAG standard: 2.4.1
- Reported by 1 rule engine (Axe)
- Results: 1 violation, 1 violator
-
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: 1 violation, 1 violator
-
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
-
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: 60 violations, 1 violator
-
control child of link or button
- Why it matters: User cannot reliably choose an item to click or tap
- Priority: high
- Related WCAG standard: 2.5.5
- Reported by 1 rule engine (Html Checker API)
- Results: 17 violations, 17 violators
-
select not named
- Why it matters: User cannot get help on the topic of a list of options
- Priority: high
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 1 violation, 1 violator
-
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 1 rule engine (QualWeb)
- Results: 36 violations, 36 violators
-
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 (QualWeb)
- Results: 2 violations, 2 violators
-
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: 86 violations, 86 violators
-
element reloads or redirects
- Why it matters: Page change may surprise a user
- Priority: high
- Related WCAG standard: 2.2.1
- Reported by 1 rule engine (WAVE)
- Results: 1 violation, 1 violator
Low priority: 5
-
line height low
- Why it matters: Text is difficult to read
- Priority: low
- Related WCAG standard: 1.4.8
- Reported by 1 rule engine (Alfa)
- Results: 7 violations, 7 violators
-
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 (Html Checker API)
- Results: 4 violations, 4 violators
-
heading level skipped
- Why it matters: Helper misdescribes the page
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- Results: 1 violation, 1 violator
-
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: 3 violations, 2 violators
-
links not grouped as nav
- Why it matters: User cannot get help identifying links as a navigation tool
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (QualWeb)
- Results: 1 violation, 1 violator
Lowest priority: 8
-
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 + Axe + HTML CodeSniffer + QualWeb + SureA11y)
- Results: 72 violations, 32 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 2 rule engines (Alfa + Axe)
- Results: 3 violations, 3 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, 1 violator
-
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 (Axe)
- Results: 8 violations, 8 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 (QualWeb)
- Results: 5 violations, 5 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: 2 violations, 2 violators
-
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
-
element referenced by multiple labels
- Why it matters: User cannot get reliable help on the topics of form items
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (SureA11y)
- Results: 2 violations, 2 violators
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 OpenSecrets home web page. Describe them and propose a plan to resolve the genuine defects.