Kilotest: Issues reported for Pacific Northwest Software Quality Conference contact

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 Pacific Northwest Software Quality Conference contact web page. Summarize them and propose a plan to resolve the genuine ones.

• 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: 3
  • Violators: 2
  • Where was the issue found?

• svg image not named

  • Why it matters: User cannot get help understanding an image
  • Priority: highest
  • Related WCAG standard: 1.1.1
  • Reported by 2 rule engines (Accessibility Checker + ASLint)
  • Violations: 32
  • Violators: 30
  • Where was the issue found?

• 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 1 rule engine (WAVE)
  • Violations: 25
  • Violators: 25
  • Where was the issue found?

• autocomplete invalid

  • Why it matters: User cannot get help entering personal information in a form item
  • Priority: high
  • Related WCAG standard: 1.3.5
  • Reported by 1 rule engine (ASLint)
  • Violations: 1
  • Violators: 1
  • Where was the issue found?

• 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)
  • Violations: 7
  • Violators: 7
  • Where was the issue found?

• hover indication poor

  • Why it matters: User cannot explore the page reliably with a mouse
  • Priority: high
  • Related WCAG standard: 2.4
  • Reported by 1 rule engine (Testaro)
  • Violations: 5
  • Violators: 5
  • 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: 95
  • Violators: 95
  • 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?

• 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)
  • Violations: 33
  • Violators: 33
  • 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: 31
  • Violators: 31
  • Where was the issue found?

• text contrast improvable

  • Why it matters: Content is not easy to understand
  • Priority: lowest
  • Related WCAG standard: 1.4.6
  • Reported by 6 rule engines (ASLint + Axe + HTML CodeSniffer + Pour + QualWeb + SureA11y)
  • Violations: 225
  • Violators: 78
  • 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: 5
  • Violators: 4
  • 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: 34
  • Violators: 34
  • 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: 3
  • Violators: 3
  • Where was the issue found?

• all-capital text

  • Why it matters: Text is difficult to read
  • Priority: lowest
  • Related WCAG standard: 3.1.5
  • Reported by 1 rule engine (Testaro)
  • Violations: 3
  • Violators: 3
  • 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: 3
  • Violators: 1
  • 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: 6
  • Violators: 6
  • Where was the issue found?