Issues reported for Translation Commons home

About the page

URL: https://translationcommons.org/
Tested 30 days ago on 2026-10-11 at 22:38 by job 261011T2228-bkc
Rule engines: 12 called, 11 able to test, violations reported by 10
Results: 621 violations, 209 violators, 40 issues
Download the full technical report (JSON)

History

34 days ago (oldest)
30 days ago (latest; this report)

Request a retest

Issues reported

Highest priority: 9

contrast poor
- Why it matters: Content is difficult to understand
- Priority: highest
- Related WCAG standard: 1.4.3
- Reported by 6 rule engines (Accessibility Checker + Axe + HTML CodeSniffer + Pour + SureA11y + WAVE)
- Results: 19 violations, 10 violators
Where was the issue found?
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)
- Results: 16 violations, 12 violators
Where was the issue found?
image 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 2 rule engines (ASLint + HTML CodeSniffer)
- Results: 4 violations, 4 violators
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 1 rule engine (Accessibility Checker)
- Results: 1 violation, 1 violator
Where was the issue found?
invalid landmark child of navigation role
- Why it matters: User cannot get help on how some of the page is organized
- Priority: highest
- Related WCAG standard: 1.3.6
- Reported by 1 rule engine (ASLint)
- Results: 8 violations, 8 violators
Where was the issue found?
meta bans zoom
- Why it matters: User cannot adjust the page size for readability
- Priority: highest
- Related WCAG standard: 1.4.4
- Reported by 1 rule engine (ASLint)
- Results: 1 violation, 1 violator
Where was the issue found?
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
Where was the issue found?
link element misplaced
- Why it matters: Page fails to get a needed external resource
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 3 violations, 3 violators
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)
- Results: 1 violation, 1 violator
Where was the issue found?

High priority: 10

visible label not in name
- Why it matters: User cannot get help choosing a form control to operate
- Priority: high
- Related WCAG standard: 2.5.3
- Reported by 3 rule engines (Accessibility Checker + Axe + SureA11y)
- Results: 3 violations, 1 violator
Where was the issue found?
target very small
- Why it matters: User cannot reliably choose an item to click or tap
- Priority: high
- Related WCAG standard: 2.5.8
- Reported by 2 rule engines (Pour + SureA11y)
- Results: 6 violations, 6 violators
Where was the issue found?
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: 1 violation, 1 violator
Where was the issue found?
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: 1 violation, 1 violator
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)
- Results: 10 violations, 10 violators
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)
- Results: 191 violations, 1 violator
Where was the issue found?
element obsolete
- Why it matters: Page includes obsolete code that the browser may fail to process
- Priority: high
- Related WCAG standard: 4.1
- Reported by 1 rule engine (QualWeb)
- Results: 5 violations, 5 violators
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)
- Results: 1 violation, 1 violator
Where was the issue found?
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: 1 violation, 1 violator
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)
- Results: 5 violations, 3 violators
Where was the issue found?

Low priority: 6

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)
- Results: 6 violations, 4 violators
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)
- Results: 20 violations, 20 violators
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)
- Results: 1 violation, 1 violator
Where was the issue found?
semantic properties represented with styles
- Why it matters: User cannot get help to fully understand the text
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Testaro)
- Results: 4 violations, 4 violators
Where was the issue found?
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
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)
- Results: 31 violations, 31 violators
Where was the issue found?

Lowest priority: 15

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)
- Results: 108 violations, 45 violators
Where was the issue found?
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 + Axe + Pour)
- Results: 4 violations, 4 violators
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)
- Results: 38 violations, 22 violators
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)
- Results: 17 violations, 17 violators
Where was the issue found?
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: 15 violations, 15 violators
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 1 rule engine (Pour)
- Results: 21 violations, 21 violators
Where was the issue found?
text contrast not testable
- Why it matters: Text may be difficult to read
- Priority: lowest
- Related WCAG standard: 1.4.3
- Reported by 1 rule engine (QualWeb)
- Results: 3 violations, 3 violators
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)
- Results: 4 violations, 4 violators
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)
- Results: 1 violation, 1 violator
Where was the issue found?
hr misused
- Why it matters: User cannot get help on the nature of segments of the page
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Testaro)
- Results: 1 violation, 1 violator
Where was the issue found?
double br use dubious
- Why it matters: User may be unable to get help to fully understand the text
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Testaro)
- Results: 1 violation, 1 violator
Where was the issue found?
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: 15 violations, 15 violators
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)
- Results: 4 violations, 1 violator
Where was the issue found?
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: 1 violation, 1 violator
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)
- Results: 47 violations, 47 violators
Where was the issue found?

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 Translation Commons home web page. Describe them and propose a plan to resolve the genuine defects.

Issues reported for Translation Commons home

About the page

History

Issues reported

contrast poor

ID not unique

image link not named

svg image not named

invalid landmark child of navigation role

meta bans zoom

attribute invalid

link element misplaced

Tab-focusable elements wrong

visible label not in name

target very small

role invalid

focusable element not active

code invalid

invalid CSS at-rule

element obsolete

box size absolute

element focusability and operability conflict

hover indication poor

link indication poor

line height low

links named identically

semantic properties represented with styles

page content moves spontaneously

focus indication improvable

text contrast improvable

content beyond landmarks

tab-opening link action unstated?

button name not visible

link destination not URL

target small

text contrast not testable

all-capital text

large visible-element count

hr misused

double br use dubious

role assigned instead of implicit

inconsistent heading, link, or button styles

title attribute invalid

z-index not zero

What you can do

Do it yourself

Use artificial intelligence