Kilotest: Issues reported for Synchronicity Earth USA

About the tests

How to deal with the issues

Do it yourself

Explore the issues below in as much detail as you want. Decide which ones are actual defects. Plan and implement corrections.

Or use AI

Make Kilotest available to your AI assistant. There are step-by-step instructions for this.

After that, you can ask:

Kilotest reports defects on the Synchronicity Earth USA web page. Summarize them and propose a plan to resolve the genuine ones.

URL: https://www.synchronicityearthusa.org/
Tested 2 days ago on 2026-10-07 at 23:21 by job 261007T2305-mxz
Summary of results:
- Rule engines:
  - Called: 12
  - Were able to test: 12
  - Reported any rule violations: 12
- Violations: 1476
- Violators: 529
- Issues: 62
Download the full technical report (JSON)

History

This is the only report about the page.

Should Kilotest retest the page?

Issues reported

Highest priority: 11

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 10 rule engines (Accessibility Checker + Alfa + Axe + Editoria11y + Html Checker + HTML CodeSniffer + Pour + QualWeb + SureA11y + WAVE)
- Violations: 21
- Violators: 5
- 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 5 rule engines (Alfa + Axe + HTML CodeSniffer + Pour + WAVE)
- Violations: 22
- Violators: 15
- Where was the issue found?
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 3 rule engines (Accessibility Checker + ASLint + HTML CodeSniffer)
- Violations: 6
- Violators: 5
- Where was the issue found?
requirement invalid
- Why it matters: User may fail to get help determining whether a form item must be completed
- Priority: highest
- Related WCAG standard: 1.3.5
- Reported by 1 rule engine (ASLint)
- Violations: 1
- Violators: 1
- 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)
- Violations: 33
- Violators: 33
- Where was the issue found?
attribute missing
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Html Checker)
- Violations: 27
- Violators: 27
- 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)
- Violations: 24
- Violators: 17
- 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)
- Violations: 16
- Violators: 16
- 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)
- Violations: 6
- Violators: 3
- Where was the issue found?
link element misplaced
- Why it matters: Page fails to get a needed external resource
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (HTML CodeSniffer)
- Violations: 3
- Violators: 3
- Where was the issue found?
button not named
- Why it matters: User cannot get help explaining a button
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (HTML CodeSniffer)
- Violations: 1
- Violators: 1
- Where was the issue found?

High priority: 16

form submission button missing
- Why it matters: User cannot easily submit a form
- Priority: high
- Related WCAG standard: 3.2.2
- Reported by 3 rule engines (ASLint + HTML CodeSniffer + QualWeb)
- Violations: 3
- Violators: 2
- Where was the issue found?
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 2 rule engines (ASLint + WAVE)
- Violations: 14
- Violators: 14
- 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)
- Violations: 3
- Violators: 3
- 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 1 rule engine (Accessibility Checker)
- Violations: 1
- Violators: 1
- Where was the issue found?
contentinfos 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 (Accessibility Checker)
- Violations: 2
- Violators: 2
- Where was the issue found?
h1 not 1st heading
- Why it matters: User cannot understand the topic of the page
- Priority: high
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Alfa)
- Violations: 1
- Violators: 1
- 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 (ASLint)
- Violations: 3
- Violators: 3
- Where was the issue found?
CSS invalid
- Why it matters: Page cannot be properly displayed
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker)
- Violations: 123
- Violators: 2
- Where was the issue found?
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)
- Violations: 1
- Violators: 1
- 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)
- Violations: 92
- Violators: 90
- Where was the issue found?
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)
- Violations: 428
- Violators: 1
- Where was the issue found?
invalid character
- Why it matters: Invalid character makes the page behave incorrectly
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker)
- Violations: 1
- Violators: 1
- Where was the issue found?
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 (Pour)
- Violations: 2
- Violators: 2
- Where was the issue found?
font small
- Why it matters: Text is difficult to read
- Priority: high
- Related WCAG standard: 1.4
- Reported by 1 rule engine (Testaro)
- Violations: 1
- Violators: 1
- 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
- Priority: high
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Testaro)
- Violations: 1
- Violators: 1
- 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)
- Violations: 5
- Violators: 5
- Where was the issue found?

Low priority: 15

not exactly 1 h1 heading
- Why it matters: User cannot understand the topic of the page
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 3 rule engines (ASLint + Axe + Pour)
- Violations: 3
- Violators: 1
- Where was the issue found?
multiple contentinfos
- Why it matters: User cannot get help on how some of the page is organized
- Priority: low
- Related WCAG standard: 1.3.6
- Reported by 2 rule engines (Accessibility Checker + QualWeb)
- Violations: 4
- Violators: 2
- Where was the issue found?
heading structure illogical
- Why it matters: Helper misdescribes the page
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (ASLint + HTML CodeSniffer)
- Violations: 3
- Violators: 2
- Where was the issue found?
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)
- Violations: 9
- Violators: 6
- Where was the issue found?
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)
- Violations: 1
- Violators: 1
- Where was the issue found?
main child of landmark
- Why it matters: User cannot get help on how some of the page is organized
- Priority: low
- Related WCAG standard: 1.3.6
- Reported by 1 rule engine (Pour)
- Violations: 2
- Violators: 2
- Where was the issue found?
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 (QualWeb)
- Violations: 10
- Violators: 10
- Where was the issue found?
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)
- Violations: 1
- Violators: 1
- Where was the issue found?
aside child of landmark
- Why it matters: User cannot get help on how some of the page is organized
- Priority: low
- Related WCAG standard: 1.3.6
- Reported by 1 rule engine (QualWeb)
- Violations: 2
- Violators: 2
- Where was the issue found?
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 (SureA11y)
- Violations: 1
- Violators: 1
- 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)
- Violations: 1
- Violators: 1
- 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)
- Violations: 48
- Violators: 48
- 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 1 rule engine (Testaro)
- Violations: 1
- Violators: 1
- Where was the issue found?
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)
- Violations: 1
- Violators: 1
- 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)
- Violations: 32
- Violators: 32
- Where was the issue found?

Lowest priority: 20

text contrast improvable
- Why it matters: Content is not easy to understand
- Priority: lowest
- Related WCAG standard: 1.4.6
- Reported by 7 rule engines (Alfa + ASLint + Axe + HTML CodeSniffer + Pour + QualWeb + SureA11y)
- Violations: 250
- Violators: 107
- 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 3 rule engines (Alfa + Axe + Pour)
- Violations: 3
- Violators: 3
- 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 + Pour + Testaro)
- Violations: 30
- Violators: 24
- 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 + Pour)
- Violations: 24
- Violators: 24
- 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 (Alfa + Testaro)
- Violations: 4
- Violators: 3
- 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)
- Violations: 2
- Violators: 2
- Where was the issue found?
title attribute empty
- Why it matters: Hovering does not get the promised explanation of an item
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- Violations: 4
- Violators: 1
- Where was the issue found?
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)
- Violations: 1
- Violators: 1
- Where was the issue found?
no default option
- Why it matters: User may risk erroneously submitting a form
- Priority: lowest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (ASLint)
- Violations: 1
- Violators: 1
- 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)
- Violations: 25
- Violators: 16
- Where was the issue found?
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 (ASLint)
- Violations: 1
- Violators: 1
- Where was the issue found?
footer child of landmark
- 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 (Axe)
- Violations: 2
- Violators: 2
- 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)
- Violations: 1
- Violators: 1
- 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)
- Violations: 14
- Violators: 3
- 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)
- Violations: 1
- Violators: 1
- Where was the issue found?
text distortion
- Why it matters: Text is difficult to read
- Priority: lowest
- Related WCAG standard: 3.1.5
- Reported by 1 rule engine (Testaro)
- Violations: 6
- Violators: 6
- 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)
- Violations: 14
- Violators: 14
- 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)
- Violations: 4
- Violators: 1
- 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)
- Violations: 7
- Violators: 7
- 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)
- Violations: 122
- Violators: 122
- Where was the issue found?

Kilotest: Issues reported for Synchronicity Earth USA

About the tests

Do it yourself

Or use AI

History

Issues reported

image not named

contrast poor

iframe not named

requirement invalid

parent invalid

attribute missing

attribute invalid

sizes attribute invalid

attribute value invalid

link element misplaced

button not named

form submission button missing

heading empty

code obsolete

visible label not in name

contentinfos not distinctly named

h1 not 1st heading

attribute obsolete

CSS invalid

CSS property does not exist

code invalid

invalid CSS at-rule

invalid character

landmarks not distinctly named

font small

input has placeholder instead of name

element focusability and operability conflict

not exactly 1 h1 heading

multiple contentinfos

heading structure illogical

font size absolute

line height absolute

main child of landmark

adjacent links not combined

links not grouped as nav

aside child of landmark

link indication poor

label types incompatible

line height low

links named identically

page content moves spontaneously

focus indication improvable

text contrast improvable

content beyond landmarks

tab-opening link action unstated?

target small

all-italic text

button name not visible

title attribute empty

labeling risky

no default option

link destination not URL

image name redundant

footer child of landmark

image link text suspect

container size unit not percentage

large visible-element count

text distortion

role assigned instead of implicit

inconsistent heading, link, or button styles

title attribute invalid

z-index not zero