Issues reported for Webby Awards home
About the page
- URL: https://www.webbyawards.com/
- Tested 175 days ago on 2026-05-19 at 15:20 by job
260519T1440-z57 - Rule engines: 10 called, 9 able to test, violations reported by 8
- Results: 2504 violations, 1008 violators, 75 issues
- Download the full technical report (JSON)
History
This is the only available report about the page.
Issues reported
Highest priority: 18
-
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 6 rule engines (Accessibility Checker + Alfa + Axe + Html Checker API + HTML CodeSniffer + QualWeb)
- Results: 7 violations, 3 violators
-
link not named
- Why it matters: User cannot get help understanding what a link points to
- Priority: highest
- Related WCAG standard: 2.4.4
- Reported by 5 rule engines (Accessibility Checker + Alfa + Axe + HTML CodeSniffer + QualWeb)
- Results: 5 violations, 2 violators
-
ID not unique
- Why it matters: User may be pointed to the wrong item
- Priority: highest
- Related WCAG standard: 4.1
- Reported by 4 rule engines (Alfa + ASLint + Html Checker API + HTML CodeSniffer)
- Results: 21 violations, 8 violators
-
focusable element hidden
- Why it matters: Keyboard-only user cannot navigate properly to the operable items
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 3 rule engines (Accessibility Checker + Alfa + Axe)
- Results: 18 violations, 7 violators
-
contrast poor
- Why it matters: Content is difficult to understand
- Priority: highest
- Related WCAG standard: 1.4.3
- Reported by 3 rule engines (Accessibility Checker + Alfa + Axe)
- Results: 172 violations, 132 violators
-
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)
- Results: 3 violations, 2 violators
-
presentational child focusable
- Why it matters: Keyboard-only user cannot navigate properly to the operable items
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 2 rule engines (Alfa + QualWeb)
- Results: 2 violations, 2 violators
-
figure not named
- Why it matters: User cannot get help on the topic of a figure
- Priority: highest
- Related WCAG standard: 1.1.1
- Reported by 1 rule engine (Accessibility Checker)
- Results: 25 violations, 25 violators
-
interactive component not named
- Why it matters: User cannot get help understanding a custom item
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Accessibility Checker)
- Results: 4 violations, 4 violators
-
label not named
- Why it matters: User cannot get help on the topic of a form item
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Accessibility Checker)
- Results: 2 violations, 2 violators
-
attribute value invalid
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- Results: 2 violations, 2 violators
-
meta charset declared too late
- Why it matters: Browser may display incorrect text
- Priority: highest
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker API)
- Results: 1 violation, 1 violator
-
attribute invalid
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- Results: 1 violation, 1 violator
-
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 API)
- Results: 2 violations, 2 violators
-
control not named
- Why it matters: User cannot get help on how to operate a form item
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 6 violations, 6 violators
-
input not named
- Why it matters: User cannot get help on what information to enter in a form item
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 8 violations, 8 violators
-
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)
- Results: 2 violations, 2 violators
-
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)
- Results: 1 violation, 1 violator
High priority: 19
-
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 4 rule engines (Accessibility Checker + ASLint + Html Checker API + HTML CodeSniffer)
- Results: 24 violations, 15 violators
-
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)
- Results: 3 violations, 2 violators
-
group not named
- Why it matters: User cannot get help on the topic of a group of form items
- Priority: high
- Related WCAG standard: 4.1.2
- Reported by 2 rule engines (Accessibility Checker + HTML CodeSniffer)
- Results: 6 violations, 5 violators
-
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 2 rule engines (ASLint + Html Checker API)
- Results: 4 violations, 4 violators
-
font small
- Why it matters: Text is difficult to read
- Priority: high
- Related WCAG standard: 1.4
- Reported by 2 rule engines (ASLint + Testaro)
- Results: 51 violations, 50 violators
-
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 2 rule engines (Axe + Testaro)
- Results: 2 violations, 2 violators
-
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)
- Results: 3 violations, 3 violators
-
role invalid
- Why it matters: User cannot get help on the nature of an item
- Priority: high
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Accessibility Checker)
- Results: 31 violations, 31 violators
-
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)
- Results: 2 violations, 2 violators
-
label empty
- Why it matters: User cannot get help on the topics of form items
- Priority: high
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- Results: 2 violations, 1 violator
-
focusable element not active
- Why it matters: Keyboard-only user cannot navigate properly to the operable items
- Priority: high
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Axe)
- Results: 31 violations, 31 violators
-
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 API)
- Results: 1 violation, 1 violator
-
CSS invalid
- Why it matters: Page cannot be properly displayed
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker API)
- Results: 2 violations, 2 violators
-
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)
- Results: 1 violation, 1 violator
-
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)
- Results: 18 violations, 18 violators
-
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)
- Results: 8 violations, 8 violators
-
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)
- Results: 166 violations, 166 violators
-
element beyond display when focused
- Why it matters: Keyboard-only user cannot navigate properly to the operable items
- Priority: high
- Related WCAG standard: 1.4.10
- Reported by 1 rule engine (Testaro)
- Results: 21 violations, 21 violators
-
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)
- Results: 8 violations, 8 violators
Low priority: 10
-
legend missing
- Why it matters: User cannot get help on the topic of a group of form items
- Priority: low
- Related WCAG standard: 4.1.2
- Reported by 4 rule engines (Accessibility Checker + ASLint + HTML CodeSniffer + QualWeb)
- Results: 17 violations, 5 violators
-
heading level skipped
- Why it matters: Helper misdescribes the page
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 3 rule engines (Alfa + Axe + Html Checker API)
- Results: 25 violations, 22 violators
-
heading names repeated
- Why it matters: User cannot differentiate parts of the page
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (ASLint + Testaro)
- Results: 4 violations, 4 violators
-
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 (Axe + Testaro)
- Results: 71 violations, 69 violators
-
links named identically
- Why it matters: User cannot get help differentiating links
- Priority: low
- Related WCAG standard: 2.4.4
- Reported by 2 rule engines (QualWeb + Testaro)
- Results: 28 violations, 9 violators
-
heading heads nothing
- Why it matters: Helper misdescribes the page
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Alfa)
- Results: 3 violations, 3 violators
-
heading structure illogical
- Why it matters: Helper misdescribes the page
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 4 violations, 4 violators
-
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)
- Results: 1 violation, 1 violator
-
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)
- Results: 117 violations, 117 violators
-
tablist navigation nonstandard
- Why it matters: Tablist items behave improperly for a keyboard-only user
- Priority: low
- Related WCAG standard: 2.1.1
- Reported by 1 rule engine (Testaro)
- Results: 4 violations, 4 violators
Lowest priority: 28
-
text contrast improvable
- Why it matters: Content is not easy to understand
- Priority: lowest
- Related WCAG standard: 1.4.6
- Reported by 4 rule engines (Alfa + Axe + HTML CodeSniffer + QualWeb)
- Results: 146 violations, 81 violators
-
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 (Accessibility Checker + Alfa + Axe)
- Results: 301 violations, 234 violators
-
image name redundant
- Why it matters: Helper repeats the explanation of an image
- Priority: lowest
- Related WCAG standard: 1.1.1
- Reported by 3 rule engines (Accessibility Checker + ASLint + Axe)
- Results: 35 violations, 32 violators
-
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 + HTML CodeSniffer + Testaro)
- Results: 72 violations, 58 violators
-
text contrast not testable
- Why it matters: Text may be difficult to read
- Priority: lowest
- Related WCAG standard: 1.4.3
- Reported by 2 rule engines (HTML CodeSniffer + QualWeb)
- Results: 167 violations, 165 violators
-
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 1 rule engine (Alfa)
- Results: 35 violations, 35 violators
-
item makes testing inconclusive
- Why it matters: Item prevents a conclusive accessibility test
- Priority: lowest
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Alfa)
- Results: 260 violations, 59 violators
-
false aria-hidden value risky
- Why it matters: User may be misled by erroneously hidden or revealed page content
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- Results: 32 violations, 10 violators
-
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)
- Results: 2 violations, 2 violators
-
link name vague
- Why it matters: User may misunderstand what a link points to
- Priority: lowest
- Related WCAG standard: 2.4.4
- Reported by 1 rule engine (ASLint)
- Results: 23 violations, 23 violators
-
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)
- Results: 10 violations, 10 violators
-
tabindex redundant
- Why it matters: Revision risks interfering with navigation by a keyboard-only user
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- Results: 33 violations, 32 violators
-
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)
- Results: 1 violation, 1 violator
-
image dubiously named
- Why it matters: Helper may describe an image inadequately
- Priority: lowest
- Related WCAG standard: 1.1.1
- Reported by 1 rule engine (ASLint)
- Results: 1 violation, 1 violator
-
links dubiously share name
- Why it matters: User may be unable to get help differentiating links
- Priority: lowest
- Related WCAG standard: 2.4.4
- Reported by 1 rule engine (Axe)
- Results: 4 violations, 4 violators
-
type redundant
- Why it matters: Page includes unnecessary code
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- Results: 32 violations, 32 violators
-
image dubiously marked decorative
- Why it matters: Helper ignores an image that is apparently informative
- Priority: lowest
- Related WCAG standard: 1.1.1
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 4 violations, 4 violators
-
position sticky
- Why it matters: User may be unable to see needed content or may be forced to scroll in both dimensions
- Priority: lowest
- Related WCAG standard: 1.4.10
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 8 violations, 8 violators
-
overflow hidden?
- Why it matters: User may be unable to enlarge the text for readability
- Priority: lowest
- Related WCAG standard: 1.4.4
- Reported by 1 rule engine (QualWeb)
- Results: 113 violations, 113 violators
-
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)
- Results: 80 violations, 80 violators
-
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 1 rule engine (QualWeb)
- Results: 2 violations, 2 violators
-
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)
- Results: 20 violations, 20 violators
-
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)
- Results: 1 violation, 1 violator
-
text distortion
- Why it matters: Text is difficult to read
- Priority: lowest
- Related WCAG standard: 3.1.5
- Reported by 1 rule engine (Testaro)
- Results: 115 violations, 115 violators
-
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)
- Results: 4 violations, 4 violators
-
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)
- Results: 7 violations, 1 violator
-
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)
- Results: 25 violations, 25 violators
-
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)
- Results: 31 violations, 31 violators
What you can do
Choose how to address these issues:
Do it yourself
Explore the issues, following the links above. Decide which issues are actual defects. Plan and implement corrections. Then retest the page.
Use artificial intelligence
Make Kilotest available to an AI assistant. Then give it a prompt like this:
Kilotest reports issues on the Webby Awards home web page. Describe them and propose a plan to resolve the genuine defects.