Kilotest: Issues reported for DemocracyNext

About the DemocracyNext page

• URL: https://www.demnext.org/
• Tested by job gb2 on 2026-04-10 at 16:47
• Page prevented testing by 1 tool (WAVE)

Issues reported

Summary

9 tools reported issues (Accessibility Checker + Alfa + ASLint + Axe + Editoria11y + HTML CodeSniffer + QualWeb + Testaro + WallyAX)

37 issues were reported (7 highest, 8 high, 8 low, 14 lowest priority)

Details

Highest priority

link not named

• Why it matters: User cannot get help understanding what a link points to
• Related WCAG standard: 2.4.4
• Reported by 7 tools (Accessibility Checker + Alfa + Axe + Editoria11y + HTML CodeSniffer + QualWeb + WallyAX)
• 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 4 tools (ASLint + Editoria11y + QualWeb + WallyAX)
• 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?

contrast poor

• Why it matters: Content is difficult to understand
• Related WCAG standard: 1.4.3
• Reported by 2 tools (Accessibility Checker + Axe)
• Where was the issue found?

figure not named

• Why it matters: User cannot get help on the topic of a figure
• Related WCAG standard: 1.1.1
• Reported by 1 tool (Accessibility Checker)
• Where was the issue found?

Tab-focusable elements wrong

• Why it matters: Item selections by a keyboard-only user are useless or impossible
• Related WCAG standard: 2.1.1
• Reported by 1 tool (Testaro)
• 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

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?

role invalid

• Why it matters: User cannot get help on the nature of an item
• Related WCAG standard: 4.1.2
• Reported by 1 tool (Accessibility Checker)
• Where was the issue found?

h1 not 1st heading

• Why it matters: User cannot understand the topic of the document
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Alfa)
• 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?

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?

element focusability and operability conflict

• Why it matters: Keyboard-only user cannot operate an item
• Related WCAG standard: 2.1.1
• 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?

skip method missing or invalid

• Why it matters: Keyboard-only user cannot easily reach the specific content of the document
• Related WCAG standard: 2.4.1
• Reported by 1 tool (WallyAX)
• Where was the issue found?

Low priority

not exactly 1 h1 heading

• Why it matters: User cannot understand the topic of the document
• Related WCAG standard: 1.3.1
• Reported by 2 tools (ASLint + Axe)
• 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?

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?

main missing

• 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?

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?

primary heading not h1

• Why it matters: User cannot understand the topic of the document
• Related WCAG standard: 1.3.1
• Reported by 1 tool (WallyAX)
• 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?

Lowest priority

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 3 tools (Accessibility Checker + Alfa + Axe)
• 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?

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?

text contrast improvable

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

skip method missing or invalid?

• Why it matters: Keyboard-only user may be unable easily to reach the specific content of the document
• Related WCAG standard: 2.4.1
• Reported by 1 tool (Alfa)
• 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?

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?

link to non-web resource

• Why it matters: Document points to harder-to-use resources
• Related WCAG standard: 1.3.3
• Reported by 1 tool (Editoria11y)
• 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?

text contrast not testable

• Why it matters: Text may be difficult to read
• Related WCAG standard: 1.4.3
• Reported by 1 tool (HTML CodeSniffer)
• 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?

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?