Kilotest: Issues reported for Animal Welfare Institute 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 Animal Welfare Institute contact web page. Summarize them and propose a plan to resolve the genuine ones.

• ID not unique

  • Why it matters: User may be pointed to the wrong item
  • Priority: highest
  • Related WCAG standard: 4.1
  • Reported by 3 rule engines (ASLint + Html Checker API + HTML CodeSniffer)
  • Violations: 4
  • Violators: 3
  • 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: 5
  • Violators: 4
  • 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 2 rule engines (Alfa + Pour)
  • Violations: 9
  • Violators: 9
  • Where was the issue found?

• option not named

  • Why it matters: User cannot get help to understand an option
  • Priority: highest
  • Related WCAG standard: 4.1.2
  • Reported by 1 rule engine (Html Checker API)
  • Violations: 1
  • Violators: 1
  • Where was the issue found?

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

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

• control child of link or button

  • Why it matters: User cannot reliably choose an item to click or tap
  • Priority: high
  • Related WCAG standard: 2.5.5
  • Reported by 4 rule engines (Html Checker API + Pour + SureA11y + Testaro)
  • Violations: 4
  • Violators: 2
  • Where was the issue found?

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

• 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 API)
  • Violations: 5
  • Violators: 1
  • 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 (Html Checker API)
  • Violations: 2
  • Violators: 2
  • 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 API)
  • Violations: 1
  • Violators: 1
  • Where was the issue found?

• box size absolute

  • Why it matters: User cannot enlarge the content of an item for readability
  • Priority: high
  • Related WCAG standard: 1.4.4
  • Reported by 1 rule engine (QualWeb)
  • 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: 15
  • Violators: 15
  • 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?

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

• element reloads or redirects

  • Why it matters: Page change may surprise a user
  • Priority: high
  • Related WCAG standard: 2.2.1
  • Reported by 1 rule engine (WAVE)
  • Violations: 1
  • Violators: 1
  • Where was the issue found?

• heading level skipped

  • Why it matters: Helper misdescribes the page
  • Priority: low
  • Related WCAG standard: 1.3.1
  • Reported by 4 rule engines (Alfa + Axe + Html Checker API + Pour)
  • 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: 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 2 rule engines (SureA11y + Testaro)
  • Violations: 5
  • Violators: 4
  • 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: 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: 45
  • Violators: 45
  • 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: 2
  • 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: 16
  • Violators: 16
  • 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 7 rule engines (Alfa + ASLint + Axe + HTML CodeSniffer + Pour + QualWeb + SureA11y)
  • Violations: 438
  • Violators: 60
  • 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: 34
  • Violators: 26
  • Where was the issue found?

• label location dubious

  • Why it matters: User may fail to notice the explanation of an item in a form
  • Priority: lowest
  • Related WCAG standard: 3.3.2
  • Reported by 2 rule engines (Accessibility Checker + QualWeb)
  • Violations: 12
  • Violators: 7
  • 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: 45
  • Violators: 45
  • 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 2 rule engines (Alfa + Testaro)
  • Violations: 3
  • 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: 7
  • Violators: 7
  • Where was the issue found?

• fieldset missing?

  • Why it matters: User may be unable to get help recognizing a group of related form items
  • Priority: lowest
  • Related WCAG standard: 1.3.1
  • Reported by 1 rule engine (ASLint)
  • Violations: 2
  • Violators: 2
  • 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?

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

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

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

• hovering changes content

  • Why it matters: User cannot explore the page reliably with a mouse
  • Priority: lowest
  • Related WCAG standard: 3.2.5
  • Reported by 1 rule engine (Testaro)
  • Violations: 3
  • Violators: 3
  • Where was the issue found?