Accessibility digest

Contents

Synopsis
PageElizabeth Warren;Democratic;Massachusetts
URLhttps://elizabethwarren.com/
Test date2024/09/22
Score2915
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-0s.json

Introduction

How accessible is the Elizabeth Warren;Democratic;Massachusetts web page at https://elizabethwarren.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 2915, the sum of 800 for the count of issues, 1386 for specific issues, 0 for unclassified rule violations, 302 for tool-by-tool ratings, 364 for the count of violating elements, 0 for the page preventing tools from running, 63 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
font size absolute1.4.42166alfa:15, qualWeb:104
element not focusable2.1.14106testaro:53, alfa:0, qualWeb:0
attribute invalid1.3.1480axe:1, nuVal:20, aslint:0, ibm:0, wax:0
attribute obsolete4.1372aslint:1, nuVal:24, htmlcs:0, ibm:0, testaro:0, wave:0
focus indication poor2.4.7472testaro:18, alfa:0, aslint:0
contrast poor1.4.3464alfa:1, axe:16, ibm:1, qualWeb:1, wave:2, aslint:0, htmlcs:0, wax:0
line height low1.4.8264alfa:10, testaro:32
link indication poor1.3.3260testaro:30, alfa:0, axe:0
links named identically2.4.4254aslint:23, qualWeb:27, testaro:15
all-capital text3.1.5153aslint:53, ed11y:2, testaro:4, alfa:0
target small2.5.5137alfa:20, testaro:37
large visible-element count2.4131testaro:1
attribute value invalid1.3.1424nuVal:6, ibm:0, wax:0
CSS invalid4.1324nuVal:8
code obsolete4.1321ibm:7, nuVal:0
void element has trailing slash4.1121nuVal:21
control label invisible2.4.6420aslint:5, axe:0, wax:0
error reference invalid3.3.1420qualWeb:5, ibm:0
overflow hidden?1.4.4120qualWeb:20
meta invalid1.3.1318nuVal:6
aria attribute invalid4.1.2416alfa:4, axe:1, ibm:0, nuVal:0, qualWeb:0, wax:0
ID not unique4.1.1416alfa:2, aslint:2, htmlcs:1, ibm:1, nuVal:4, wax:1, axe:0, qualWeb:0
aria-controls or -owns invalid1.3.1416nuVal:4, ibm:0
inconsistent heading, link, or button styles3.2.4116testaro:16
tab-opening link action unstated3.2.5315ed11y:10
text contrast not testable1.4.3112alfa:12, htmlcs:5, aslint:0
button not named4.1.2412aslint:3, alfa:0, axe:0, htmlcs:0, nuVal:0, qualWeb:0, wave:0, wax:0
iframe not named4.1.2412aslint:3, htmlcs:1, wax:1, alfa:0, axe:0, ibm:0, qualWeb:0
operable element not focusable2.1.1412testaro:3
title attribute invalid1.3.1412testaro:3
z-index not zero1.4112testaro:12
content beyond landmarks1.3.6111alfa:11, axe:5, ibm:11, wax:4
tab-opening link action unstated?3.2.5111aslint:11, htmlcs:11, testaro:11
label types incompatible1.3.1210testaro:5
text and image link not combined2.4.4210wave:5, aslint:0, qualWeb:0
visible label not in name2.5.339alfa:1, axe:1, htmlcs:2, ibm:3, qualWeb:2
autocomplete invalid1.3.539aslint:3, alfa:0, axe:0, htmlcs:0, ibm:0, nuVal:0, qualWeb:0, wax:0
link not named2.4.448alfa:1, axe:1, ed11y:2, htmlcs:2, ibm:1, qualWeb:1, wave:2, wax:2
label reference invalid1.3.148aslint:1, nuVal:2, htmlcs:0, wave:0, wax:0
aria reference invalid1.3.148ibm:2, wave:1
no role-required name4.1.248ibm:2, wax:0
dubious aria-label1.3.118nuVal:8
script element invalid1.3.148nuVal:2
links dubiously share name2.4.417axe:7
control child of link or button2.5.536nuVal:2, testaro:2, wax:1, axe:0
parent missing1.3.144alfa:1, axe:0, nuVal:0, qualWeb:0, wax:0
line height absolute1.4.1224alfa:2
fieldset missing?1.3.114aslint:4, htmlcs:0, wax:0
descendant missing1.3.144axe:1, qualWeb:1, wax:1, alfa:0, nuVal:0
list item orphan1.3.144axe:1, wax:1
parent invalid1.3.144nuVal:1, ibm:0
image not named1.1.144nuVal:1, alfa:0, axe:0, ed11y:0, htmlcs:0, ibm:0, qualWeb:0, wave:0, wax:0
link name vague2.4.413aslint:3, ed11y:3, wave:3
position sticky1.4.1013htmlcs:3, aslint:0
forms not distinctly named1.3.633ibm:1
landmarks not distinctly named1.3.633ibm:1, wax:1, axe:0
code invalid4.133nuVal:1, qualWeb:0, wave:0
element closure invalid4.1.133nuVal:1
invalid at-rule4.133nuVal:1
box size absolute1.4.433qualWeb:1
element beyond display when focused1.4.1033testaro:1
role assigned instead of implicit4.1.213testaro:3
font small1.433wave:1, alfa:0, aslint:0, testaro:0
heading level skipped1.3.122alfa:1, axe:1, ed11y:1, wave:1, wax:1
text contrast improvable1.4.612alfa:1, aslint:2, htmlcs:2, qualWeb:1, axe:0, wax:0
link href missing1.3.122aslint:1, testaro:1, htmlcs:0, nuVal:0
heading structure illogical1.3.122aslint:1, htmlcs:1
nav links not list1.3.122htmlcs:1
link incomplete1.3.122htmlcs:1, wax:1
type redundant1.3.112nuVal:2
section heading missing1.3.112nuVal:2
iframe sandbox attributes risky4.122nuVal:1
heading names repeated1.3.122testaro:1, wax:1, aslint:0
tabindex redundant1.3.111aslint:1
heading-like styles dubious1.3.111axe:1, wave:1, ed11y:0, htmlcs:0
no option focusable2.1.111ibm:1
complementary not named1.3.611ibm:1
image dubiously named1.1.111qualWeb:1, aslint:0, wave:0
noscript element not equivalent?4.111wave:1
false aria-hidden value risky2.4.600aslint:3

Itemized issues

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

Issue: font size absolute

Impact: User cannot adjust the text size for readability

WCAG: 1.4.4

Score: 166

Elements

Violations of alfa rules

Rule r74

Description: Paragraph text has an absolute font size

Count of instances: 15

Violations of qualWeb rules

Rule QW-WCAG-T28

Description: Font size set to an absolute unit value

Count of instances: 104

Issue: element not focusable

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

WCAG: 2.1.1

Score: 106

Elements

None identified

Violations of testaro rules

Rule focAll

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

Count of instances: 53

Issue: attribute invalid

Impact: Item behaves improperly

WCAG: 1.3.1

Score: 80

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

Violations of nuVal rules

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

Description: Attribute not allowed on this element

Count of instances: 20

Issue: attribute obsolete

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

WCAG: 4.1

Score: 72

Elements

Violations of aslint rules

Rule obsolete_html_attributes

Description: Element has an obsolete attribute

Count of instances: 1

Violations of nuVal rules

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

Description: Attribute is obsolete on its element

Count of instances: 24

Issue: focus indication poor

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

WCAG: 2.4.7

Score: 72

Elements

Violations of testaro rules

Rule focInd

Description: Focused element displays a nonstandard or no focus indicator

Count of instances: 18

Issue: contrast poor

Impact: Content is difficult to understand

WCAG: 1.4.3

Score: 64

Elements

Violations of alfa rules

Rule r69

Description: Text outside widget has subminimum contrast

Count of instances: 1

Violations of axe rules

Rule color-contrast

Description: Element has insufficient color contrast

Count of instances: 16

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

Violations of qualWeb rules

Rule QW-ACT-R37

Description: Text has less than the minimum contrast

Count of instances: 1

Violations of wave rules

Rule contrast

Description: Very low contrast

Count of instances: 2

Issue: line height low

Impact: Text is difficult to read

WCAG: 1.4.8

Score: 64

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

Issue: link indication poor

Impact: User cannot differentiate a link from plain text

WCAG: 1.3.3

Score: 60

Elements

Violations of testaro rules

Rule linkUl

Description: Inline links are not underlined

Count of instances: 30

Issue: links named identically

Impact: User cannot get help differentiating links

WCAG: 2.4.4

Score: 54

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

Violations of qualWeb rules

Rule QW-ACT-R9

Description: Links with identical accessible names have different purposes

Count of instances: 15

Rule QW-ACT-R44

Description: Links with identical accessible names and context serve different purposes

Count of instances: 12

Violations of testaro rules

Rule linkAmb

Description: Links with the same text content have different destinations

Count of instances: 15

Issue: all-capital text

Impact: Text is difficult to read

WCAG: 3.1.5

Score: 53

Elements

Violations of aslint rules

Rule capital_letters_words

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

Count of instances: 53

Violations of ed11y rules

Rule textUppercase

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

Count of instances: 2

Violations of testaro rules

Rule allCaps

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

Count of instances: 4

Issue: target small

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

WCAG: 2.5.5

Score: 37

Elements

Violations of alfa rules

Rule r111

Description: Target size is suboptimal

Count of instances: 20

Violations of testaro rules

Rule targetSize

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

Count of instances: 37

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

Impact: Item behaves improperly

WCAG: 1.3.1

Score: 24

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

Issue: CSS invalid

Impact: Document cannot be properly displayed

WCAG: 4.1

Score: 24

Elements

None identified

Violations of nuVal rules

Rule ^CSS: .+: Too many values or values are not recognized.*$

Description: Invalid CSS value or too many values

Count of instances: 2

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

Description: Invalid value in CSS

Count of instances: 4

Rule CSS: Parse Error.

Description: Invalid CSS

Count of instances: 2

Issue: code obsolete

Impact: Document contains code that is no longer standard

WCAG: 4.1

Score: 21

Elements

Violations of ibm rules

Rule element_attribute_deprecated

Description: Element or attribute is obsolete

Count of instances: 7

Issue: void element has trailing slash

Impact: Document contains invalid code

WCAG: 4.1

Score: 21

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

Issue: control label invisible

Impact: User cannot understand how to operate a form item

WCAG: 2.4.6

Score: 20

Elements

Violations of aslint rules

Rule label_visually_hidden_only

Description: Form control has a label but it is not visible

Count of instances: 5

Issue: error reference invalid

Impact: User cannot correct a form error

WCAG: 3.3.1

Score: 20

Elements

None identified

Violations of qualWeb rules

Rule QW-ACT-R41

Description: Error message describes no invalid form field value

Count of instances: 5

Issue: overflow hidden?

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

WCAG: 1.4.4

Score: 20

Elements

Violations of qualWeb rules

Rule QW-ACT-R40

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

Count of instances: 20

Issue: meta invalid

Impact: Document fails to include needed data

WCAG: 1.3.1

Score: 18

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

Issue: aria attribute invalid

Impact: Item behavior violates user expectations

WCAG: 4.1.2

Score: 16

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

Violations of axe rules

Rule aria-valid-attr-value

Description: ARIA attribute has an invalid value

Count of instances: 1

Issue: ID not unique

Impact: User may be pointed to the wrong item

WCAG: 4.1.1

Score: 16

Elements

Violations of alfa rules

Rule r3

Description: Element id attribute value is not unique

Count of instances: 2

Violations of aslint rules

Rule duplicated_id_attribute

Description: Element id attribute value is not unique

Count of instances: 2

Violations of htmlcs rules

Rule AAA.4_1_1.F77

Description: Duplicate id attribute value

Count of instances: 1

Violations of ibm rules

Rule element_id_unique

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

Count of instances: 1

Violations of nuVal rules

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

Description: Duplicate id

Count of instances: 4

Violations of wax rules

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

Description: id attribute value is not unique

Count of instances: 1

Issue: aria-controls or -owns invalid

Impact: Keyboard-only user cannot reach an item

WCAG: 1.3.1

Score: 16

Elements

None identified

Violations of nuVal rules

Rule The aria-controls attribute must point to an element in the same document.

Description: aria-controls attribute references an element not in the document

Count of instances: 4

Issue: inconsistent heading, link, or button styles

Impact: User cannot easily distinguish items of different types

WCAG: 3.2.4

Score: 16

Elements

None identified

Violations of testaro rules

Rule styleDiff

Description: Heading, link, and button style inconsistencies

Count of instances: 16

Issue: tab-opening link action unstated

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

WCAG: 3.2.5

Score: 15

Elements

Violations of ed11y rules

Rule linkNewWindow

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

Count of instances: 10

Issue: text contrast not testable

Impact: Text may be difficult to read

WCAG: 1.4.3

Score: 12

Elements

Violations of alfa rules

Rule cantTellTextContrast

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

Count of instances: 12

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

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

Rule AAA.1_4_6.G17.BgImage

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

Count of instances: 1

Issue: button not named

Impact: User cannot get help explaing a button

WCAG: 4.1.2

Score: 12

Elements

Violations of aslint rules

Rule empty_button_description

Description: button element has no visible accessible name

Count of instances: 3

Issue: iframe not named

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

WCAG: 4.1.2

Score: 12

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

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