Issues reported for Society for Evidence Based Gender Medicine home

Warning: This report is not the latest about the page. See history below.

About the page

URL: https://segm.org/
Tested 34 days ago on 2026-10-07 at 22:28 by job 261007T2202-905
Rule engines: 12 called, 12 able to test, violations reported by 12
Results: 3259 violations, 629 violators, 57 issues
Download the full technical report (JSON)

History

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

Issues reported

Highest priority: 12

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 8 rule engines (Accessibility Checker + Alfa + Axe + Editoria11y + Pour + QualWeb + SureA11y + WAVE)
- Results: 9 violations, 3 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 7 rule engines (Accessibility Checker + Alfa + Axe + HTML CodeSniffer + Pour + SureA11y + WAVE)
- Results: 701 violations, 231 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 7 rule engines (Alfa + Axe + HTML CodeSniffer + Pour + QualWeb + SureA11y + WAVE)
- Results: 44 violations, 12 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 6 rule engines (Accessibility Checker + Alfa + Axe + Pour + QualWeb + SureA11y)
- Results: 6 violations, 2 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 4 rule engines (Editoria11y + HTML CodeSniffer + QualWeb + WAVE)
- Results: 4 violations, 2 violators
Where was the issue found?
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 3 rule engines (Accessibility Checker + Pour + WAVE)
- Results: 9 violations, 9 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: 3 violations, 3 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 2 rule engines (ASLint + HTML CodeSniffer)
- Results: 9 violations, 9 violators
Where was the issue found?
label referent ineligible
- Why it matters: User cannot get help understanding an item in a form
- Priority: highest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Accessibility Checker)
- Results: 1 violation, 1 violator
Where was the issue found?
requirement invalid
- Why it matters: User may fail to get help determining whether a form item must be completed
- Priority: highest
- Related WCAG standard: 1.3.5
- Reported by 1 rule engine (ASLint)
- Results: 1 violation, 1 violator
Where was the issue found?
DOCTYPE missing
- Why it matters: Browser processes the page improperly
- Priority: highest
- Related WCAG standard: 4.1
- Reported by 1 rule engine (Html Checker)
- Results: 1 violation, 1 violator
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)
- Results: 1 violation, 1 violator
Where was the issue found?

High priority: 12

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 3 rule engines (Alfa + Pour + SureA11y)
- Results: 5 violations, 5 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: 2 violations, 2 violators
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)
- Results: 2 violations, 2 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?
h1 not 1st heading
- Why it matters: User cannot understand the topic of the page
- Priority: high
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (Alfa)
- Results: 1 violation, 1 violator
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 1 rule engine (ASLint)
- Results: 2 violations, 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: 7 violations, 7 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?
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: 2 violations, 2 violators
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)
- 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: 67 violations, 67 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: 4 violations, 4 violators
Where was the issue found?

Low priority: 11

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 + Pour)
- Results: 3 violations, 2 violators
Where was the issue found?
not exactly 1 h1 heading
- Why it matters: User cannot understand the topic of the page
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 3 rule engines (ASLint + Axe + Pour)
- Results: 3 violations, 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 2 rule engines (Alfa + Testaro)
- Results: 18 violations, 17 violators
Where was the issue found?
main missing
- 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 2 rule engines (Axe + Pour)
- Results: 2 violations, 1 violator
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)
- Results: 3 violations, 3 violators
Where was the issue found?
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: 1 violation, 1 violator
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 1 rule engine (HTML CodeSniffer)
- Results: 3 violations, 2 violators
Where was the issue found?
links not grouped as nav
- Why it matters: User cannot get help identifying links as a navigation tool
- Priority: low
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (QualWeb)
- Results: 1 violation, 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: 3 violations, 1 violator
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: 144 violations, 144 violators
Where was the issue found?

Lowest priority: 22

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)
- Results: 851 violations, 333 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 4 rule engines (Accessibility Checker + Alfa + Axe + Pour)
- Results: 776 violations, 430 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: 287 violations, 164 violators
Where was the issue found?
role redundant
- Why it matters: Page includes unnecessary code
- Priority: lowest
- Related WCAG standard: 4.1.2
- Reported by 2 rule engines (Accessibility Checker + Pour)
- Results: 2 violations, 1 violator
Where was the issue found?
aria attribute redundant
- Why it matters: Page includes unnecessary code
- Priority: lowest
- Related WCAG standard: 4.1.2
- Reported by 2 rule engines (Accessibility Checker + Pour)
- Results: 2 violations, 1 violator
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)
- Results: 42 violations, 41 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 2 rule engines (Alfa + Testaro)
- Results: 17 violations, 17 violators
Where was the issue found?
link name vague
- Why it matters: User may misunderstand what a link points to
- Priority: lowest
- Related WCAG standard: 2.4.4
- Reported by 2 rule engines (ASLint + Pour)
- Results: 23 violations, 23 violators
Where was the issue found?
element referenced by multiple labels
- Why it matters: User cannot get reliable help on the topics of form items
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 2 rule engines (ASLint + WAVE)
- Results: 4 violations, 3 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: 9 violations, 5 violators
Where was the issue found?
title attribute empty
- Why it matters: Hovering does not get the promised explanation of an item
- Priority: lowest
- Related WCAG standard: 1.3.1
- Reported by 1 rule engine (ASLint)
- Results: 1 violation, 1 violator
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)
- Results: 2 violations, 2 violators
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: 2 violations, 2 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: 106 violations, 106 violators
Where was the issue found?
event not keyboard-triggerable?
- Why it matters: Keyboard-only user may be unable to perform an action
- Priority: lowest
- Related WCAG standard: 2.1.1
- Reported by 1 rule engine (QualWeb)
- Results: 3 violations, 3 violators
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 1 rule engine (QualWeb)
- Results: 2 violations, 2 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?
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: 3 violations, 3 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: 3 violations, 3 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: 35 violations, 35 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: 19 violations, 19 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 Society for Evidence Based Gender Medicine home web page. Describe them and propose a plan to resolve the genuine defects.

Issues reported for Society for Evidence Based Gender Medicine home

About the page

History

Issues reported

image not named

contrast poor

button not named

link not named

image link not named

control not named

svg image not named

ID not unique

label referent ineligible

requirement invalid

DOCTYPE missing

autocomplete missing

target very small

code obsolete

forms not distinctly named

role invalid

h1 not 1st heading

attribute obsolete

tab-opening link action unstated

box size absolute

small targets too near to each other

input has placeholder instead of name

element focusability and operability conflict

element beyond display when focused

heading level skipped

not exactly 1 h1 heading

line height low

main missing

font size absolute

heading heads nothing

heading structure illogical

links not grouped as nav

links named identically

page content moves spontaneously

focus indication improvable

text contrast improvable

content beyond landmarks

tab-opening link action unstated?

role redundant

aria attribute redundant

target small

all-italic text

link name vague

element referenced by multiple labels

button name not visible

title attribute empty

fieldset missing?

labeling risky

text contrast not testable

event not keyboard-triggerable?

label location dubious

large visible-element count

text distortion

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