Accessibility digest

Contents

Synopsis
PageJared Young;Better Party;Missouri
URLhttps://votejaredyoung.com
Test date2024/09/22
Score4455
Configuration
Redirectionspermitted
Tool isolationno
Report format(s)standard
Requester
Devicedefault
Browser typewebkit
Reduced motionnot requested
Tested byTestaro, procedure senate2024
Scored byTestilo, procedure tsp50
Digested byTestilo, procedure tdp50
Full report 240915T1658-ikz-16.json

Introduction

How accessible is the Jared Young;Better Party;Missouri web page at https://votejaredyoung.com?

This digest gives one answer to that question. Eleven different tools (Alfa, ASLint, Axe, Editoria11y, Equal Access, HTML CodeSniffer, Nu Html Checker, QualWeb, Testaro, WAVE, and WallyAX) tested the page to check its compliance with their accessibility rules. In all, the tools define about a thousand rules, which are classified here into about three hundred accessibility issues.

The results were interpreted to yield a score, with 0 being ideal. The score for this page was 4455, the sum of 690 for the count of issues, 2102 for specific issues, 0 for unclassified rule violations, 666 for tool-by-tool ratings, 870 for the count of violating elements, 0 for the page preventing tools from running, 127 for browser warnings, and 0 for delayed page responses.

How the page was scored

Introduction

This is an explanation of the scoring of the page.

Motivations for scoring

Why score? Specifically, why aggregate many facts about a page into a single number?

One motivation is to simplify comparison and tracking. If you want to compare a page with other pages, or if you want to track changes in a page over time, aggregating many test results for each page into one page score simplifies the task. It becomes possible to say things like Page A is more accessible than page B or Page A is becoming more accessible over time.

Another motivation is to influence behavior. A score arises from decisions about importance, urgency, and other attributes. People may use scores to award benefits, impose costs, or prioritize work. So, scoring can influence who gets and does what.

How to score?

Scoring is subjective. Accessibility testing tools use various scoring procedures, based on various ideas.

The built-in scoring procedures of Testilo are based on the idea that multiple attributes should affect a web-page accessibility score, including:

Some ideas found elsewhere in accessibility scoring are rejected by the Testilo procedures:

Scoring method summary

The scoring method is found in the code of the procedure. The file for any procedure tspnn is in the file procs/score/tspnn.js within the Testilo package.

The score computed by this procedure for any page is a non-negative number. The numbers represent accessibility faults, so a higher-scoring page is considered less accessible than a lower-scoring page. The best possible score is 0.

The procedure makes the score of a page the sum of 7 components:

Scoring method details

The above component descriptions omit various details.

About a thousand tool rules are classified into issues in the tic50.js file used by this procedure. Each of those rules has a quality, ranging from 0 to 1. When the issue score is computed, the count of violations of each rule is multiplied by the quality of that rule. Whichever tool has the largest quality-weighted violation count for an issue, that count is treated as the instance count for the issue. Thus, if 8 tools each report 15 violations within the issue, and their rule qualities are all 1, the instance count is 15, not 120. Moreover, the issue itself has a weight, ranging from 1 to 4, representing its importance. This instance count is multiplied by that weight. That product is further multiplied by the issueCountWeight value, namely 10. That final product is further adjusted if the issue is inherently limited in instance count. For example, if the issue is that the page html element has no lang attribute, the instance count is limited to 1. If there is such a limit, the maxWeight value, namely 30, is divided by the actual instance count and the quotient is added to 1. That product (or 1 if there is no limit) is multiplied by the instance count, and then the result is treated as the contribution of the issue to the issue score.

Each solo (not yet issue-classified) rule violation is multiplied by the sum of 1 and the ordinal severity of the rule, to produce the solo score.

Each rule violation reported by each tool is severity-weighted in the same way as solo rule violations are. Then the sum of those violations is multiplied by the toolWeight value, namely 0.1, to produce the tool score.

The count of elements reported as violators of any rule is multiplied by the elementWeight value, namely 2, to produce the element score.

The count of prevented Testaro rules is multiplied by the testaroRulePreventionWeight quantity, namely 30, and the count of other prevented tools is multiplied by the preventionWeight value, namely 300, to produce the prevention score.

The log score is the sum of several components:

Each of these components is multiplied by a weight found in the logWeights object.

Finally, the latency score is based on how much longer it took for the page to become loaded and stable than expected. The expected total duration in seconds is the normalLatency value, namely 22 seconds (that is 2 seconds per visit, multiplied by the 11 visits of the 11 tools). This is subtracted from the actual total latency, and that difference is multiplied by the latencyWeight amount, namely 2.

Issue summary

Details about this summary

The summary

Sorting is by score.

How many violations each tool reported, by issue
IssueWCAGWeightScoreInstance counts
line height low1.4.82200alfa:44, testaro:100
contrast poor1.4.34164alfa:5, axe:41, htmlcs:11, ibm:11, qualWeb:31, wave:21, wax:23, aslint:0
ID not unique4.1.14160alfa:10, aslint:10, htmlcs:9, ibm:9, nuVal:36, wax:40, axe:0, qualWeb:0
content beyond landmarks1.3.61152alfa:152, axe:50, ibm:49, wax:51
h1 not 1st heading1.3.1393alfa:1
text contrast improvable1.4.6181alfa:6, aslint:81, axe:27, htmlcs:22, qualWeb:59, wax:33
void element has trailing slash4.1179nuVal:79
link indication poor1.3.3276testaro:38, alfa:0, axe:0
target very small2.5.8366alfa:22
main missing1.3.6262axe:1
primary heading not h11.3.1262wax:1
overflow hidden?1.4.4154qualWeb:54
link element invalid1.3.1448htmlcs:12, wax:12, nuVal:0
skip method missing or invalid2.4.1348wax:1, axe:0, ibm:0, wave:0
links named identically2.4.4240aslint:20, testaro:5, qualWeb:0
role assigned instead of implicit4.1.2139testaro:39
target small2.5.5138alfa:38, testaro:34
heading structure illogical1.3.1238aslint:19, htmlcs:9
focus indication poor2.4.7432testaro:8, alfa:0, aslint:0
image dubiously marked decorative1.1.1131htmlcs:31
large visible-element count2.4131testaro:1
link not named2.4.4428alfa:7, axe:7, ibm:7, qualWeb:7, ed11y:0, htmlcs:0, wave:0, wax:0
link not named2.4.4428aslint:7, ed11y:7, htmlcs:7, qualWeb:7, wave:7, wax:7
all-capital text3.1.5122aslint:22, testaro:1, alfa:0, ed11y:0
iframe not named4.1.2420aslint:5, htmlcs:1, wax:2, alfa:0, axe:0, ibm:0, qualWeb:0
error reference invalid3.3.1420qualWeb:5, ibm:0
container size unit not percentage1.4.10120qualWeb:20
type redundant1.3.1118nuVal:18
heading names repeated1.3.1218testaro:1, wax:9, aslint:0
inconsistent heading, link, or button styles3.2.4118testaro:18
heading level skipped1.3.1216alfa:8, axe:8, ed11y:8, wave:8, wax:0
text contrast not testable1.4.3116alfa:2, htmlcs:16, aslint:0
invalid landmark child of navigation role1.3.6416aslint:4
control not named4.1.2416htmlcs:3, wave:4, wax:3, alfa:0, axe:0, ibm:0, qualWeb:0
input not named4.1.2416htmlcs:4, wax:4, axe:0
attribute value invalid1.3.1416nuVal:4, ibm:0, wax:0
color missing1.4.3416qualWeb:4
attribute obsolete4.1315aslint:3, nuVal:5, htmlcs:0, ibm:0, testaro:0, wave:0
link destination not URL1.3.1115aslint:15
box size absolute1.4.4315qualWeb:5
element beyond display when focused1.4.10315testaro:5
heading heads nothing1.3.1214alfa:7, wax:0
meta invalid1.3.1312nuVal:4
code obsolete4.139ibm:3, nuVal:0
svg image not named1.1.148aslint:2, ibm:1, alfa:0, axe:0, qualWeb:0, wax:0
button not named4.1.248aslint:1, htmlcs:1, wave:1, wax:2, alfa:0, axe:0, nuVal:0, qualWeb:0
tab-opening link action unstated3.2.538ed11y:5
role redundant4.1.218nuVal:8, ibm:0
parent invalid1.3.148nuVal:2, ibm:0
element not focusable2.1.148testaro:4, alfa:0, qualWeb:0
tabindex redundant1.3.116aslint:6
tab-opening link action unstated?3.2.515aslint:5, htmlcs:5, testaro:5
labeling risky3.3.215aslint:5
position sticky1.4.1014aslint:4, htmlcs:2
nav links not list1.3.124htmlcs:2
no role-required name4.1.244ibm:1, wax:0
section heading missing1.3.114nuVal:4
autocomplete missing1.3.544testaro:2
z-index not zero1.414testaro:4
element in head invalid4.1.133aslint:1, testaro:0
landmarks not distinctly named1.3.633axe:1, wax:1, ibm:0
text distortion3.1.513testaro:3
filter style4.113testaro:3
link name vague2.4.412aslint:2, ed11y:2, wave:0
double br use dubious1.3.112testaro:2
noscript element not equivalent?4.112wave:2
item makes testing inconclusive4.111alfa:1
heading abnormally long1.3.111ed11y:1
audio or video alternatives missing?1.2.211wave:1

Itemized issues

The reported rule violations are itemized below, issue by issue. Additional details can be inspected in the full report.

Issue: line height low

Impact: Text is difficult to read

WCAG: 1.4.8

Score: 200

Elements

Violations of alfa rules

Rule r73

Description: Text line height is not at least 1.5

Count of instances: 44

Violations of testaro rules

Rule lineHeight

Description: Text has a line height less than 1.5 times its font size

Count of instances: 100

Issue: contrast poor

Impact: Content is difficult to understand

WCAG: 1.4.3

Score: 164

Elements

Violations of alfa rules

Rule r69

Description: Text outside widget has subminimum contrast

Count of instances: 5

Violations of axe rules

Rule color-contrast

Description: Element has insufficient color contrast

Count of instances: 41

Violations of htmlcs rules

Rule AAA.1_4_6.G18.Fail

Description: Contrast between the text and its background is less than 4.5:1

Count of instances: 11

Violations of ibm rules

Rule text_contrast_sufficient

Description: Text has a contrast with its background less than the WCAG AA minimum for its size and weight

Count of instances: 11

Violations of qualWeb rules

Rule QW-ACT-R37

Description: Text has less than the minimum contrast

Count of instances: 31

Violations of wave rules

Rule contrast

Description: Very low contrast

Count of instances: 21

Violations of wax rules

Rule ^This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of .+. Recommendation: change .+ to #.+$

Description: Contrast between the element text and its background is less than 4.5:1

Count of instances: 18

Rule ^This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 3:1, but text in this element has a contrast ratio of .+. Recommendation: change .+ to #.+$

Description: Contrast between the element text and its background is less than 3:1

Count of instances: 5

Issue: ID not unique

Impact: User may be pointed to the wrong item

WCAG: 4.1.1

Score: 160

Elements

Violations of alfa rules

Rule r3

Description: Element id attribute value is not unique

Count of instances: 10

Violations of aslint rules

Rule duplicated_id_attribute

Description: Element id attribute value is not unique

Count of instances: 10

Violations of htmlcs rules

Rule AAA.4_1_1.F77

Description: Duplicate id attribute value

Count of instances: 9

Violations of ibm rules

Rule element_id_unique

Description: Element has an id attribute value that is already in use

Count of instances: 9

Violations of nuVal rules

Rule ^Duplicate ID .+$|^The first occurrence of ID .* was here.*$

Description: Duplicate id

Count of instances: 36

Violations of wax rules

Rule ^Duplicate id attribute value .+ found on the web page.+$

Description: id attribute value is not unique

Count of instances: 40

Issue: content beyond landmarks

Impact: User cannot get help on how some of the document is organized

WCAG: 1.3.6

Score: 152

Elements

Violations of alfa rules

Rule r57

Description: Perceivable text content is not included in any landmark

Count of instances: 152

Violations of axe rules

Rule region

Description: Some page content is not contained by landmarks

Count of instances: 50

Violations of ibm rules

Rule aria_content_in_landmark

Description: Content is not within a landmark element

Count of instances: 49

Violations of wax rules

Rule Use landmarks to contain page content.

Description: Content is not within a landmark element

Count of instances: 51

Issue: h1 not 1st heading

Impact: User cannot understand the topic of the document

WCAG: 1.3.1

Score: 93

Elements

Violations of alfa rules

Rule r61

Description: First heading is not h1

Count of instances: 1

Issue: text contrast improvable

Impact: Content is not easy to understand

WCAG: 1.4.6

Score: 81

Elements

Violations of alfa rules

Rule r66

Description: Text contrast less than AAA requires

Count of instances: 6

Violations of aslint rules

Rule color_contrast_aaa7

Description: Text has contrast less than 7:1

Count of instances: 63

Rule color_contrast_aaa4

Description: Text has contrast less than 4.5:1

Count of instances: 18

Violations of axe rules

Rule color-contrast-enhanced

Description: Element has insufficient color contrast (Level AAA)

Count of instances: 27

Violations of htmlcs rules

Rule AAA.1_4_6.G17.Fail

Description: Text has insufficient contrast

Count of instances: 22

Violations of qualWeb rules

Rule QW-ACT-R76

Description: Text has less than the enhanced minimum contrast

Count of instances: 59

Violations of wax rules

Rule ^This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 7:1, but text in this element has a contrast ratio of .+. Recommendation: change .+ to #.+$

Description: Contrast between the element text and its background is less than 7:1

Count of instances: 33

Issue: void element has trailing slash

Impact: Document contains invalid code

WCAG: 4.1

Score: 79

Elements

Violations of nuVal rules

Rule Trailing slash on void elements has no effect and interacts badly with unquoted attribute values.

Description: Void element has a useless trailing slash.

Count of instances: 79

Issue: link indication poor

Impact: User cannot differentiate a link from plain text

WCAG: 1.3.3

Score: 76

Elements

Violations of testaro rules

Rule linkUl

Description: Inline links are not underlined

Count of instances: 38

Issue: target very small

Impact: User cannot reliably choose an item to click or tap

WCAG: 2.5.8

Score: 66

Elements

Violations of alfa rules

Rule r113

Description: Target size is substandard

Count of instances: 22

Issue: main missing

Impact: User cannot get help on how some of the document is organized

WCAG: 1.3.6

Score: 62

Elements

Violations of axe rules

Rule landmark-one-main

Description: page has no main landmark

Count of instances: 1

Issue: primary heading not h1

Impact: User cannot understand the topic of the document

WCAG: 1.3.1

Score: 62

Elements

Violations of wax rules

Rule ^The heading structure is not logically nested. This h. element appears to be the primary document heading, so should be an h1 element.+$

Description: Apparent primary document heading is not h1

Count of instances: 1

Issue: overflow hidden?

Impact: User may be unable to enlarge the text for readability

WCAG: 1.4.4

Score: 54

Elements

Violations of qualWeb rules

Rule QW-ACT-R40

Description: Zoomed text node may be clipped by a CSS overflow declaration

Count of instances: 54

Issue: link element invalid

Impact: Document fails to get a needed external resource

WCAG: 1.3.1

Score: 48

Elements

None identified

Violations of htmlcs rules

Rule AAA.2_4_8.H59.1

Description: Element is not in the document head

Count of instances: 12

Violations of wax rules

Rule Link elements can only be located in the head section of the document.

Description: link element is not located in the head element

Count of instances: 12

Issue: skip method missing or invalid

Impact: Keyboard-only user cannot easily reach the specific content of the document

WCAG: 2.4.1

Score: 48

Elements

None identified

Violations of wax rules

Rule Ensure that any common navigation elements can be bypassed; for instance, by use of skip links, header elements, or ARIA landmark roles.

Description: Page provides no way to quickly navigate to the main content

Count of instances: 1

Issue: links named identically

Impact: User cannot get help differentiating links

WCAG: 2.4.4

Score: 40

Elements

Violations of aslint rules

Rule links_same_content_different_url

Description: Links with the same text content have different destination URLs

Count of instances: 20

Violations of testaro rules

Rule linkAmb

Description: Links with the same text content have different destinations

Count of instances: 5

Issue: role assigned instead of implicit

Impact: User may misunderstand the purpose of an item

WCAG: 4.1.2

Score: 39

Elements

Violations of testaro rules

Rule role

Description: Explicitly assigned ARIA role is also an implicit element role

Count of instances: 39

Issue: target small

Impact: User cannot reliably choose an item to click or tap

WCAG: 2.5.5

Score: 38

Elements

Violations of alfa rules

Rule r111

Description: Target size is suboptimal

Count of instances: 38

Violations of testaro rules

Rule targetSize

Description: Button, input, or non-inline link is smaller than 44 px wide and high

Count of instances: 34

Issue: heading structure illogical

Impact: Helper misdescribes the document

WCAG: 1.3.1

Score: 38

Elements

Violations of aslint rules

Rule headings_hierarchy

Description: Heading level is illogical in its context

Count of instances: 19

Violations of htmlcs rules

Rule AAA.1_3_1_AAA.G141

Description: Heading level is incorrect

Count of instances: 9

Issue: focus indication poor

Impact: Keyboard-only user cannot choose an item to operate

WCAG: 2.4.7

Score: 32

Elements

Violations of testaro rules

Rule focInd

Description: Focused element displays a nonstandard or no focus indicator

Count of instances: 8

Issue: image dubiously marked decorative

Impact: Helper ignores an image that is apparently informative

WCAG: 1.1.1

Score: 31

Elements

Violations of htmlcs rules

Rule AAA.1_1_1.H67.2

Description: Image marked as decorative may be informative

Count of instances: 31

Issue: large visible-element count

Impact: User cannot easily find items in the document

WCAG: 2.4

Score: 31

Elements

Violations of testaro rules

Rule bulk

Description: Page contains many visible elements

Count of instances: 1

Issue: link not named

Impact: User cannot get help understanding what a link points to

WCAG: 2.4.4

Score: 28

Elements

Violations of alfa rules

Rule r11

Description: Link has no accessible name

Count of instances: 7

Violations of axe rules

Rule link-name

Description: Link has no discernible text

Count of instances: 7

Violations of ibm rules

Rule a_text_purpose

Description: Hyperlink has no link text, label, or image with a text alternative

Count of instances: 7

Violations of qualWeb rules

Rule QW-ACT-R12

Description: Link has no accessible name

Count of instances: 7

Issue: link not named

Impact: User cannot get help understanding what a link points to

WCAG: 2.4.4

Score: 28

Elements

Violations of aslint rules

Rule img_empty_alt_in_link

Description: Element is an image in a link but has no text alternative

Count of instances: 7

Violations of ed11y rules

Rule altEmptyLinked

Description: Link name is only an image with no text alternative

Count of instances: 7

Violations of htmlcs rules

Rule AAA.1_1_1.H30.2

Description: img element is the only link content but has no text alternative

Count of instances: 7

Violations of qualWeb rules

Rule QW-WCAG-T21

Description: Accessible name is not provided for an image which is the only content in a link

Count of instances: 7

Violations of wave rules

Rule alt_link_missing

Description: Linked image has no text alternative

Count of instances: 7

Violations of wax rules

Rule Img element is the only content of the link, but is missing alt text. The alt text should describe the purpose of the link.

Description: Link content is an image without a text alternative describing the link purpose

Count of instances: 7

Issue: all-capital text

Impact: Text is difficult to read

WCAG: 3.1.5

Score: 22

Elements

Violations of aslint rules

Rule capital_letters_words

Description: Element or its title has entirely upper-case words

Count of instances: 22

Violations of testaro rules

Rule allCaps

Description: Element has a text substring of at least 8 upper-case characters

Count of instances: 1

Issue: iframe not named

Impact: User cannot get help on the topic of an embedded document

WCAG: 4.1.2

Score: 20

Elements

Violations of aslint rules

Rule title_iframe

Description: Element is an iframe or object but its title attribute is missing or empty

Count of instances: 5

Violations of htmlcs rules

Rule AAA.2_4_1.H64.1

Description: iframe element has no non-empty title attribute

Count of instances: 1

Violations of wax rules

Rule Provide accessible names for