Issues reported for Portland Accessibility and User Experience Meetup home
About the page
- URL: https://pdxa11yux.org/
- Tested 199 days ago on 2026-04-25 at 17:57 by job
260425T1728-o4p - Rule engines: 10 called, 10 able to test, violations reported by 8
- Results: 49 violations, 24 violators, 8 issues
- Download the full technical report (JSON)
History
This is the only available report about the page.
Issues reported
Highest priority: 1
-
abbr title missing
- Why it matters: User cannot get help understanding an abbreviation
- Priority: highest
- Related WCAG standard: 3.1.4
- Reported by 2 rule engines (ASLint + QualWeb)
- Results: 2 violations, 2 violators
High priority: 0
- None
Low priority: 2
-
line height low
- Why it matters: Text is difficult to read
- Priority: low
- Related WCAG standard: 1.4.8
- Reported by 1 rule engine (Alfa)
- Results: 3 violations, 2 violators
-
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: 10 violations, 10 violators
Lowest priority: 5
-
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 + ASLint + Axe + HTML CodeSniffer)
- Results: 20 violations, 10 violators
-
role redundant
- Why it matters: Page includes unnecessary code
- Priority: lowest
- Related WCAG standard: 4.1.2
- Reported by 2 rule engines (Accessibility Checker + Html Checker API)
- Results: 2 violations, 1 violator
-
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 + Testaro)
- Results: 9 violations, 9 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: 1 violation, 1 violator
-
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: 2 violations, 1 violator
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 Portland Accessibility and User Experience Meetup home web page. Describe them and propose a plan to resolve the genuine defects.