Kilotest: Issues reported for Sightline Institute

About the Sightline Institute page

• URL: https://www.sightline.org/
• Tested by job 8ip on 2026-04-03 at 04:04

Issues reported

Summary

11 tools reported issues (Accessibility Checker + Alfa + ASLint + Axe + Editoria11y + Html Checker API + HTML CodeSniffer + QualWeb + Testaro + WallyAX + WAVE)

57 issues were reported (14 highest, 5 high, 13 low, 25 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 8 tools (Accessibility Checker + Alfa + Axe + Editoria11y + HTML CodeSniffer + QualWeb + WallyAX + WAVE)
• Where was the issue found?

contrast poor

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

iframe not named

• Why it matters: User cannot get help on the topic of an embedded document
• Related WCAG standard: 4.1.2
• Reported by 4 tools (Accessibility Checker + ASLint + HTML CodeSniffer + WallyAX)
• Where was the issue found?

attribute invalid

• Why it matters: Item behaves improperly
• Related WCAG standard: 1.3.1
• Reported by 3 tools (Accessibility Checker + Axe + WallyAX)
• Where was the issue found?

aria attribute invalid

• Why it matters: Item behavior violates user expectations
• Related WCAG standard: 4.1.2
• Reported by 3 tools (Alfa + Axe + QualWeb)
• 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?

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?

image not named

• Why it matters: User cannot get help to know what is in an image
• Related WCAG standard: 1.1.1
• Reported by 1 tool (Accessibility Checker)
• Where was the issue found?

CSS bans page rotation

• Why it matters: User must read sideways after rotating a device
• Related WCAG standard: 1.3.4
• Reported by 1 tool (ASLint)
• Where was the issue found?

parent invalid

• Why it matters: User cannot properly operate an item
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Html Checker API)
• Where was the issue found?

attribute value invalid

• Why it matters: Item behaves improperly
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Html Checker API)
• Where was the issue found?

attribute missing

• Why it matters: Item behaves improperly
• Related WCAG standard: 4.1.2
• Reported by 1 tool (Html Checker API)
• 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?

CSS invalid

• Why it matters: Document cannot be properly displayed
• Related WCAG standard: 4.1
• Reported by 1 tool (Html Checker API)
• 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?

Low priority

heading level skipped

• Why it matters: Helper misdescribes the document
• Related WCAG standard: 1.3.1
• Reported by 4 tools (Alfa + Axe + Html Checker API + WAVE)
• Where was the issue found?

decorative element has title

• Why it matters: Hovering-produced information is denied to a keyboard-only user
• Related WCAG standard: 1.3.1
• Reported by 3 tools (ASLint + HTML CodeSniffer + WAVE)
• 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?

font size absolute

• Why it matters: User cannot adjust the text size for readability
• Related WCAG standard: 1.4.4
• Reported by 1 tool (Alfa)
• Where was the issue found?

heading heads nothing

• Why it matters: Helper misdescribes the document
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Alfa)
• Where was the issue found?

label types incompatible

• Why it matters: User cannot get reliable help on the topics of form items
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Testaro)
• 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?

page content moves spontaneously

• Why it matters: Motion-sensitive user may suffer harm
• Related WCAG standard: 2.2.2
• Reported by 1 tool (Testaro)
• 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?

semantic properties represented with styles

• Why it matters: User cannot get help to fully understand the text
• Related WCAG standard: 1.3.1
• Reported by 1 tool (WallyAX)
• Where was the issue found?

adjacent links not combined

• Why it matters: Keyboard-only user expends extra effort to skip a link
• Related WCAG standard: 2.4.4
• Reported by 1 tool (WAVE)
• Where was the issue found?

Lowest priority

text contrast improvable

• Why it matters: Content is not easy to understand
• Related WCAG standard: 1.4.6
• Reported by 6 tools (Alfa + ASLint + Axe + HTML CodeSniffer + QualWeb + WallyAX)
• 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?

tabindex positive

• Why it matters: Keyboard-only user cannot predict the navigation sequence
• Related WCAG standard: 2.4.3
• Reported by 3 tools (ASLint + WallyAX + WAVE)
• 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?

link name vague

• Why it matters: User may misunderstand what a link points to
• Related WCAG standard: 2.4.4
• Reported by 2 tools (ASLint + WAVE)
• 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 2 tools (HTML CodeSniffer + QualWeb)
• Where was the issue found?

position sticky

• Why it matters: User may be unable to see needed content or may be forced to scroll in both dimensions
• Related WCAG standard: 1.4.10
• Reported by 2 tools (HTML CodeSniffer + WallyAX)
• Where was the issue found?

button name not visible

• Why it matters: User cannot get help explaining a button
• Related WCAG standard: 4.1.2
• Reported by 1 tool (ASLint)
• Where was the issue found?

custom button keyboard-inoperable?

• Why it matters: Custom item may prevent a keyboard-only user from operating it
• Related WCAG standard: 2.1.1
• Reported by 1 tool (ASLint)
• 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?

no default option

• Why it matters: User may risk erroneously submitting a form
• Related WCAG standard: 4.1.2
• Reported by 1 tool (ASLint)
• Where was the issue found?

link destination not URL

• Why it matters: Helper cannot properly explain a link to a 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?

type redundant

• Why it matters: Document includes unnecessary code
• Related WCAG standard: 1.3.1
• Reported by 1 tool (Html Checker API)
• 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?

overflow hidden?

• Why it matters: User may be unable to enlarge the text for readability
• Related WCAG standard: 1.4.4
• Reported by 1 tool (QualWeb)
• Where was the issue found?

all-capital text

• Why it matters: Text is difficult to read
• Related WCAG standard: 3.1.5
• Reported by 1 tool (Testaro)
• Where was the issue found?

large visible-element count

• Why it matters: User cannot easily find items in the document
• Related WCAG standard: 2.4
• Reported by 1 tool (Testaro)
• 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?

role assigned instead of implicit

• Why it matters: User may misunderstand the purpose of an item
• Related WCAG standard: 4.1.2
• 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?

title attribute invalid

• Why it matters: User gets too little, too much, or repeated help explaining an item
• Related WCAG standard: 1.3.1
• 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?

noscript element not equivalent?

• Why it matters: User who has disabled JavaScript may be denied some content
• Related WCAG standard: 4.1
• Reported by 1 tool (WAVE)
• Where was the issue found?

title attribute redundant

• Why it matters: Helper repeats the explanation of an item
• Related WCAG standard: 1.3.1
• Reported by 1 tool (WAVE)
• Where was the issue found?