Issues reported for Solver Collective home
About the page
- URL: https://solvercollective.com/
- Tested 115 days ago on 2026-07-19 at 00:05 by job
260719T0000-9a8 - Rule engines: 10 called, 10 able to test, violations reported by 10
- Results: 1833 violations, 400 violators, 70 issues
- Download the full technical report (JSON)
History
This is the only available report about the page.
Issues reported
Highest priority: 23
-
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 7 rule engines (Accessibility Checker + Alfa + Axe + Editoria11y + HTML CodeSniffer + QualWeb + WAVE)
- Results: 26 violations, 9 violators
-
iframe not named
- Why it matters: User cannot get help on the topic of an embedded page
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 6 rule engines (Accessibility Checker + Alfa + ASLint + Axe + HTML CodeSniffer + QualWeb)
- Results: 7 violations, 3 violators
-
contrast poor
- Why it matters: Content is difficult to understand
- Priority: highest
- Related WCAG standard: 1.4.3
- Reported by 5 rule engines (Accessibility Checker + Alfa + Axe + HTML CodeSniffer + WAVE)
- Results: 302 violations, 136 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 5 rule engines (ASLint + Editoria11y + HTML CodeSniffer + QualWeb + WAVE)
- Results: 20 violations, 12 violators
-
ID not unique
- Why it matters: User may be pointed to the wrong item
- Priority: highest
- Related WCAG standard: 4.1
- Reported by 4 rule engines (ASLint + Html Checker API + HTML CodeSniffer + QualWeb)
- Results: 7 violations, 3 violators
-
no video text alternative
- Why it matters: User cannot get help reading video content as text
- Priority: highest
- Related WCAG standard: 1.2.2
- Reported by 2 rule engines (Axe + QualWeb)
- Results: 7 violations, 1 violator
-
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 2 rule engines (HTML CodeSniffer + WAVE)
- Results: 5 violations, 3 violators
-
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 2 rule engines (QualWeb + WAVE)
- Results: 2 violations, 2 violators
-
internal link broken
- Why it matters: User cannot reach a promised page location
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- Results: 1 violation, 1 violator
-
audio or video caption track missing
- Why it matters: User cannot get help reading speech as text
- Priority: highest
- Related WCAG standard: 1.2.1
- Reported by 1 rule engine (ASLint)
- Results: 1 violation, 1 violator
-
video alternative missing
- Why it matters: User cannot get help consuming a video recording as text or speech
- Priority: highest
- Related WCAG standard: 1.2.1
- Reported by 1 rule engine (ASLint)
- 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: 1 violation, 1 violator
-
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 invalid
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- Results: 5 violations, 3 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: 2 violations, 2 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: 2 violations, 2 violators
-
text area 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: 1 violation, 1 violator
-
video transcript missing
- Why it matters: User cannot get help reading video content as text
- Priority: highest
- Related WCAG standard: 1.2.1
- Reported by 1 rule engine (QualWeb)
- Results: 1 violation, 1 violator
-
video audio track missing
- Why it matters: User cannot get help hearing video content as speech
- Priority: highest
- Related WCAG standard: 1.2.1
- Reported by 1 rule engine (QualWeb)
- Results: 1 violation, 1 violator
-
video audio description missing
- Why it matters: User cannot get help hearing video content as speech
- Priority: highest
- Related WCAG standard: 1.2.5
- Reported by 1 rule engine (QualWeb)
- Results: 1 violation, 1 violator
-
audio track missing
- Why it matters: User cannot get help reading speech as text
- Priority: highest
- Related WCAG standard: 1.2.1
- Reported by 1 rule engine (QualWeb)
- Results: 2 violations, 1 violator
-
autocomplete missing
- Why it matters: User cannot get help entering personal information in a form
- Priority: highest
- Related WCAG standard: 1.3.5
- Reported by 1 rule engine (Testaro)
- Results: 1 violation, 1 violator
-
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
High priority: 8
-
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
-
animation long or repetitive
- Why it matters: Motion-sensitive user may suffer harm
- Priority: high
- Related WCAG standard: 2.2.2
- Reported by 1 rule engine (ASLint)
- Results: 2 violations, 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: 15 violations, 15 violators
-
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: 1 violation, 1 violator
-
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: 14 violations, 14 violators
-
input has placeholder instead of name
- Why it matters: User cannot get reliable help on what information to enter in a form item
- Priority: high
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Testaro)
- Results: 2 violations, 2 violators
-
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: 1 violation, 1 violator
-
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: 1 violation, 1 violator
Low priority: 11
-
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: 15 violations, 6 violators
-
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: 18 violations, 9 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: 27 violations, 27 violators
-
line height absolute
- Why it matters: User cannot adjust the line height of text for readability
- Priority: low
- Related WCAG standard: 1.4.12
- Reported by 1 rule engine (Alfa)
- Results: 27 violations, 27 violators
-
autoplay
- Why it matters: Motion- or noise-sensitive user may suffer harm
- Priority: low
- Related WCAG standard: 1.4.2
- Reported by 1 rule engine (ASLint)
- 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, 3 violators
-
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: 5 violations, 5 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 1 rule engine (Testaro)
- Results: 6 violations, 6 violators
-
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
-
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: 49 violations, 49 violators
-
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: 4 violations, 4 violators
Lowest priority: 28
-
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: 375 violations, 171 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: 233 violations, 122 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: 45 violations, 25 violators
-
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
-
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: 54 violations, 54 violators
-
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: 133 violations, 105 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: 25 violations, 9 violators
-
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: 64 violations, 13 violators
-
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: 3 violations, 1 violator
-
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, 1 violator
-
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: 3 violations, 2 violators
-
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: 1 violation, 1 violator
-
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: 28 violations, 28 violators
-
role redundant
- Why it matters: Page includes unnecessary code
- Priority: lowest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Html Checker API)
- Results: 1 violation, 1 violator
-
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: 42 violations, 42 violators
-
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: 5 violations, 5 violators
-
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: 3 violations, 3 violators
-
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: 150 violations, 150 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: 13 violations, 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
-
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: 21 violations, 21 violators
-
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: 6 violations, 6 violators
-
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
-
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: 2 violations, 1 violator
-
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: 16 violations, 16 violators
-
nearby images have same alt
- Why it matters: User cannot get help differentiating two adjacent images
- Priority: lowest
- Related WCAG standard: 1.1.1
- Reported by 1 rule engine (WAVE)
- Results: 2 violations, 2 violators
-
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
-
audio or video alternatives missing?
- Why it matters: User may be unable to get help reading video content as text
- Priority: lowest
- Related WCAG standard: 1.2.2
- 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 Solver Collective home web page. Describe them and propose a plan to resolve the genuine defects.