Accessibility digest

Contents

Synopsis
PagePhillip Anderson;Disrupt The Corruption Party;Wisconsin
URLhttps://www.andersonforussenate.com
Test date2024/09/22
Score2094
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-2i.json

Introduction

How accessible is the Phillip Anderson;Disrupt The Corruption Party;Wisconsin web page at https://www.andersonforussenate.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 2094, the sum of 640 for the count of issues, 1075 for specific issues, 0 for unclassified rule violations, 179 for tool-by-tool ratings, 152 for the count of violating elements, 0 for the page preventing tools from running, 48 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
not exactly 1 h1 heading1.3.12124nuVal:2, aslint:0, axe:0, wave:0
contrast poor1.4.34100axe:25, ibm:13, qualWeb:13, wax:14, alfa:0, aslint:0, htmlcs:0, wave:0
focus indication poor2.4.7492testaro:23, alfa:0, aslint:0
error reference invalid3.3.1468qualWeb:17, ibm:0
main missing1.3.6262axe:1
page content moves spontaneously2.2.2262testaro:1, aslint:0
void element has trailing slash4.1157nuVal:57
link indication poor1.3.3244axe:4, testaro:22, alfa:0
image dubiously named1.1.1140qualWeb:40, aslint:0, wave:0
target small2.5.5134alfa:12, testaro:34
control not named4.1.2432wax:8, alfa:0, axe:0, htmlcs:0, ibm:0, qualWeb:0, wave:0
large visible-element count2.4131testaro:1
overflow hidden?1.4.4127qualWeb:27
line height low1.4.8220alfa:10, testaro:1
button not named4.1.2420aslint:5, alfa:0, axe:0, htmlcs:0, nuVal:0, qualWeb:0, wave:0, wax:0
text contrast improvable1.4.6117aslint:17, axe:1, htmlcs:13, qualWeb:14, wax:15, alfa:0
attribute obsolete4.1315aslint:2, nuVal:5, htmlcs:0, ibm:0, testaro:0, wave:0
type redundant1.3.1115nuVal:15
text contrast not testable1.4.3113htmlcs:13, alfa:0, aslint:0
iframe not named4.1.2412aslint:1, htmlcs:1, wax:3, alfa:0, axe:0, ibm:0, qualWeb:0
title attribute invalid1.3.1412testaro:3
all-italic text3.1.5111testaro:11, alfa:0, aslint:0
links named identically2.4.4210aslint:5, qualWeb:2, testaro:2
visible label not in name2.5.339alfa:1, axe:1, htmlcs:1, ibm:1, qualWeb:3
no role-required name4.1.248ibm:2, wax:0
fieldset missing1.3.128ibm:4, testaro:0, wave:0
attribute value invalid1.3.148nuVal:2, ibm:0, wax:0
attribute invalid1.3.148nuVal:2, aslint:0, axe:0, ibm:0, wax:0
autocomplete missing1.3.548testaro:4
operable element not focusable2.1.148testaro:2
heading structure illogical1.3.126aslint:3, htmlcs:1
nav links not list1.3.126htmlcs:3
role assigned instead of implicit4.1.216testaro:6
inconsistent heading, link, or button styles3.2.416testaro:6
tab-opening link action unstated3.2.535ed11y:3
z-index not zero1.415testaro:5
fieldset missing?1.3.114aslint:4, htmlcs:1, wax:1
custom button keyboard-inoperable?2.1.114aslint:4
table misused1.3.124qualWeb:2, testaro:1, wave:0
semantic properties represented with styles1.3.124wax:2, htmlcs:0
tab-opening link action unstated?3.2.513aslint:3, htmlcs:3, testaro:3
link destination not URL1.3.113aslint:3
table headers missing1.3.133aslint:1, ed11y:1, ibm:1
position sticky1.4.1013htmlcs:3, aslint:0
code obsolete4.133ibm:1, nuVal:0
content beyond landmarks1.3.613ibm:1, wax:3, alfa:0, axe:0
role invalid4.1.233ibm:1, alfa:0, aslint:0, axe:0, nuVal:0, qualWeb:0
table not marked as such1.3.133qualWeb:1
font size absolute1.4.423qualWeb:2, alfa:0
element reloads or redirects2.2.133wave:1, aslint:0, qualWeb:0
heading level skipped1.3.122alfa:1, axe:1, ed11y:1, wave:0, wax:0
link incomplete1.3.122htmlcs:1, wax:1
justification undefined?1.4.812qualWeb:2
text distortion3.1.512testaro:2
title attribute redundant1.3.112testaro:2, aslint:0, qualWeb:0, wave:0
heading names repeated1.3.122wax:1, aslint:0, testaro:0
item makes testing inconclusive4.111alfa:1
hr misused1.3.111aslint:1, testaro:1
link name vague2.4.411aslint:1, ed11y:1, wave:0
table caption missing1.3.111aslint:1, qualWeb:1, axe:0, htmlcs:0, wave:0
links dubiously share name2.4.411axe:1
link to non-web resource1.3.311ed11y:1, testaro:0, wave:0
image dubiously marked decorative1.1.111htmlcs:1
noscript element not equivalent?4.111wave:1

Itemized issues

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

Issue: not exactly 1 h1 heading

Impact: User cannot understand the topic of the document

WCAG: 1.3.1

Score: 124

Elements

None identified

Violations of nuVal rules

Rule Consider using the h1 element as a top-level heading only (all h1 elements are treated as top-level headings by many screen readers and other tools).

Description: Page contains more than 1 h1 element

Count of instances: 2

Issue: contrast poor

Impact: Content is difficult to understand

WCAG: 1.4.3

Score: 100

Elements

None identified

Violations of axe rules

Rule color-contrast

Description: Element has insufficient color contrast

Count of instances: 25

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: 13

Violations of qualWeb rules

Rule QW-ACT-R37

Description: Text has less than the minimum contrast

Count of instances: 13

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: 14

Issue: focus indication poor

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

WCAG: 2.4.7

Score: 92

Elements

Violations of testaro rules

Rule focInd

Description: Focused element displays a nonstandard or no focus indicator

Count of instances: 23

Issue: error reference invalid

Impact: User cannot correct a form error

WCAG: 3.3.1

Score: 68

Elements

None identified

Violations of qualWeb rules

Rule QW-ACT-R41

Description: Error message describes no invalid form field value

Count of instances: 17

Issue: main missing

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

WCAG: 1.3.6

Score: 62

Elements

None identified

Violations of axe rules

Rule landmark-one-main

Description: page has no main landmark

Count of instances: 1

Issue: page content moves spontaneously

Impact: Motion-sensitive user may suffer harm

WCAG: 2.2.2

Score: 62

Elements

None identified

Violations of testaro rules

Rule motion

Description: Change of visible content not requested by user

Count of instances: 1

Issue: void element has trailing slash

Impact: Document contains invalid code

WCAG: 4.1

Score: 57

Elements

None identified

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: 57

Issue: link indication poor

Impact: User cannot differentiate a link from plain text

WCAG: 1.3.3

Score: 44

Elements

Violations of axe rules

Rule link-in-text-block

Description: Element is not distinct from surrounding text without reliance on color

Count of instances: 4

Violations of testaro rules

Rule linkUl

Description: Inline links are not underlined

Count of instances: 22

Issue: image dubiously named

Impact: Helper may describe an image inadequately

WCAG: 1.1.1

Score: 40

Elements

None identified

Violations of qualWeb rules

Rule QW-WCAG-T8

Description: Text alternative is suspect

Count of instances: 40

Issue: target small

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

WCAG: 2.5.5

Score: 34

Elements

Violations of alfa rules

Rule r111

Description: Target size is suboptimal

Count of instances: 12

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: control not named

Impact: User cannot get help on how to operate a form item

WCAG: 4.1.2

Score: 32

Elements

None identified

Violations of wax rules

Rule Ensure form elements have associated labels.

Description: Form control element has no label

Count of instances: 8

Issue: large visible-element count

Impact: User cannot easily find items in the document

WCAG: 2.4

Score: 31

Elements

None identified

Violations of testaro rules

Rule bulk

Description: Page contains many visible elements

Count of instances: 1

Issue: overflow hidden?

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

WCAG: 1.4.4

Score: 27

Elements

None identified

Violations of qualWeb rules

Rule QW-ACT-R40

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

Count of instances: 27

Issue: line height low

Impact: Text is difficult to read

WCAG: 1.4.8

Score: 20

Elements

Violations of alfa rules

Rule r73

Description: Text line height is not at least 1.5

Count of instances: 10

Violations of testaro rules

Rule lineHeight

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

Count of instances: 1

Issue: button not named

Impact: User cannot get help explaing a button

WCAG: 4.1.2

Score: 20

Elements

None identified

Violations of aslint rules

Rule empty_button_description

Description: button element has no visible accessible name

Count of instances: 5

Issue: text contrast improvable

Impact: Content is not easy to understand

WCAG: 1.4.6

Score: 17

Elements

None identified

Violations of aslint rules

Rule color_contrast_aaa7

Description: Text has contrast less than 7:1

Count of instances: 17

Violations of axe rules

Rule color-contrast-enhanced

Description: Element has insufficient color contrast (Level AAA)

Count of instances: 1

Violations of htmlcs rules

Rule AAA.1_4_6.G17.Fail

Description: Text has insufficient contrast

Count of instances: 13

Violations of qualWeb rules

Rule QW-ACT-R76

Description: Text has less than the enhanced minimum contrast

Count of instances: 14

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: 15

Issue: attribute obsolete

Impact: Document includes obsolete code that the browser may fail to process

WCAG: 4.1

Score: 15

Elements

None identified

Violations of aslint rules

Rule obsolete_html_attributes

Description: Element has an obsolete attribute

Count of instances: 2

Violations of nuVal rules

Rule ^The .+ attribute on the .+ element is obsolete.*$

Description: Attribute is obsolete on its element

Count of instances: 5

Issue: type redundant

Impact: Document includes unnecessary code

WCAG: 1.3.1

Score: 15

Elements

None identified

Violations of nuVal rules

Rule The type attribute is unnecessary for JavaScript resources.

Description: type attribute is unnecessary for a JavaScript resource

Count of instances: 15

Issue: text contrast not testable

Impact: Text may be difficult to read

WCAG: 1.4.3

Score: 13

Elements

None identified

Violations of htmlcs rules

Rule AAA.1_4_6.G17.Abs

Description: Contrast between the absolutely positioned text and its background may be less than 7:1

Count of instances: 13

Issue: iframe not named

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

WCAG: 4.1.2

Score: 12

Elements

None identified

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: 1

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 Iframe element requires a non-empty title attribute that identifies the frame.

Description: iframe element has no title attribute identifying it

Count of instances: 3

Issue: title attribute invalid

Impact: User cannot hover to get help explaining an item

WCAG: 1.3.1

Score: 12

Elements

Violations of testaro rules

Rule titledEl

Description: title attribute belongs to an inappropriate element

Count of instances: 3

Issue: all-italic text

Impact: Text is difficult to read

WCAG: 3.1.5

Score: 11

Elements

Violations of testaro rules

Rule allSlanted

Description: Element has a text substring of at least 40 italic or oblique characters

Count of instances: 11

Issue: links named identically

Impact: User cannot get help differentiating links

WCAG: 2.4.4

Score: 10

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: 5

Violations of qualWeb rules

Rule QW-ACT-R9

Description: Links with identical accessible names have different purposes

Count of instances: 2

Violations of testaro rules

Rule linkAmb

Description: Links with the same text content have different destinations

Count of instances: 2

Issue: visible label not in name

Impact: User cannot get help choosing a form control to operate

WCAG: 2.5.3

Score: 9

Elements

None identified

Violations of alfa rules

Rule r14

Description: Visible label is not in the accessible name

Count of instances: 1

Violations of axe rules

Rule label-content-name-mismatch

Description: Element visible text is not part of its accessible name

Count of instances: 1

Violations of htmlcs rules

Rule AAA.2_5_3.F96

Description: Visible label is not in the accessible name

Count of instances: 1

Violations of ibm rules

Rule label_name_visible

Description: Accessible name does not match or contain the visible label text

Count of instances: 1

Violations of qualWeb rules

Rule QW-ACT-R30

Description: Visible label is not part of the accessible name

Count of instances: 3

Issue: no role-required name

Impact: User cannot get help understanding an item

WCAG: 4.1.2

Score: 8

Elements

None identified

Violations of ibm rules

Rule aria_accessiblename_exists

Description: Element has no accessible name, although its role requires one

Count of instances: 2

Issue: fieldset missing

Impact: User cannot get help recognizing a group of related form items

WCAG: 1.3.1

Score: 8

Elements

None identified

Violations of ibm rules

Rule input_checkboxes_grouped

Description: checkbox input is not grouped with others with the same name

Count of instances: 4

Issue: attribute value invalid

Impact: Item behaves improperly

WCAG: 1.3.1

Score: 8

Elements

None identified

Violations of nuVal rules

Rule ^Bad value .* for attribute .+ on element .+$

Description: Attribute on this element has an invalid value

Count of instances: 2

Issue: attribute invalid

Impact: Item behaves improperly

WCAG: 1.3.1

Score: 8

Elements

None identified

Violations of nuVal rules

Rule ^Attribute .+ not allowed on element .+ at this point.*$

Description: Attribute not allowed on this element

Count of instances: 2

Issue: autocomplete missing

Impact: User cannot get help entering personal information in a form

WCAG: 1.3.5

Score: 8

Elements

Violations of testaro rules

Rule autocomplete

Description: Name or email input is missing its required autocomplete attribute

Count of instances: 4

Issue: operable element not focusable

Impact: Keyboard-only user cannot navigate properly to an operable item

WCAG: 2.1.1

Score: 8

Elements

Violations of testaro rules

Rule opFoc

Description: Operable element is not Tab-focusable

Count of instances: 2

Issue: heading structure illogical

Impact: Helper misdescribes the document

WCAG: 1.3.1

Score: 6

Elements

None identified

Violations of aslint rules

Rule headings_hierarchy

Description: Heading level is illogical in its context

Count of instances: 3

Violations of htmlcs rules

Rule AAA.1_3_1_AAA.G141

Description: Heading level is incorrect

Count of instances: 1

Issue: nav links not list

Impact: User cannot get help recognizing a list of navigation links

WCAG: 1.3.1

Score: 6

Elements

None identified

Violations of htmlcs rules

Rule AAA.1_3_1.H48

Description: Navigation links are not coded as a list

Count of instances: 3

Issue: role assigned instead of implicit

Impact: User may misunderstand the purpose of an item

WCAG: 4.1.2

Score: 6

Elements

Violations of testaro rules

Rule role

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

Count of instances: 6

Issue: inconsistent heading, link, or button styles

Impact: User cannot easily distinguish items of different types

WCAG: 3.2.4

Score: 6

Elements

None identified

Violations of testaro rules

Rule styleDiff

Description: Heading, link, and button style inconsistencies

Count of instances: 6

Issue: tab-opening link action unstated

Impact: Following a link opens a new window, surprising a user

WCAG: 3.2.5

Score: 5

Elements

Violations of ed11y rules

Rule linkNewWindow

Description: Link opens a new window or tab without prior notice

Count of instances: 3

Issue: z-index not zero

Impact: User cannot predict the effect of clicking

WCAG: 1.4

Score: 5

Elements

Violations of testaro rules

Rule zIndex

Description: Element has a nondefault z-index value

Count of instances: 5

Issue: fieldset missing?

Impact: User may be unable to get help recognizing a group of related form items

WCAG: 1.3.1

Score: 4

Elements

None identified

Violations of aslint rules

Rule group_elements_name_attribute

Description: Element is an input with a name attribute but has no fieldset parent

Count of instances: 4

Violations of htmlcs rules

Rule AAA.1_3_1.H71.SameName

Description: Radio buttons or check boxes may require a group description via a fieldset element

Count of instances: 1

Violations of wax rules

Rule If these radio buttons or check boxes require a further group-level description, they should be contained within a fieldset element.

Description: Radio buttons or check boxes may require a group description via a fieldset element

Count of instances: 1

Issue: custom button keyboard-inoperable?

Impact: Custom item may prevent a keyboard-only user from operating it

WCAG: 2.1.1

Score: 4

Elements

None identified

Violations of aslint rules

Rule link_button_space_key

Description: Element has a button role but may fail to be keyboard-operable

Count of instances: 4

Issue: table misused

Impact: Helper misinforms a user about whether items are cells of a table

WCAG: 1.3.1

Score: 4

Elements

Violations of qualWeb rules

Rule QW-WCAG-T12

Description: th or caption element or non-empty summary attribute used in a layout table

Count of instances: 1

Rule QW-BP9

Description: Table element without header cells has a caption

Count of instances: 1

Violations of testaro rules

Rule nonTable

Description: table element fails the structural requirements for tabular data

Count of instances: 1

Issue: semantic properties represented with styles

Impact: User cannot get help to fully understand the text

WCAG: 1.3.1

Score: 4

Elements

None identified

Violations of wax rules

Rule Semantic markup should be used to mark emphasised or special text so that it can be programmatically determined.

Description: Special text is designated with styles instead of semantically

Count of instances: 2

Issue: tab-opening link action unstated?

Impact: Following a link opens a new window, possibly surprising a user

WCAG: 3.2.5

Score: 3

Elements

Violations of aslint rules

Rule links_new_window_mark

Description: Indicator that the link opens a new window or tab may be missing

Count of instances: 3

Violations of htmlcs rules

Rule AAA.3_2_5.H83.3

Description: Link text may fail to indicate that the link will open in a new window

Count of instances: 3

Violations of testaro rules

Rule linkExt

Description: Link opens a new window or tab

Count of instances: 3

Issue: link destination not URL

Impact: Helper cannot properly explain a link to a user

WCAG: 1.3.1

Score: 3

Elements

None identified

Violations of aslint rules

Rule unclear_anchor_uri

Description: Link destination is #, a script, or empty

Count of instances: 3

Issue: table headers missing

Impact: User cannot get help on relationships in a table

WCAG: 1.3.1

Score: 3

Elements

Violations of aslint rules

Rule table_row_and_column_headersRC

Description: None of the cells in the table is a header

Count of instances: 1

Violations of ed11y rules

Rule tableNoHeaderCells

Description: None of the cells in the table is a th element

Count of instances: 1

Violations of ibm rules

Rule table_headers_exists

Description: No cell in the table is a th element or has a scope or headers attribute

Count of instances: 1

Issue: position sticky

Impact: User may be unable to see needed content or may be forced to scroll in both dimensions

WCAG: 1.4.10

Score: 3

Elements

None identified

Violations of htmlcs rules

Rule AAA.1_4_10.C32,C31,C33,C38,SCR34,G206

Description: Fixed-position element may force bidirectional scrolling

Count of instances: 3

Issue: code obsolete

Impact: Document contains code that is no longer standard

WCAG: 4.1

Score: 3

Elements

None identified

Violations of ibm rules

Rule element_attribute_deprecated

Description: Element or attribute is obsolete

Count of instances: 1

Issue: content beyond landmarks

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

WCAG: 1.3.6

Score: 3

Elements

None identified

Violations of ibm rules

Rule aria_content_in_landmark

Description: Content is not within a landmark element

Count of instances: 1

Violations of wax rules

Rule Use landmarks to contain page content.

Description: Content is not within a landmark element

Count of instances: 3

Issue: role invalid

Impact: User cannot get help on the nature of an item

WCAG: 4.1.2

Score: 3

Elements

None identified

Violations of ibm rules

Rule aria_contentinfo_misuse

Description: Element with a contentinfo role is present without an element with a main role

Count of instances: 1

Issue: table not marked as such

Impact: Helper misinforms a user about whether items are cells of a table

WCAG: 1.3.1

Score: 3

Elements

None identified

Violations of qualWeb rules

Rule QW-WCAG-T18

Description: Table markup not used to present tabular information

Count of instances: 1

Issue: font size absolute

Impact: User cannot adjust the text size for readability

WCAG: 1.4.4

Score: 3

Elements

None identified

Violations of qualWeb rules

Rule QW-WCAG-T28

Description: Font size set to an absolute unit value

Count of instances: 2

Issue: element reloads or redirects

Impact: Document change may surprise a user

WCAG: 2.2.1

Score: 3

Elements

None identified

Violations of wave rules

Rule meta_refresh

Description: Page refreshes or redirects

Count of instances: 1

Issue: heading level skipped

Impact: Helper misdescribes the document

WCAG: 1.3.1

Score: 2

Elements

Violations of alfa rules

Rule r53

Description: Heading skips one or more levels

Count of instances: 1

Violations of axe rules

Rule heading-order

Description: Heading levels do not increase by only one or their order is ambiguous

Count of instances: 1

Violations of ed11y rules

Rule headingLevelSkipped

Description: Heading level is more than 1 greater than that of the previous heading

Count of instances: 1

Issue: link incomplete

Impact: User may fail to reach a promised location

WCAG: 1.3.1

Score: 2

Elements

None identified

Violations of htmlcs rules

Rule AAA.4_1_2.H91.A.Placeholder

Description: Link has text but no href, id, or name attribute

Count of instances: 1

Violations of wax rules

Rule Anchor element found with link content, but no href, ID or name attribute has been supplied.

Description: Link has text but no href, id, or name attribute

Count of instances: 1

Issue: justification undefined?

Impact: Text may be difficult to read

WCAG: 1.4.8

Score: 2

Elements

None identified

Violations of qualWeb rules

Rule QW-WCAG-T29

Description: Alignment either to the left or right is not specified in CSS

Count of instances: 2

Issue: text distortion

Impact: Text is difficult to read

WCAG: 3.1.5

Score: 2

Elements

Violations of testaro rules

Rule distortion

Description: Element text is distorted by a transform style property

Count of instances: 2

Issue: title attribute redundant

Impact: Helper repeats the explanation of an item

WCAG: 1.3.1

Score: 2

Elements

Violations of testaro rules

Rule linkTitle

Description: Link title value is also contained in the link text

Count of instances: 2

Issue: heading names repeated

Impact: User cannot differentiate parts of the document

WCAG: 1.3.1

Score: 2

Elements

None identified

Violations of wax rules

Rule ^The heading structure is not logically nested. This h. element should be an h. to be properly nested.+$

Description: Heading level is illogical

Count of instances: 1

Issue: item makes testing inconclusive

Impact: Item prevents a conclusive accessibility test

WCAG: 4.1

Score: 1

Elements

None identified

Violations of alfa rules

Rule cantTell

Description: Test could not give a conclusive result

Count of instances: 1

Issue: hr misused

Impact: User cannot get help on the nature of segments of the document

WCAG: 1.3.1

Score: 1

Elements

Violations of aslint rules

Rule horizontal_rule

Description: hr element has neither a true aria-hidden attribute nor a presentation role

Count of instances: 1

Violations of testaro rules

Rule hr

Description: hr instead of styles is used for vertical segmentation

Count of instances: 1

Issue: link name vague

Impact: User may misunderstand what a link points to

WCAG: 2.4.4

Score: 1

Elements

Violations of aslint rules

Rule link_with_unclear_purpose

Description: Element is a link but has vague or generic content

Count of instances: 1

Violations of ed11y rules

Rule linkTextIsGeneric

Description: Element is a link but has generic content

Count of instances: 1

Issue: table caption missing

Impact: User cannot get help on the topic of a table

WCAG: 1.3.1

Score: 1

Elements

None identified

Violations of aslint rules

Rule table_missing_descriptionC

Description: Element contains no caption element

Count of instances: 1

Violations of qualWeb rules

Rule QW-WCAG-T2

Description: caption element not used to associate a caption with a data table

Count of instances: 1

Issue: links dubiously share name

Impact: User may be unable to get help differentiating links

WCAG: 2.4.4

Score: 1

Elements

None identified

Violations of axe rules

Rule identical-links-same-purpose

Description: Links with the same accessible name may serve dissimilar purposes

Count of instances: 1

Issue: link to non-web resource

Impact: Document points to harder-to-use resources

WCAG: 1.3.3

Score: 1

Elements

Violations of ed11y rules

Rule linkDocument

Description: Element links to a PDF, Word, PowerPoint, or Google Docs document

Count of instances: 1

Issue: image dubiously marked decorative

Impact: Helper ignores an image that is apparently informative

WCAG: 1.1.1

Score: 1

Elements

None identified

Violations of htmlcs rules

Rule AAA.1_1_1.H67.2

Description: Image marked as decorative may be informative

Count of instances: 1

Issue: noscript element not equivalent?

Impact: User who has disabled JavaScript may be denied some content

WCAG: 4.1

Score: 1

Elements

None identified

Violations of wave rules

Rule noscript

Description: noscript element may fail to contain an accessible equivalent or alternative

Count of instances: 1

Elements with issues

Elements exhibiting issues:

Element /html/body/a
Element /html/body/footer/div/div[1]/div/div/p[2]/a
Element /html/body/footer/div/div[1]/div/div/p[3]/a
Element /html/body/footer/div/div[1]/div/div/p[4]/a
Element /html/body/footer/div/div[1]/div/div/table
Element /html/body/footer/div/div[1]/div/hr
Element /html/body/footer/div/div[2]/div/div[2]/a[1]
Element /html/body/footer/div/div[2]/div/div[2]/a[2]
Element /html/body/footer/div/div[2]/div/div[2]/a[3]
Element /html/body/footer/div/div[2]/div/div[3]/a
Element /html/body/header
Element /html/body/header/div/a
Element /html/body/header/div/button
Element /html/body/header/div/div/h1/a
Element /html/body/header/div/nav/ul[1]/li[1]/a
Element /html/body/header/div/nav/ul[1]/li[2]/a
Element /html/body/header/div/nav/ul[1]/li[3]/a
Element /html/body/header/div/nav/ul[1]/li[4]/a
Element /html/body/header/div/nav/ul[1]/li[6]/a
Element /html/body/header/div/nav/ul[1]/li[7]/a
Element /html/body/header/div/nav/ul[1]/li[8]/a
Element /html/body/header/div/nav/ul[1]/li[9]/a
Element /html/body/header/div/nav/ul[2]/li[1]/a
Element /html/body/header/div/nav/ul[2]/li[2]/a
Element /html/body/section[1]/div[1]
Element /html/body/section[1]/div[3]/a[1]
Element /html/body/section[1]/div[3]/a[2]
Element /html/body/section[1]/div[3]/div/div[1]/a
Element /html/body/section[1]/div[3]/ol
Element /html/body/section[1]/div[3]/ol/li[4]
Element /html/body/section[1]/div[3]/ol/li[5]
Element /html/body/section[1]/div[4]/div/div/div/div/p[2]/span/a[1]
Element /html/body/section[1]/div[4]/div/div/div/div/p[2]/span/a[2]
Element /html/body/section[1]/div[4]/div/div/div/div/p[2]/span/a[3]
Element /html/body/section[1]/div[4]/div/div/div/div/p[2]/span/a[4]
Element /html/body/section[1]/div[4]/div/div/div/div/p[3]/span[1]/a
Element /html/body/section[1]/div[4]/div/div/div/div/p[3]/span[4]/a
Element /html/body/section[1]/div[4]/div/div/div/div/p[4]/a
Element /html/body/section[1]/div[4]/div/div/div/div/p[5]/a
Element /html/body/section[1]/div[4]/div/div/div/div/p[6]/img
Element /html/body/section[1]/section/div/div/div/div[1]/div[2]/div[1]/div[2]/div[2]/div
Element /html/body/section[1]/section/div/div/div/div[1]/div[2]/div[2]/div[1]/div[2]/div
Element /html/body/section[1]/section/div/div/div/div[1]/div[2]/div[2]/div[1]/div[2]/div/div
Element /html/body/section[1]/section/div/div/div/div[1]/div[2]/div[2]/div[2]/div[2]/div
Element /html/body/section[1]/section/div/div/div/div[1]/div[2]/div[2]/div[2]/div[2]/div/div
Element /html/body/section[1]/section/div/div/div/div[1]/div[2]/div[2]/div[3]/div[2]/div
Element /html/body/section[1]/section/div/div/div/div[1]/div[2]/div[3]/div[1]/div[2]/div/div
Element /html/body/section[1]/section/div/div/div/div[1]/div[2]/div[4]/div[2]/div[2]/div
Element /html/body/section[1]/section/div/div/div/div[1]/div[2]/div[5]/div[1]/div[2]/div/div
Element /html/body/section[1]/section/div/div/div/div[1]/div[2]/div[5]/div[2]/div[2]/div/div
Element /html/body/section[1]/section/div/div/div/div[1]/div[2]/div[6]/div[2]/div[2]/div
Element /html/body/section[1]/section/div/div/div/div[2]/form/div[14]/div/input[1]
Element /html/body/section[1]/section/div/div/div/div[2]/form/div[14]/div/input[2]
Element /html/body/section[1]/section/div/div/div/div[2]/form/div[1]/p/input
Element /html/body/section[1]/section/div/div/div/div[2]/form/div[3]/div/input
Element /html/body/section[1]/section/div/div/div/div[2]/form/div[4]/div/input
Element /html/body/section[1]/section/div/div/div/div[2]/form/div[5]/div/input
Element /html/body/section[1]/section/div/div/div/div[2]/form/div[6]/div/input
Element /html/body/section[1]/section/div/div/div/div[2]/form/div[7]/div[1]/div/input
Element /html/body/section[1]/section/div/div/div/div[2]/form/div[7]/div[2]/div/input
Element /html/body/section[1]/section/div/div/div/div[2]/form/div[8]/div[1]/div/input
Element /html/body/section[1]/section/div/div/div/div[2]/form/div[9]/div[1]/div/input[1]
Element /html/body/section[1]/section/div/div/div/div[2]/form/div[9]/div[1]/div/input[2]
Element /html/body/section[1]/section/div/div/div/div[2]/form/div[9]/div[2]/div/input[1]
Element /html/body/section[1]/section/div/div/div/div[2]/form/div[9]/div[2]/div/input[2]
Element /html/body/section[1]/section/div/div/div/div[2]/form/input[1]
Element /html/body/section[1]/section/div/div/div/div[2]/form/input[2]
Element /html/body/section[1]/section/div/div/div/div[2]/form/input[3]
Element /html/body/section[1]/section/div/div/div/div[2]/form/input[4]
Element /html/body/section[1]/section/div/div/div/h5
Element /html/body/section[2]
Element /html/body/section[2]/button
Element /html/body/section[2]/div
Element /html/body/section[2]/div/div/div/div[1]/div/div/a[1]
Element /html/body/section[2]/div/div/div/div[1]/div/div/a[2]
Element /html/body/section[2]/div/div/div/div[1]/div/div/a[3]