Accessibility digest
Contents
| Page | Robert Barb;Green;Montana |
|---|---|
| URL | https://www.robertbarb4ussenate.com |
| Test date | 2024/09/22 |
| Score | 1191 |
| Redirections | permitted |
|---|---|
| Tool isolation | no |
| Report format(s) | standard |
| Requester | |
| Device | default |
| Browser type | webkit |
| Reduced motion | not requested |
| Tested by | Testaro, procedure senate2024 |
| Scored by | Testilo, procedure tsp50 |
| Digested by | Testilo, procedure tdp50 |
| Full report | 240915T1658-ikz-1a.json |
Introduction
How accessible is the Robert Barb;Green;Montana web page at https://www.robertbarb4ussenate.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 1191, the sum of 300 for the count of issues, 761 for specific issues, 0 for unclassified rule violations, 41 for tool-by-tool ratings, 58 for the count of violating elements, 0 for the page preventing tools from running, 31 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:
- conformity to standards
- adherence to best practices
- how many different issues exist
- how many instances of each issue exist
- how many tools report violations of their rules
- how trustworthy each test of each tool is
- how serious each violation of a rule is
- simplicity
- speed of page responses
- testability
- conformity to expectations of browsers
Some ideas found elsewhere in accessibility scoring are rejected by the Testilo procedures:
- density: that an accessibility score should be based on the count of accessibility faults as a fraction of the count of potential accessibility faults (so, the score of a large page with particular faults should be better than the score of a smaller page with exactly those faults)
- applicability: that the score of a page should depend on the types of its content (so, the score of a page with accessible video content should be better than the score of an otherwise identical page without video content)
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:
- issue score: how many instances of issues were reported
- solo score: how many violations of rules not yet classified into issues were reported
- tool score: how many violations of their rules did tools report
- element score: how many HTML elements did any tool identify as violating at least one tool rule
- prevention score: how many tools were unable to perform their tests on the page
- log score: how much logging of page errors and other events did the browser do
- latency score: how long did the page take to load and become stable
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:
- log count: how many times the browser logged a message
- log size: how many characters large the collection of browser log messages was
- error log count: how many browser log messages reported page errors
- error log size: how many characters large the collection of browser log messages reporting page errors was
- prohibition count: how many times the browser logged a prohibited response status (403)
- visit rejection count: how many times the browser logged an abnormal response status
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
- This table shows the numbers of rule violations (
instances
) reported by one or more tools, classified by issue. - Tools often disagree on instance counts, because of non-equivalent rules or invalid tests. You can inspect the full report to diagnose differences.
- The
WCAG
value is the principle, guideline, or success criterion of the Web Content Accessibility Guidelines most relevant to the issue. - The
Weight
value estimates the importance of an instance of the issue, from 1 (minor or advisory) to 4 (serious). - The
Score
value is the contribution of the instances of the issue to the page score. - An instance count of 0 means the tool has a rule belonging to the issue but reported no violations of that rule, although at least one tool reported at least one violation.
- You can sort this table by WCAG, weight, or score.
The summary
Sorting is by score.
| Issue | WCAG | Weight | Score | Instance counts |
|---|---|---|---|---|
| meta bans zoom | 1.4.4 | 4 | 248 | alfa:1, aslint:1, axe:1, nuVal:2, qualWeb:1, wax:1 |
| h1 not 1st heading | 1.3.1 | 3 | 93 | alfa:1 |
| not exactly 1 h1 heading | 1.3.1 | 2 | 62 | aslint:1, axe:1, wave:1, nuVal:0 |
| main missing | 1.3.6 | 2 | 62 | axe:1 |
| no landmarks | 1.3.6 | 2 | 62 | wave:1 |
| primary heading not h1 | 1.3.1 | 2 | 62 | wax:1 |
| skip method missing or invalid | 2.4.1 | 3 | 48 | ibm:1, wax:1, axe:0, wave:0 |
| contrast poor | 1.4.3 | 4 | 16 | alfa:4, ibm:4, wave:4, aslint:0, axe:0, htmlcs:0, qualWeb:0, wax:0 |
| line height low | 1.4.8 | 2 | 16 | alfa:8, testaro:0 |
| semantic properties represented with styles | 1.3.1 | 2 | 12 | wax:6, htmlcs:0 |
| content beyond landmarks | 1.3.6 | 1 | 9 | axe:5, ibm:9, wax:5, alfa:0 |
| attribute value invalid | 1.3.1 | 4 | 8 | nuVal:2, ibm:0, wax:0 |
| focus indication poor | 2.4.7 | 4 | 8 | testaro:2, alfa:0, aslint:0 |
| text contrast improvable | 1.4.6 | 1 | 6 | alfa:6, aslint:6, axe:0, htmlcs:0, qualWeb:0, wax:0 |
| all-capital text | 3.1.5 | 1 | 6 | aslint:6, ed11y:5, testaro:6, alfa:0 |
| element obsolete | 4.1 | 3 | 6 | aslint:2, alfa:0, htmlcs:0, nuVal:0, qualWeb:0 |
| code obsolete | 4.1 | 3 | 6 | ibm:2, nuVal:0 |
| link indication poor | 1.3.3 | 2 | 4 | alfa:1, testaro:2, axe:0 |
| heading structure illogical | 1.3.1 | 2 | 4 | aslint:1, htmlcs:2 |
| tab-opening link action unstated | 3.2.5 | 3 | 3 | ed11y:2 |
| nesting invalid | 4.1.1 | 3 | 3 | nuVal:1 |
| element closure invalid | 4.1.1 | 3 | 3 | nuVal:1 |
| image dubiously named | 1.1.1 | 1 | 3 | qualWeb:3, aslint:0, wave:0 |
| tab-opening link action unstated? | 3.2.5 | 1 | 2 | aslint:2, htmlcs:2, testaro:2 |
| target small | 2.5.5 | 1 | 2 | testaro:2, alfa:0 |
| underlining dubious | 1.3.1 | 1 | 2 | wave:2 |
| heading names repeated | 1.3.1 | 2 | 2 | wax:1, aslint:0, testaro:0 |
| item makes testing inconclusive | 4.1 | 1 | 1 | alfa:1 |
| position sticky | 1.4.10 | 1 | 1 | htmlcs:1, aslint:0 |
| void element has trailing slash | 4.1 | 1 | 1 | nuVal:1 |
Itemized issues
The reported rule violations are itemized below, issue by issue. Additional details can be inspected in the full report.
Issue: meta bans zoom
Impact: User cannot adjust the document size for readability
WCAG: 1.4.4
Score: 248
Elements
- /html/head/meta[2]
Violations of alfa rules
Rule r47
Description: Element restricts zooming
Count of instances: 1
Violations of aslint rules
Rule zoom_disabled
Description: Element specifies a minimum or maximum scale or prohibits zooming
Count of instances: 1
Violations of axe rules
Rule meta-viewport
Description: Zooming and scaling are disabled
Count of instances: 1
Violations of nuVal rules
Rule Consider avoiding viewport values that prevent users from resizing documents.
Description: viewport value prevents users from resizing the document
Count of instances: 2
Violations of qualWeb rules
Rule QW-ACT-R14
Description: meta viewport prevents zoom
Count of instances: 1
Violations of wax rules
Rule Ensure does not disable text scaling and zooming.
Description: Element disables zooming or scaling
Count of instances: 1
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: not exactly 1 h1 heading
Impact: User cannot understand the topic of the document
WCAG: 1.3.1
Score: 62
Elements
- /html
Violations of aslint rules
Rule h1_must_be
Description: Page contains no h1 element
Count of instances: 1
Violations of axe rules
Rule page-has-heading-one
Description: Document contains no level-one heading
Count of instances: 1
Violations of wave rules
Rule h1_missing
Description: Missing first level heading
Count of instances: 1
Issue: main missing
Impact: User cannot get help on how some of the document is organized
WCAG: 1.3.6
Score: 62
Elements
- /html
Violations of axe rules
Rule landmark-one-main
Description: page has no main landmark
Count of instances: 1
Issue: no landmarks
Impact: User cannot get help on how the document is organized
WCAG: 1.3.6
Score: 62
Elements
None identified
Violations of wave rules
Rule region_missing
Description: Page has no regions or ARIA landmarks
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
None identified
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: 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
- /html/body
Violations of ibm rules
Rule skip_main_exists
Description: Page provides no way to quickly navigate to the main content
Count of instances: 1
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: contrast poor
Impact: Content is difficult to understand
WCAG: 1.4.3
Score: 16
Elements
- /html/body/div[3]/h2
- /html/body/div[4]/p/a
- /html/body/div[5]/h2
- /html/body/div[5]/p/a
Violations of alfa rules
Rule r69
Description: Text outside widget has subminimum contrast
Count of instances: 4
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: 4
Violations of wave rules
Rule contrast
Description: Very low contrast
Count of instances: 4
Issue: line height low
Impact: Text is difficult to read
WCAG: 1.4.8
Score: 16
Elements
- /html/body/div[2]/div/div[1]/p
- /html/body/div[2]/p[1]
- /html/body/div[2]/p[2]
- /html/body/div[2]/p[3]
- /html/body/div[3]/div/p
- /html/body/div[4]/p
- /html/body/div[5]/p
- /html/body/div[5]/div/p
Violations of alfa rules
Rule r73
Description: Text line height is not at least 1.5
Count of instances: 8
Issue: semantic properties represented with styles
Impact: User cannot get help to fully understand the text
WCAG: 1.3.1
Score: 12
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: 6
Issue: content beyond landmarks
Impact: User cannot get help on how some of the document is organized
WCAG: 1.3.6
Score: 9
Elements
- /html/body/div[1]
- /html/body/div[2]
- /html/body/div[3]
- /html/body/div[4]
- /html/body/div[5]
- /html/body/div[2]/h2
- /html/body/div[2]/div/div[1]/p
- /html/body/div[3]/h2
- /html/body/div[3]/div/p
- /html/body/div[4]/h2
- /html/body/div[4]/p/a
- /html/body/div[5]/h2
- /html/body/div[5]/p/a
- /html/body/div[5]/div/p
Violations of axe rules
Rule region
Description: Some page content is not contained by landmarks
Count of instances: 5
Violations of ibm rules
Rule aria_content_in_landmark
Description: Content is not within a landmark element
Count of instances: 9
Violations of wax rules
Rule Use landmarks to contain page content.
Description: Content is not within a landmark element
Count of instances: 5
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: focus indication poor
Impact: Keyboard-only user cannot choose an item to operate
WCAG: 2.4.7
Score: 8
Elements
- /html/body/div[4]/p/a
- /html/body/div[5]/p/a
Violations of testaro rules
Rule focInd
Description: Focused element displays a nonstandard or no focus indicator
Count of instances: 2
Issue: text contrast improvable
Impact: Content is not easy to understand
WCAG: 1.4.6
Score: 6
Elements
- /html/body/div[2]/h2
- /html/body/div[3]/h2
- /html/body/div[4]/h2
- /html/body/div[4]/p/a
- /html/body/div[5]/h2
- /html/body/div[5]/p/a
Violations of alfa rules
Rule r66
Description: Text contrast less than AAA requires
Count of instances: 6
Violations of aslint rules
Rule color_contrast_aaa4
Description: Text has contrast less than 4.5:1
Count of instances: 4
Rule color_contrast_aaa7
Description: Text has contrast less than 7:1
Count of instances: 2
Issue: all-capital text
Impact: Text is difficult to read
WCAG: 3.1.5
Score: 6
Elements
- /html/head/title
- /html/body/div[2]/h2
- /html/body/div[3]/h2
- /html/body/div[4]/h2
- /html/body/div[5]/h2
- /html/body/div[5]/div/p
- /html/body/div[3]/div/p
Violations of aslint rules
Rule capital_letters_words
Description: Element or its title has entirely upper-case words
Count of instances: 6
Violations of ed11y rules
Rule textUppercase
Description: Element contains more than 4 consecutive upper-case words
Count of instances: 5
Violations of testaro rules
Rule allCaps
Description: Element has a text substring of at least 8 upper-case characters
Count of instances: 6
Issue: element obsolete
Impact: Document includes obsolete code that the browser may fail to process
WCAG: 4.1
Score: 6
Elements
- /html/body/div[2]/div/div[1]/p/u
- /html/body/div[2]/p[1]/u
Violations of aslint rules
Rule obsolete_html_elements
Description: Element is obsolete
Count of instances: 2
Issue: code obsolete
Impact: Document contains code that is no longer standard
WCAG: 4.1
Score: 6
Elements
- /html/body/div[2]/div/div[1]/p/u
- /html/body/div[2]/p[1]/u
Violations of ibm rules
Rule element_attribute_deprecated
Description: Element or attribute is obsolete
Count of instances: 2
Issue: link indication poor
Impact: User cannot differentiate a link from plain text
WCAG: 1.3.3
Score: 4
Elements
- /html/body/div[4]/p/a
- /html/body/div[5]/p/a
Violations of alfa rules
Rule r62
Description: Inline link is not distinct from the surrounding text except by color
Count of instances: 1
Violations of testaro rules
Rule linkUl
Description: Inline links are not underlined
Count of instances: 2
Issue: heading structure illogical
Impact: Helper misdescribes the document
WCAG: 1.3.1
Score: 4
Elements
- /html/body/div[2]/h2
Violations of aslint rules
Rule headings_hierarchy
Description: Heading level is illogical in its context
Count of instances: 1
Violations of htmlcs rules
Rule AAA.1_3_1_AAA.G141
Description: Heading level is incorrect
Count of instances: 2
Issue: tab-opening link action unstated
Impact: Following a link opens a new window, surprising a user
WCAG: 3.2.5
Score: 3
Elements
- /html/body/div[4]/p/a
- /html/body/div[5]/p/a
Violations of ed11y rules
Rule linkNewWindow
Description: Link opens a new window or tab without prior notice
Count of instances: 2
Issue: nesting invalid
Impact: Document contains invalid code
WCAG: 4.1.1
Score: 3
Elements
None identified
Violations of nuVal rules
Rule ^End tag .+ violates nesting rules.*$
Description: End tag violates nesting rules
Count of instances: 1
Issue: element closure invalid
Impact: Document contains invalid code
WCAG: 4.1.1
Score: 3
Elements
None identified
Violations of nuVal rules
Rule ^No .+ element in scope but a .+ end tag seen.*$
Description: End tag for an element that is not in scope
Count of instances: 1
Issue: image dubiously named
Impact: Helper may describe an image inadequately
WCAG: 1.1.1
Score: 3
Elements
- /html/body/div[1]/div/img
- /html/body/div[2]/div/div[2]/img
- /html/body/div[3]/div/img
Violations of qualWeb rules
Rule QW-WCAG-T8
Description: Text alternative is suspect
Count of instances: 3
Issue: tab-opening link action unstated?
Impact: Following a link opens a new window, possibly surprising a user
WCAG: 3.2.5
Score: 2
Elements
- /html/body/div[4]/p/a
- /html/body/div[5]/p/a
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: 2
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: 2
Violations of testaro rules
Rule linkExt
Description: Link opens a new window or tab
Count of instances: 2
Issue: target small
Impact: User cannot reliably choose an item to click or tap
WCAG: 2.5.5
Score: 2
Elements
- /html/body/div[4]/p/a
- /html/body/div[5]/p/a
Violations of testaro rules
Rule targetSize
Description: Button, input, or non-inline link is smaller than 44 px wide and high
Count of instances: 2
Issue: underlining dubious
Impact: User may be misled into believing some text is a link
WCAG: 1.3.1
Score: 2
Elements
- /html/body/div[2]/div/div[1]/p/u
- /html/body/div[2]/p[1]/u
Violations of wave rules
Rule underline
Description: CSS underline on text that is not a link
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
- /
Violations of alfa rules
Rule cantTell
Description: Test could not give a conclusive result
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: 1
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: 1
Issue: void element has trailing slash
Impact: Document contains invalid code
WCAG: 4.1
Score: 1
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: 1
Elements with issues
Elements exhibiting issues:
Element /
- h1 not 1st heading
- item makes testing inconclusive
Element /html
- main missing
- not exactly 1 h1 heading
Element /html/body
- skip method missing or invalid
Element /html/body/div[1]
- content beyond landmarks
Element /html/body/div[1]/div/img
- image dubiously named
Element /html/body/div[2]
- content beyond landmarks
Element /html/body/div[2]/div/div[1]/p
- content beyond landmarks
- line height low
Element /html/body/div[2]/div/div[1]/p/u
- code obsolete
- element obsolete
- underlining dubious
Element /html/body/div[2]/div/div[2]/img
- image dubiously named
Element /html/body/div[2]/h2
- all-capital text
- content beyond landmarks
- heading structure illogical
- text contrast improvable
Element /html/body/div[2]/p[1]
- line height low
Element /html/body/div[2]/p[1]/u
- code obsolete
- element obsolete
- underlining dubious
Element /html/body/div[2]/p[2]
- line height low
Element /html/body/div[2]/p[3]
- line height low
Element /html/body/div[3]
- content beyond landmarks
Element /html/body/div[3]/div/img
- image dubiously named
Element /html/body/div[3]/div/p
- all-capital text
- content beyond landmarks
- line height low
Element /html/body/div[3]/h2
- all-capital text
- content beyond landmarks
- contrast poor
- text contrast improvable
Element /html/body/div[4]
- content beyond landmarks
Element /html/body/div[4]/h2
- all-capital text
- content beyond landmarks
- text contrast improvable
Element /html/body/div[4]/p
- line height low
Element /html/body/div[4]/p/a
- content beyond landmarks
- contrast poor
- focus indication poor
- link indication poor
- tab-opening link action unstated
- tab-opening link action unstated?
- target small
- text contrast improvable
Element /html/body/div[5]
- content beyond landmarks
Element /html/body/div[5]/div/p
- all-capital text
- content beyond landmarks
- line height low
Element /html/body/div[5]/h2
- all-capital text
- content beyond landmarks
- contrast poor
- text contrast improvable
Element /html/body/div[5]/p
- line height low
Element /html/body/div[5]/p/a
- content beyond landmarks
- contrast poor
- focus indication poor
- link indication poor
- tab-opening link action unstated
- tab-opening link action unstated?
- target small
- text contrast improvable
Element /html/head/meta[2]
- meta bans zoom
Element /html/head/title
- all-capital text