Kilotest: Issues reported for PTR Global

About the PTR Global page

URL: https://www.ptrglobal.com/
Tested 44 days ago by job sdo on 2026-06-05 at 04:36
Page not testable by Html Checker API (World Wide Web Consortium): HTTP 502: Bad Gateway (<!DOCTYPE html>   <!--[if IE 8]> <html class="no-)
Page not testable by WAVE (Utah State University): Timed out at 25 seconds

Issues reported

Summary

9 rule engines reported issues (Accessibility Checker + Alfa + ASLint + Axe + Editoria11y + Html Checker + HTML CodeSniffer + QualWeb + Testaro)

90 issues were reported (17 highest, 21 high, 13 low, 39 lowest priority)

1227 violators were reported

Download the full technical report

Details

Highest priority: 17

link not named
- Why it matters: User cannot get help understanding what a link points to
- Related WCAG standard: 2.4.4
- Reported by 6 rule engines (Accessibility Checker + Alfa + Axe + Editoria11y + HTML CodeSniffer + QualWeb)
- 10 violators were reported
- 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 6 rule engines (Accessibility Checker + Alfa + Axe + Editoria11y + HTML CodeSniffer + QualWeb)
- 8 violators were reported
- Where was the issue found?
contrast poor
- Why it matters: Content is difficult to understand
- Related WCAG standard: 1.4.3
- Reported by 4 rule engines (Accessibility Checker + Alfa + Axe + HTML CodeSniffer)
- 133 violators were reported
- Where was the issue found?
ID not unique
- Why it matters: User may be pointed to the wrong item
- Related WCAG standard: 4.1.1
- Reported by 3 rule engines (ASLint + Axe + HTML CodeSniffer)
- 65 violators were reported
- 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 rule engines (Accessibility Checker + ASLint)
- 6 violators were reported
- Where was the issue found?
internal link broken
- Why it matters: User cannot reach a promised document location
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (ASLint + HTML CodeSniffer)
- 8 violators were reported
- Where was the issue found?
no role-required name
- Why it matters: User cannot get help understanding an item
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Accessibility Checker)
- 1 violator was reported
- 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 rule engine (Accessibility Checker)
- 3 violators were reported
- 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 1 rule engine (ASLint)
- 1 violator was reported
- 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 rule engine (ASLint)
- 1 violator was reported
- Where was the issue found?
aria attribute invalid
- Why it matters: Item behavior violates user expectations
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Axe)
- 3 violators were reported
- 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 rule engine (Html Checker)
- 1 violator was reported
- Where was the issue found?
CSS background invalid
- Why it matters: Background is displayed improperly
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker)
- 1 violator was reported
- Where was the issue found?
link element invalid
- Why it matters: Document fails to get a needed external resource
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker)
- 3 violators were reported
- Where was the issue found?
fatal error
- Why it matters: Document prevents testing for accessibility
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker)
- 1 violator was reported
- Where was the issue found?
autocomplete missing
- Why it matters: User cannot get help entering personal information in a form
- Related WCAG standard: 1.3.5
- Reported by 1 rule engine (Testaro)
- 2 violators were reported
- 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 rule engine (Testaro)
- 1 violator was reported
- Where was the issue found?

High priority: 21

heading empty
- Why it matters: User cannot get help on the topic of a part of the document
- Related WCAG standard: 2.4.6
- Reported by 7 rule engines (Accessibility Checker + Alfa + ASLint + Axe + Editoria11y + HTML CodeSniffer + QualWeb)
- 2 violators were reported
- Where was the issue found?
attribute obsolete
- Why it matters: Document includes obsolete code that the browser may fail to process
- Related WCAG standard: 4.1
- Reported by 2 rule engines (ASLint + Html Checker)
- 2 violators were reported
- Where was the issue found?
form submission button missing
- Why it matters: User cannot easily submit a form
- Related WCAG standard: 3.2.2
- Reported by 2 rule engines (ASLint + HTML CodeSniffer)
- 2 violators were reported
- Where was the issue found?
code obsolete
- Why it matters: Document contains code that is no longer standard
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Accessibility Checker)
- 5 violators were reported
- Where was the issue found?
navigations not distinctly named
- Why it matters: User cannot get help on how some of the document is organized
- Related WCAG standard: 1.3.6
- Reported by 1 rule engine (Accessibility Checker)
- 2 violators were reported
- Where was the issue found?
role invalid
- Why it matters: User cannot get help on the nature of an item
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Accessibility Checker)
- 4 violators were reported
- Where was the issue found?
negative text-indent
- Why it matters: Helper may hide content from a user
- Related WCAG standard: 4.1
- Reported by 1 rule engine (ASLint)
- 2 violators were reported
- Where was the issue found?
font small
- Why it matters: Text is difficult to read
- Related WCAG standard: 1.4
- Reported by 1 rule engine (ASLint)
- 2 violators were reported
- Where was the issue found?
focusable element not active
- Why it matters: Keyboard-only user cannot navigate properly to the operable items
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Axe)
- 4 violators were reported
- Where was the issue found?
landmarks not distinctly named
- Why it matters: User cannot get help on how some of the document is organized
- Related WCAG standard: 1.3.6
- Reported by 1 rule engine (Axe)
- 1 violator was reported
- Where was the issue found?
tab-opening link action unstated
- Why it matters: Following a link opens a new window, surprising a user
- Related WCAG standard: 3.2.5
- Reported by 1 rule engine (Editoria11y)
- 33 violators were reported
- Where was the issue found?
image named with filename
- Why it matters: Helper gives a user the filename of an image instead of describing it
- Related WCAG standard: 1.1.1
- Reported by 1 rule engine (Editoria11y)
- 14 violators were reported
- Where was the issue found?
meta invalid
- Why it matters: Document fails to include needed data
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker)
- 3 violators were reported
- Where was the issue found?
CSS invalid
- Why it matters: Document cannot be properly displayed
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker)
- 1 violator was reported
- Where was the issue found?
code invalid
- Why it matters: Invalid code in the document may prevent a helper from working
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker)
- 1 violator was reported
- Where was the issue found?
element closure invalid
- Why it matters: Document contains invalid code
- Related WCAG standard: 4.1.1
- Reported by 1 rule engine (Html Checker)
- 2 violators were reported
- 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 rule engine (QualWeb)
- 1 violator was reported
- 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
- Related WCAG standard: 2.5.8
- Reported by 1 rule engine (Testaro)
- 16 violators were reported
- 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
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Testaro)
- 1 violator was reported
- 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 rule engine (Testaro)
- 28 violators were reported
- 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 rule engine (Testaro)
- 6 violators were reported
- Where was the issue found?

Low priority: 13

heading level skipped
- Why it matters: Helper misdescribes the document
- Related WCAG standard: 1.3.1
- Reported by 3 rule engines (Alfa + Axe + Editoria11y)
- 16 violators were reported
- Where was the issue found?
heading structure illogical
- Why it matters: Helper misdescribes the document
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (ASLint + HTML CodeSniffer)
- 22 violators were reported
- Where was the issue found?
link href missing
- Why it matters: Helper cannot properly explain a link to a user
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (ASLint + Testaro)
- 15 violators were reported
- 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 rule engines (QualWeb + Testaro)
- 9 violators were reported
- Where was the issue found?
fieldset missing
- Why it matters: User cannot get help recognizing a group of related form items
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Accessibility Checker)
- 5 violators were reported
- Where was the issue found?
heading heads nothing
- Why it matters: Helper misdescribes the document
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Alfa)
- 6 violators were reported
- Where was the issue found?
link incomplete
- Why it matters: User may fail to reach a promised location
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (HTML CodeSniffer)
- 2 violators were reported
- Where was the issue found?
table misused
- Why it matters: Helper misinforms a user about whether items are cells of a table
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (QualWeb)
- 4 violators were reported
- Where was the issue found?
cell headers ambiguous?
- Why it matters: User may be unable to get help on relationships in a table
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (QualWeb)
- 16 violators were reported
- 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 rule engine (Testaro)
- 288 violators were reported
- 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 rule engine (Testaro)
- 1 violator was reported
- 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 rule engine (Testaro)
- 1 violator was reported
- Where was the issue found?
focus indication improvable
- Why it matters: Keyboard-only user cannot easily choose an item to operate
- Related WCAG standard: 2.4.7
- Reported by 1 rule engine (Testaro)
- 62 violators were reported
- Where was the issue found?

Lowest priority: 39

text contrast improvable
- Why it matters: Content is not easy to understand
- Related WCAG standard: 1.4.6
- Reported by 5 rule engines (Alfa + ASLint + Axe + HTML CodeSniffer + QualWeb)
- 359 violators were reported
- Where was the issue found?
content beyond landmarks
- Why it matters: User cannot get help on how some of the document is organized
- Related WCAG standard: 1.3.6
- Reported by 3 rule engines (Accessibility Checker + Alfa + Axe)
- 7 violators were reported
- Where was the issue found?
label location dubious
- Why it matters: User may fail to notice the explanation of an item in a form
- Related WCAG standard: 3.3.2
- Reported by 3 rule engines (Accessibility Checker + ASLint + QualWeb)
- 7 violators were reported
- 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 3 rule engines (Alfa + HTML CodeSniffer + QualWeb)
- 80 violators were reported
- 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 rule engines (ASLint + HTML CodeSniffer + Testaro)
- 70 violators were reported
- Where was the issue found?
fieldset missing?
- Why it matters: User may be unable to get help recognizing a group of related form items
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (ASLint + HTML CodeSniffer)
- 24 violators were reported
- Where was the issue found?
table caption missing
- Why it matters: User cannot get help on the topic of a table
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (ASLint + QualWeb)
- 8 violators were reported
- Where was the issue found?
hr misused
- Why it matters: User cannot get help on the nature of segments of the document
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (ASLint + Testaro)
- 2 violators were reported
- Where was the issue found?
all-italic text
- Why it matters: Text is difficult to read
- Related WCAG standard: 3.1.5
- Reported by 2 rule engines (ASLint + Testaro)
- 34 violators were reported
- Where was the issue found?
role redundant
- Why it matters: Document includes unnecessary code
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Accessibility Checker)
- 3 violators were reported
- 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 1 rule engine (Alfa)
- 13 violators were reported
- Where was the issue found?
item makes testing inconclusive
- Why it matters: Item prevents a conclusive accessibility test
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Alfa)
- 11 violators were reported
- 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 rule engine (ASLint)
- 9 violators were reported
- Where was the issue found?
title attribute empty
- Why it matters: Hovering does not get the promised explanation of an item
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- 6 violators were reported
- 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 rule engine (ASLint)
- 10 violators were reported
- 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 1 rule engine (ASLint)
- 6 violators were reported
- Where was the issue found?
labeling risky
- Why it matters: User may misunderstand a form control
- Related WCAG standard: 3.3.2
- Reported by 1 rule engine (ASLint)
- 20 violators were reported
- 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 rule engine (ASLint)
- 58 violators were reported
- 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 rule engine (ASLint)
- 11 violators were reported
- Where was the issue found?
image dubiously named
- Why it matters: Helper may describe an image inadequately
- Related WCAG standard: 1.1.1
- Reported by 1 rule engine (ASLint)
- 3 violators were reported
- Where was the issue found?
element referenced by multiple labels
- Why it matters: User cannot get reliable help on the topics of form items
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- 20 violators were reported
- 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 rule engine (Axe)
- 2 violators were reported
- Where was the issue found?
link to non-web resource
- Why it matters: Document points to harder-to-use resources
- Related WCAG standard: 1.3.3
- Reported by 1 rule engine (Editoria11y)
- 7 violators were reported
- Where was the issue found?
heading abnormally long
- Why it matters: User has difficulty understanding the topic of a part of the document
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Editoria11y)
- 2 violators were reported
- Where was the issue found?
type redundant
- Why it matters: Document includes unnecessary code
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker)
- 25 violators were reported
- Where was the issue found?
heading-like styles dubious
- Why it matters: User may be unable to understand the topic of a part of the document
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (HTML CodeSniffer)
- 10 violators were reported
- Where was the issue found?
list unordered type dubious
- Why it matters: User may be unable to get help on whether a list is ordered
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (HTML CodeSniffer)
- 4 violators were reported
- 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 1 rule engine (HTML CodeSniffer)
- 6 violators were reported
- 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 rule engine (QualWeb)
- 149 violators were reported
- Where was the issue found?
image link text suspect
- Why it matters: Keyboard-only user may misunderstand the effect of following a link
- Related WCAG standard: 2.4.4
- Reported by 1 rule engine (QualWeb)
- 6 violators were reported
- Where was the issue found?
list-like br use dubious
- Why it matters: User cannot get help recognizing a list of items
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (QualWeb)
- 3 violators were reported
- 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 rule engine (Testaro)
- 43 violators were reported
- 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 rule engine (Testaro)
- 1 violator was reported
- Where was the issue found?
text distortion
- Why it matters: Text is difficult to read
- Related WCAG standard: 3.1.5
- Reported by 1 rule engine (Testaro)
- 36 violators were reported
- Where was the issue found?
double br use dubious
- Why it matters: User may be unable to get help to fully understand the text
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Testaro)
- 9 violators were reported
- 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 rule engine (Testaro)
- 27 violators were reported
- 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 rule engine (Testaro)
- 1 violator was reported
- 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 rule engine (Testaro)
- 20 violators were reported
- 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 rule engine (Testaro)
- 236 violators were reported
- Where was the issue found?

Kilotest: Issues reported for PTR Global

About the PTR Global page

Issues reported

Summary

Details

link not named

image not named

contrast poor

ID not unique

svg image not named

internal link broken

no role-required name

figure not named

iframe not named

CSS bans page rotation

aria attribute invalid

parent invalid

CSS background invalid

link element invalid

fatal error

autocomplete missing

Tab-focusable elements wrong

heading empty

attribute obsolete

form submission button missing

code obsolete

navigations not distinctly named

role invalid

negative text-indent

font small

focusable element not active

landmarks not distinctly named

tab-opening link action unstated

image named with filename

meta invalid

CSS invalid

code invalid

element closure invalid

box size absolute

small targets too near to each other

input has placeholder instead of name

element focusability and operability conflict

hover indication poor

heading level skipped

heading structure illogical

link href missing

links named identically

fieldset missing

heading heads nothing

link incomplete

table misused

cell headers ambiguous?

line height low

link indication poor

page content moves spontaneously

focus indication improvable

text contrast improvable

content beyond landmarks

label location dubious

text contrast not testable

tab-opening link action unstated?

fieldset missing?

table caption missing

hr misused

all-italic text

role redundant

target small

item makes testing inconclusive

button name not visible

title attribute empty

custom button keyboard-inoperable?

link name vague

labeling risky

tabindex redundant

link destination not URL

image dubiously named

element referenced by multiple labels

links dubiously share name

link to non-web resource

heading abnormally long