Accessibility digest

Contents

Synopsis
PagePatricia Morgan;Republican;Rhode Island
URLhttps://www.patriciamorgan.com
Test date2024/09/22
Score3971
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-1u.json

Introduction

How accessible is the Patricia Morgan;Republican;Rhode Island web page at https://www.patriciamorgan.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 3971, the sum of 750 for the count of issues, 2177 for specific issues, 0 for unclassified rule violations, 409 for tool-by-tool ratings, 520 for the count of violating elements, 0 for the page preventing tools from running, 115 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
CSS invalid4.13564nuVal:188
font small1.43156testaro:52, wave:4, alfa:0, aslint:0
not exactly 1 h1 heading1.3.12124nuVal:2, aslint:0, axe:0, wave:0
font size absolute1.4.42104alfa:18, qualWeb:65
line height low1.4.8296alfa:18, testaro:48
parent invalid1.3.1480nuVal:20, ibm:0
text contrast not testable1.4.3177alfa:77, htmlcs:13, aslint:0
contrast poor1.4.3468axe:17, htmlcs:1, qualWeb:8, alfa:0, aslint:0, ibm:0, wave:0, wax:0
operable element not focusable2.1.1456testaro:14
color missing1.4.3452qualWeb:13
attribute value invalid1.3.1448nuVal:12, ibm:0, wax:0
element not focusable2.1.1448testaro:24, alfa:0, qualWeb:0
skip method missing or invalid2.4.1348wax:1, axe:0, ibm:0, wave:0
void element has trailing slash4.1146nuVal:46
overflow hidden?1.4.4140qualWeb:40
text fully justified1.4.8236alfa:13, wave:18, qualWeb:0
attribute invalid1.3.1436axe:5, ibm:9, nuVal:8, aslint:0, wax:0
large visible-element count2.4131testaro:1
error reference invalid3.3.1428qualWeb:7, ibm:0
meta invalid1.3.1324nuVal:8
image has no src1.3.1424nuVal:6
focus indication poor2.4.7424testaro:6, alfa:0, aslint:0
item makes testing inconclusive4.1122alfa:22
image named with filename1.1.1321aslint:7, alfa:0, ed11y:0
aria attribute invalid4.1.2420alfa:5, axe:0, ibm:0, nuVal:0, qualWeb:0, wax:0
justification undefined?1.4.8118qualWeb:18
link element invalid1.3.1416htmlcs:4, wax:4, nuVal:0
text contrast improvable1.4.6115alfa:7, aslint:7, axe:11, htmlcs:7, qualWeb:15, wax:0
code obsolete4.1315ibm:5, nuVal:0
all-capital text3.1.5112aslint:12, ed11y:1, testaro:8, alfa:0
element closure invalid4.1.1312nuVal:4
text and image link not combined2.4.4212wave:6, aslint:0, qualWeb:0
image dubiously named1.1.1111qualWeb:11, wave:7, aslint:0
tab-opening link action unstated?3.2.5110aslint:10, htmlcs:10, testaro:10
section heading missing1.3.1110nuVal:10
dubious aria-label1.3.1110nuVal:10
link indication poor1.3.3210testaro:5, alfa:0, axe:0
hover indication poor3.3.239testaro:3
target small2.5.518alfa:3, testaro:8
line height absolute1.4.1228alfa:4
skip method missing or invalid?2.4.118alfa:1, qualWeb:0
links named identically2.4.428aslint:4, qualWeb:0, testaro:0
tab-opening link action unstated3.2.538ed11y:5
no role-required name4.1.248ibm:2, wax:0
autocomplete missing1.3.548testaro:4
title attribute invalid1.3.148testaro:2
form submission button missing3.2.236aslint:2, qualWeb:2, htmlcs:0
element reloads or redirects2.2.136qualWeb:2, aslint:0, wave:0
inconsistent heading, link, or button styles3.2.416testaro:6
heading-like styles dubious1.3.115wave:5, axe:0, ed11y:0, htmlcs:0
region not named4.1.244alfa:1, ibm:1
svg image not named1.1.144aslint:1, ibm:1, alfa:0, axe:0, qualWeb:0, wax:0
button not named4.1.244aslint:1, alfa:0, axe:0, htmlcs:0, nuVal:0, qualWeb:0, wave:0, wax:0
requirement invalid1.3.544aslint:1
iframe not named4.1.244wax:1, alfa:0, aslint:0, axe:0, htmlcs:0, ibm:0, qualWeb:0
checkbox input not named4.1.244wax:1
focusable element not active4.1.233axe:1, qualWeb:0
regions not distinctly named1.3.633ibm:1
role invalid4.1.233ibm:1, alfa:0, aslint:0, axe:0, nuVal:0, qualWeb:0
box size absolute1.4.433qualWeb:1
heading level skipped1.3.122alfa:1, axe:1, ed11y:1, wave:1, wax:0
heading heads nothing1.3.122alfa:1, wax:0
fieldset missing?1.3.112aslint:2, htmlcs:0, wax:0
heading structure illogical1.3.122aslint:1, htmlcs:1
type redundant1.3.112nuVal:2
underlining dubious1.3.112wave:2
heading names repeated1.3.122wax:1, aslint:0, testaro:0
labeling risky3.3.211aslint:1
tabindex redundant1.3.111aslint:1
position sticky1.4.1011aslint:1, htmlcs:1
content beyond landmarks1.3.611axe:1, ibm:1, alfa:0, wax:0
image dubiously marked decorative1.1.111htmlcs:1
aria attribute redundant4.1.211ibm:1, nuVal:0
z-index not zero1.411testaro:1
false aria-hidden value risky2.4.600aslint:9

Itemized issues

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

Issue: CSS invalid

Impact: Document cannot be properly displayed

WCAG: 4.1

Score: 564

Elements

None identified

Violations of nuVal rules

Rule CSS: Parse Error.

Description: Invalid CSS

Count of instances: 20

Rule ^CSS: .+: Property .+ doesn't exist.*$

Description: Invalid property in CSS

Count of instances: 10

Rule ^CSS: .+: Unknown dimension.*$

Description: Unknown CSS dimension

Count of instances: 2

Rule ^CSS: .+: .+ is not a .+ value.*$

Description: Invalid value in CSS

Count of instances: 30

Rule ^CSS: .+: .+ is not a valid color 3 or 6 hexadecimals numbers.*$

Description: Invalid hexadecimal color in CSS

Count of instances: 74

Rule ^CSS: .+: Parse Error.*$

Description: Invalid CSS

Count of instances: 52

Issue: font small

Impact: Text is difficult to read

WCAG: 1.4

Score: 156

Elements

Violations of testaro rules

Rule miniText

Description: Text node has a font smaller than 11 pixels

Count of instances: 52

Violations of wave rules

Rule text_small

Description: Text is very small

Count of instances: 4

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: font size absolute

Impact: User cannot adjust the text size for readability

WCAG: 1.4.4

Score: 104

Elements

Violations of alfa rules

Rule r74

Description: Paragraph text has an absolute font size

Count of instances: 18

Violations of qualWeb rules

Rule QW-WCAG-T28

Description: Font size set to an absolute unit value

Count of instances: 65

Issue: line height low

Impact: Text is difficult to read

WCAG: 1.4.8

Score: 96

Elements

Violations of alfa rules

Rule r73

Description: Text line height is not at least 1.5

Count of instances: 18

Violations of testaro rules

Rule lineHeight

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

Count of instances: 48

Issue: parent invalid

Impact: User cannot properly operate an item

WCAG: 1.3.1

Score: 80

Elements

None identified

Violations of nuVal rules

Rule ^Element .+ not allowed as child of element .+ in this context.*$

Description: Element has an invalid parent

Count of instances: 20

Issue: text contrast not testable

Impact: Text may be difficult to read

WCAG: 1.4.3

Score: 77

Elements

Violations of alfa rules

Rule cantTellTextContrast

Description: Test of text contrast could not give a conclusive result

Count of instances: 77

Violations of htmlcs rules

Rule AAA.1_4_3_F24.F24.FGColour

Description: Inline foreground color may lack a complementary background color

Count of instances: 7

Rule AAA.1_4_6.G18.Abs

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

Count of instances: 5

Rule AAA.1_4_6.G18.BgImage

Description: Contrast between the text and the background image may be less than 4.5:1

Count of instances: 1

Issue: contrast poor

Impact: Content is difficult to understand

WCAG: 1.4.3

Score: 68

Elements

Violations of axe rules

Rule color-contrast

Description: Element has insufficient color contrast

Count of instances: 17

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

Violations of qualWeb rules

Rule QW-ACT-R37

Description: Text has less than the minimum contrast

Count of instances: 8

Issue: operable element not focusable

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

WCAG: 2.1.1

Score: 56

Elements

Violations of testaro rules

Rule opFoc

Description: Operable element is not Tab-focusable

Count of instances: 14

Issue: color missing

Impact: Content is impossible to perceive under some conditions

WCAG: 1.4.3

Score: 52

Elements

Violations of qualWeb rules

Rule QW-WCAG-T31

Description: Foreground or background color is specified but not both

Count of instances: 13

Issue: attribute value invalid

Impact: Item behaves improperly

WCAG: 1.3.1

Score: 48

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

Issue: element not focusable

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

WCAG: 2.1.1

Score: 48

Elements

None identified

Violations of testaro rules

Rule focAll

Description: Discrepancy between elements that should be and that are Tab-focusable

Count of instances: 24

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

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: void element has trailing slash

Impact: Document contains invalid code

WCAG: 4.1

Score: 46

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

Issue: overflow hidden?

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

WCAG: 1.4.4

Score: 40

Elements

Violations of qualWeb rules

Rule QW-ACT-R40

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

Count of instances: 40

Issue: text fully justified

Impact: Text is difficult to read

WCAG: 1.4.8

Score: 36

Elements

Violations of alfa rules

Rule r71

Description: Paragraph text is fully justified

Count of instances: 13

Violations of wave rules

Rule text_justified

Description: Text is justified

Count of instances: 18

Issue: attribute invalid

Impact: Item behaves improperly

WCAG: 1.3.1

Score: 36

Elements

Violations of axe rules

Rule aria-prohibited-attr

Description: Element has an attribute that is not valid for the role of the element

Count of instances: 5

Violations of ibm rules

Rule aria_attribute_valid

Description: ARIA attribute is invalid for the role of its element

Count of instances: 9

Violations of nuVal rules

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

Description: Attribute not allowed on this element

Count of instances: 8

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: error reference invalid

Impact: User cannot correct a form error

WCAG: 3.3.1

Score: 28

Elements

None identified

Violations of qualWeb rules

Rule QW-ACT-R41

Description: Error message describes no invalid form field value

Count of instances: 7

Issue: meta invalid

Impact: Document fails to include needed data

WCAG: 1.3.1

Score: 24

Elements

None identified

Violations of nuVal rules

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

Description: Attribute of a meta element has an invalid value

Count of instances: 8

Issue: image has no src

Impact: Image to be shown cannot be found

WCAG: 1.3.1

Score: 24

Elements

None identified

Violations of nuVal rules

Rule Element img is missing required attribute src.

Description: img element has no src attribute

Count of instances: 6

Issue: focus indication poor

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

WCAG: 2.4.7

Score: 24

Elements

Violations of testaro rules

Rule focInd

Description: Focused element displays a nonstandard or no focus indicator

Count of instances: 6

Issue: item makes testing inconclusive

Impact: Item prevents a conclusive accessibility test

WCAG: 4.1

Score: 22

Elements

Violations of alfa rules

Rule cantTell

Description: Test could not give a conclusive result

Count of instances: 22

Issue: image named with filename

Impact: Helper gives a user the filename of an image instead of describing it

WCAG: 1.1.1

Score: 21

Elements

Violations of aslint rules

Rule alt_text_include_filename

Description: Image text alternative includes a filename

Count of instances: 7

Issue: aria attribute invalid

Impact: Item behavior violates user expectations

WCAG: 4.1.2

Score: 20

Elements

Violations of alfa rules

Rule r18

Description: ARIA state or property is not allowed for the element on which it is specified

Count of instances: 5

Issue: justification undefined?

Impact: Text may be difficult to read

WCAG: 1.4.8

Score: 18

Elements

Violations of qualWeb rules

Rule QW-WCAG-T29

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

Count of instances: 18

Issue: link element invalid

Impact: Document fails to get a needed external resource

WCAG: 1.3.1

Score: 16

Elements

Violations of htmlcs rules

Rule AAA.2_4_8.H59.1

Description: Element is not in the document head

Count of instances: 4

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

Issue: text contrast improvable

Impact: Content is not easy to understand

WCAG: 1.4.6

Score: 15

Elements

Violations of alfa rules

Rule r66

Description: Text contrast less than AAA requires

Count of instances: 7

Violations of aslint rules

Rule color_contrast_aaa4

Description: Text has contrast less than 4.5:1

Count of instances: 7

Violations of axe rules

Rule color-contrast-enhanced

Description: Element has insufficient color contrast (Level AAA)

Count of instances: 11

Violations of htmlcs rules

Rule AAA.1_4_6.G17.Fail

Description: Text has insufficient contrast

Count of instances: 7

Violations of qualWeb rules

Rule QW-ACT-R76

Description: Text has less than the enhanced minimum contrast

Count of instances: 15

Issue: code obsolete

Impact: Document contains code that is no longer standard

WCAG: 4.1

Score: 15

Elements

Violations of ibm rules

Rule element_attribute_deprecated

Description: Element or attribute is obsolete

Count of instances: 5

Issue: all-capital text

Impact: Text is difficult to read

WCAG: 3.1.5

Score: 12

Elements

Violations of aslint rules

Rule capital_letters_words

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

Count of instances: 12

Violations of ed11y rules

Rule textUppercase

Description: Element contains more than 4 consecutive upper-case words

Count of instances: 1

Violations of testaro rules

Rule allCaps

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

Count of instances: 8

Issue: element closure invalid

Impact: Document contains invalid code

WCAG: 4.1.1

Score: 12

Elements

None identified

Violations of nuVal rules

Rule ^Stray end tag .+$

Description: Invalid closing tag

Count of instances: 4

Issue: text and image link not combined

Impact: Keyboard-only user expends extra effort to skip a link

WCAG: 2.4.4

Score: 12

Elements

Violations of wave rules

Rule link_redundant

Description: Adjacent links go to the same URL

Count of instances: 6

Issue: image dubiously named

Impact: Helper may describe an image inadequately

WCAG: 1.1.1

Score: 11

Elements

Violations of qualWeb rules

Rule QW-WCAG-T8

Description: Text alternative is suspect

Count of instances: 11

Violations of wave rules

Rule alt_suspicious

Description: Image text alternative is suspect

Count of instances: 7

Issue: tab-opening link action unstated?

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

WCAG: 3.2.5

Score: 10

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

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

Violations of testaro rules

Rule linkExt

Description: Link opens a new window or tab

Count of instances: 10

Issue: section heading missing

Impact: User cannot understand the topic of a part of the document

WCAG: 1.3.1

Score: 10

Elements

None identified

Violations of nuVal rules

Rule Section lacks heading. Consider using h2-h6 elements to add identifying headings to all sections, or else use a div element instead for any cases where no heading is needed.

Description: section has no heading

Count of instances: 10

Issue: dubious aria-label

Impact: User may fail to get help understanding an item in a form

WCAG: 1.3.1

Score: 10

Elements

None identified

Violations of nuVal rules

Rule Possible misuse of aria-label. (If you disagree with this warning, file an issue report or send e-mail to www-validator@w3.org.)

Description: aria-label attribute may be misused

Count of instances: 10

Issue: link indication poor

Impact: User cannot differentiate a link from plain text

WCAG: 1.3.3

Score: 10

Elements

Violations of testaro rules

Rule linkUl

Description: Inline links are not underlined

Count of instances: 5

Issue: hover indication poor

Impact: User cannot explore the document reliably with a mouse

WCAG: 3.3.2

Score: 9

Elements

None identified

Violations of testaro rules

Rule hovInd

Description: Hovering is unclearly indicated

Count of instances: 3

Issue: target small

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

WCAG: 2.5.5

Score: 8

Elements

Violations of alfa rules

Rule r111

Description: Target size is suboptimal

Count of instances: 3

Violations of testaro rules

Rule targetSize

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

Count of instances: 8

Issue: line height absolute

Impact: User cannot adjust the line height of text for readability

WCAG: 1.4.12

Score: 8

Elements

Violations of alfa rules

Rule r80

Description: Paragraph text has an absolute line height

Count of instances: 4

Issue: skip method missing or invalid?

Impact: Keyboard-only user may be unable easily to reach the specific content of the document

WCAG: 2.4.1

Score: 8

Elements

Violations of alfa rules

Rule r87

Description: First focusable element is not a link to the main content

Count of instances: 1

Issue: links named identically

Impact: User cannot get help differentiating links

WCAG: 2.4.4

Score: 8

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

Issue: tab-opening link action unstated

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

WCAG: 3.2.5

Score: 8

Elements

Violations of ed11y rules

Rule linkNewWindow

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

Count of instances: 5

Issue: no role-required name

Impact: User cannot get help understanding an item

WCAG: 4.1.2

Score: 8

Elements

Violations of ibm rules

Rule aria_accessiblename_exists

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

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: title attribute invalid

Impact: User cannot hover to get help explaining an item

WCAG: 1.3.1

Score: 8

Elements

Violations of testaro rules

Rule titledEl

Description: title attribute belongs to an inappropriate element

Count of instances: 2

Issue: form submission button missing

Impact: User cannot easily submit a form

WCAG: 3.2.2

Score: 6

Elements

Violations of aslint rules

Rule missing_submit_button

Description: Element is a form but contains no input or button element for submission

Count of instances: 2

Violations of qualWeb rules

Rule QW-WCAG-T19

Description: Submit button not provided

Count of instances: 2

Issue: element reloads or redirects

Impact: Document change may surprise a user

WCAG: 2.2.1

Score: 6

Elements

Violations of qualWeb rules

Rule QW-ACT-R4

Description: Element refreshes or redirects with delay

Count of instances: 1

Rule QW-ACT-R71

Description: Element has a refresh delay (no exception)

Count of instances: 1

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: heading-like styles dubious

Impact: User may be unable to understand the topic of a part of the document

WCAG: 1.3.1

Score: 5

Elements

Violations of wave rules

Rule heading_possible

Description: Possible heading

Count of instances: 5

Issue: region not named

Impact: User cannot get help surveying the parts of the document

WCAG: 4.1.2

Score: 4

Elements

Violations of alfa rules

Rule r40

Description: Region has no accessible name

Count of instances: 1

Violations of ibm rules

Rule aria_region_labelled

Description: Element with a region role has no label

Count of instances: 1

Issue: svg image not named

Impact: User cannot get help understanding an image

WCAG: 1.1.1

Score: 4

Elements

Violations of aslint rules

Rule accessible_svg

Description: Element has no title, description, text, attribute label, or role description

Count of instances: 1

Violations of ibm rules

Rule svg_graphics_labelled

Description: Element is svg but has no accessible name

Count of instances: 1

Issue: button not named

Impact: User cannot get help explaing a button

WCAG: 4.1.2

Score: 4

Elements

Violations of aslint rules

Rule empty_button_description

Description: button element has no visible accessible name

Count of instances: 1

Issue: requirement invalid

Impact: User may fail to get help determining whether a form item must be completed

WCAG: 1.3.5

Score: 4

Elements

Violations of aslint rules

Rule misused_required_attribute

Description: Requirement status of the element is invalid

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

Elements

None identified

Violations of wax rules

Rule Provide accessible names for