Issues reported for ICF North Texas home

About the page

URL: https://www.icf-nt.com/
Tested 16 days ago on 2026-10-25 at 19:55 by job 261025T1953-5g6
Rule engines: 12 called, 11 able to test, violations reported by 11
Results: 1034 violations, 335 violators, 73 issues
Download the full technical report (JSON)

History

This is the only available report about the page.

Request a retest

Issues reported

Highest priority: 16

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 9 rule engines (Accessibility Checker + Axe + Editoria11y + Html Checker API + HTML CodeSniffer + Pour + QualWeb + SureA11y + WAVE)
- Results: 63 violations, 10 violators
Where was the issue found?
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 8 rule engines (Accessibility Checker + Axe + Editoria11y + HTML CodeSniffer + Pour + QualWeb + SureA11y + WAVE)
- Results: 69 violations, 12 violators
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 6 rule engines (Accessibility Checker + Axe + HTML CodeSniffer + Pour + SureA11y + WAVE)
- Results: 32 violations, 16 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 5 rule engines (ASLint + Editoria11y + HTML CodeSniffer + QualWeb + WAVE)
- Results: 39 violations, 22 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 4 rule engines (ASLint + Html Checker API + HTML CodeSniffer + QualWeb)
- Results: 6 violations, 5 violators
Where was the issue found?
button not named
- Why it matters: User cannot get help explaining a button
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 3 rule engines (Html Checker API + HTML CodeSniffer + WAVE)
- Results: 4 violations, 2 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 2 rule engines (Accessibility Checker + ASLint)
- Results: 5 violations, 3 violators
Where was the issue found?
attribute invalid
- Why it matters: Item behaves improperly
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (Accessibility Checker + Html Checker API)
- Results: 73 violations, 40 violators
Where was the issue found?
no role-required name
- Why it matters: User cannot get help understanding an item
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (Accessibility Checker)
- Results: 2 violations, 2 violators
Where was the issue found?
dialog not named
- Why it matters: User cannot get help explaining a pop-up window
- Priority: highest
- Related WCAG standard: 4.1.2
- Reported by 1 rule engine (ASLint)
- Results: 2 violations, 2 violators
Where was the issue found?
internal link broken
- Why it matters: User cannot reach a promised page location
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- Results: 7 violations, 3 violators
Where was the issue found?
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 1 rule engine (ASLint)
- Results: 1 violation, 1 violator
Where was the issue found?
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: 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: 2 violations, 2 violators
Where was the issue found?
heading image not named
- Why it matters: User cannot get help understanding an image used as a heading
- Priority: highest
- Related WCAG standard: 1.1.1
- Reported by 1 rule engine (QualWeb)
- Results: 1 violation, 1 violator
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: 8 violations, 8 violators
Where was the issue found?

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 7 rule engines (Accessibility Checker + ASLint + Axe + Editoria11y + HTML CodeSniffer + Pour + WAVE)
- Results: 14 violations, 3 violators
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 4 rule engines (ASLint + Html Checker API + HTML CodeSniffer + QualWeb)
- Results: 8 violations, 4 violators
Where was the issue found?
table headers missing
- Why it matters: User cannot get help on relationships in a table
- Priority: high
- Related WCAG standard: 1.3.1
- Reported by 3 rule engines (Accessibility Checker + ASLint + Editoria11y)
- Results: 5 violations, 4 violators
Where was the issue found?
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
Where was the issue found?
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 3 rule engines (ASLint + HTML CodeSniffer + Testaro)
- Results: 9 violations, 9 violators
Where was the issue found?
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 2 rule engines (Accessibility Checker + SureA11y)
- Results: 2 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: 8 violations, 8 violators
Where was the issue found?
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: 8 violations, 8 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?
contenteditable element incomplete
- Why it matters: User cannot get help on how to edit editable content
- Priority: high
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- Results: 3 violations, 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?
tab-opening link action unstated
- Why it matters: Following a link opens a new window, surprising a user
- Priority: high
- Related WCAG standard: 3.2.5
- Reported by 1 rule engine (Editoria11y)
- Results: 8 violations, 8 violators
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: 3 violations, 3 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: 38 violations, 1 violator
Where was the issue found?
table not marked as such
- Why it matters: Helper misinforms a user about whether items are cells of a table
- Priority: high
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (QualWeb)
- Results: 2 violations, 2 violators
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)
- Results: 9 violations, 9 violators
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: 3 violations, 3 violators
Where was the issue found?
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: 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: 2 violations, 1 violator
Where was the issue found?

Low priority: 15

link href missing
- Why it matters: Helper cannot properly explain a link to a user
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 3 rule engines (ASLint + Html Checker API + Testaro)
- Results: 5 violations, 4 violators
Where was the issue found?
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: 2 violations, 2 violators
Where was the issue found?
table misused
- Why it matters: Helper misinforms a user about whether items are cells of a table
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (QualWeb + Testaro)
- Results: 4 violations, 2 violators
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)
- Results: 11 violations, 6 violators
Where was the issue found?
link image alt duplicative
- Why it matters: Helper repeats the explanation of a link
- Priority: low
- Related WCAG standard: 1.1.1
- Reported by 1 rule engine (HTML CodeSniffer)
- Results: 2 violations, 2 violators
Where was the issue found?
cell headers ambiguous?
- Why it matters: User may be unable to get help on relationships in a table
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (QualWeb)
- Results: 8 violations, 5 violators
Where was the issue found?
adjacent links not combined
- Why it matters: Keyboard-only user expends extra effort to skip a link
- Priority: low
- Related WCAG standard: 2.4.4
- Reported by 1 rule engine (QualWeb)
- Results: 2 violations, 2 violators
Where was the issue found?
aside child of landmark
- Why it matters: User cannot get help on how some of the page is organized
- Priority: low
- Related WCAG standard: 1.3.6
- Reported by 1 rule engine (QualWeb)
- Results: 1 violation, 1 violator
Where was the issue found?
main child of landmark
- Why it matters: User cannot get help on how some of the page is organized
- Priority: low
- Related WCAG standard: 1.3.6
- Reported by 1 rule engine (QualWeb)
- Results: 1 violation, 1 violator
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: 11 violations, 11 violators
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?
duplicate attribute
- Why it matters: Browser processes the page improperly
- Priority: low
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Testaro)
- Results: 6 violations, 1 violator
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?
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: 58 violations, 58 violators
Where was the issue found?

Lowest priority: 23

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: 148 violations, 58 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: 27 violations, 21 violators
Where was the issue found?
tabindex positive
- Why it matters: Keyboard-only user cannot predict the navigation sequence
- Priority: lowest
- Related WCAG standard: 2.4.3
- Reported by 3 rule engines (ASLint + Axe + Pour)
- Results: 3 violations, 2 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: 77 violations, 48 violators
Where was the issue found?
table caption missing or empty
- Why it matters: User cannot get help on the topic of a table
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (ASLint + QualWeb)
- Results: 6 violations, 5 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: 1 violation, 1 violator
Where was the issue found?
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: 1 violation, 1 violator
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: 5 violations, 4 violators
Where was the issue found?
aria-label on non-labelable role
- Why it matters: User is misinformed about an item
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Html Checker API)
- Results: 3 violations, 3 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: 25 violations, 25 violators
Where was the issue found?
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 (Pour)
- Results: 1 violation, 1 violator
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?
list-like br use dubious
- Why it matters: User cannot get help recognizing a list of items
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (QualWeb)
- Results: 1 violation, 1 violator
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: 35 violations, 35 violators
Where was the issue found?
all-italic text
- Why it matters: Text is difficult to read
- Priority: lowest
- Related WCAG standard: 3.1.5
- Reported by 1 rule engine (Testaro)
- Results: 1 violation, 1 violator
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: 5 violations, 5 violators
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: 31 violations, 31 violators
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: 21 violations, 21 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: 3 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: 31 violations, 31 violators
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: 39 violations, 39 violators
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)
- Results: 6 violations, 6 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 ICF North Texas home web page. Describe them and propose a plan to resolve the genuine defects.

Issues reported for ICF North Texas home

About the page

History

Issues reported

image not named

link not named

contrast poor

image link not named

ID not unique

button not named

svg image not named

attribute invalid

no role-required name

dialog not named

internal link broken

iframe not named

attribute value invalid

link element misplaced

heading image not named

Tab-focusable elements wrong

heading empty

element obsolete

table headers missing

form submission button missing

attribute obsolete

visible label not in name

target very small

code obsolete

role invalid

contenteditable element incomplete

focusable element not active

tab-opening link action unstated

code invalid

invalid CSS at-rule

table not marked as such

small targets too near to each other

element focusability and operability conflict

element beyond display when focused

hover indication poor

link href missing

heading names repeated

table misused

link indication poor

link image alt duplicative

cell headers ambiguous?

adjacent links not combined

aside child of landmark

main child of landmark

line height low

semantic properties represented with styles

page content moves spontaneously

duplicate attribute

links named identically

focus indication improvable

text contrast improvable

content beyond landmarks

tabindex positive

tab-opening link action unstated?

table caption missing or empty

button name not visible

labeling risky

link destination not URL

aria-label on non-labelable role

target small

tabindex redundant

text contrast not testable

list-like br use dubious

all-capital text

all-italic 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

hovering changes content

What you can do

Do it yourself

Use artificial intelligence