Accessibility digest
Contents
| Page | Tracy Andrus;Democratic;Texas |
|---|---|
| URL | http://www.tracyandrusforsenate.com |
| Test date | 2024/09/22 |
| Score | 4396 |
| 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-21.json |
Introduction
How accessible is the Tracy Andrus;Democratic;Texas web page at http://www.tracyandrusforsenate.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 4396, the sum of 770 for the count of issues, 2990 for specific issues, 0 for unclassified rule violations, 403 for tool-by-tool ratings, 144 for the count of violating elements, 30 for the page preventing tools from running, 59 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 |
|---|---|---|---|---|
| not exactly 1 h1 heading | 1.3.1 | 2 | 1488 | nuVal:24, aslint:0, axe:0, wave:0 |
| contrast poor | 1.4.3 | 4 | 164 | alfa:23, axe:41, htmlcs:4, ibm:22, qualWeb:34, wave:8, wax:7, aslint:0 |
| attribute value invalid | 1.3.1 | 4 | 128 | nuVal:32, ibm:0, wax:0 |
| image not named | 1.1.1 | 4 | 96 | alfa:12, axe:12, ed11y:8, htmlcs:12, ibm:12, nuVal:24, qualWeb:12, wave:12, wax:12 |
| main missing | 1.3.6 | 2 | 62 | axe:1 |
| page content moves spontaneously | 2.2.2 | 2 | 62 | testaro:1, aslint:0 |
| presentational child focusable | 4.1.2 | 4 | 60 | alfa:15, qualWeb:15 |
| parent missing | 1.3.1 | 4 | 60 | qualWeb:15, alfa:0, axe:0, nuVal:0, wax:0 |
| hover indication poor | 3.3.2 | 3 | 54 | testaro:18 |
| void element has trailing slash | 4.1 | 1 | 52 | nuVal:52 |
| content beyond landmarks | 1.3.6 | 1 | 48 | alfa:48, axe:34, ibm:46, wax:18 |
| focus indication poor | 2.4.7 | 4 | 48 | testaro:12, alfa:0, aslint:0 |
| skip method missing or invalid | 2.4.1 | 3 | 48 | wax:1, axe:0, ibm:0, wave:0 |
| control child of link or button | 2.5.5 | 3 | 45 | axe:15, wax:15, nuVal:0, testaro:0 |
| line height low | 1.4.8 | 2 | 36 | alfa:2, testaro:18 |
| invalid landmark child of navigation role | 1.3.6 | 4 | 36 | aslint:9 |
| text contrast improvable | 1.4.6 | 1 | 33 | alfa:26, aslint:21, axe:11, htmlcs:23, qualWeb:33, wax:12 |
| large visible-element count | 2.4 | 1 | 31 | testaro:1 |
| color missing | 1.4.3 | 4 | 28 | qualWeb:7 |
| target small | 2.5.5 | 1 | 26 | alfa:15, testaro:26 |
| button not named | 4.1.2 | 4 | 24 | alfa:4, aslint:6, axe:4, htmlcs:2, qualWeb:4, wave:4, wax:4, nuVal:0 |
| parent invalid | 1.3.1 | 4 | 24 | nuVal:6, ibm:0 |
| all-capital text | 3.1.5 | 1 | 22 | aslint:22, ed11y:1, testaro:4, alfa:0 |
| section heading missing | 1.3.1 | 1 | 22 | nuVal:22 |
| overflow hidden? | 1.4.4 | 1 | 20 | qualWeb:20 |
| control not named | 4.1.2 | 4 | 16 | ibm:4, alfa:0, axe:0, htmlcs:0, qualWeb:0, wave:0, wax:0 |
| title attribute invalid | 1.3.1 | 4 | 16 | testaro:4 |
| font small | 1.4 | 3 | 15 | aslint:5, alfa:0, testaro:0, wave:0 |
| tab-opening link action unstated | 3.2.5 | 3 | 14 | ed11y:9 |
| inconsistent heading, link, or button styles | 3.2.4 | 1 | 13 | testaro:13 |
| interactive component not named | 4.1.2 | 4 | 12 | ibm:3 |
| operable element not focusable | 2.1.1 | 4 | 12 | testaro:3 |
| item makes testing inconclusive | 4.1 | 1 | 10 | alfa:10 |
| text contrast not testable | 1.4.3 | 1 | 10 | alfa:10, htmlcs:8, aslint:0 |
| links named identically | 2.4.4 | 2 | 10 | aslint:5, qualWeb:0, testaro:0 |
| tab-opening link action unstated? | 3.2.5 | 1 | 9 | aslint:9, htmlcs:7, testaro:9 |
| svg image not named | 1.1.1 | 4 | 8 | aslint:2, ibm:2, alfa:0, axe:0, qualWeb:0, wax:0 |
| image dubiously named | 1.1.1 | 1 | 8 | aslint:2, qualWeb:8, wave:1 |
| background image invalid | 4.1 | 4 | 8 | nuVal:2 |
| z-index not zero | 1.4 | 1 | 7 | testaro:7 |
| attribute obsolete | 4.1 | 3 | 6 | aslint:1, nuVal:2, htmlcs:0, ibm:0, testaro:0, wave:0 |
| heading structure illogical | 1.3.1 | 2 | 6 | aslint:3, htmlcs:1 |
| navigations not distinctly named | 1.3.6 | 3 | 6 | ibm:2 |
| link indication poor | 1.3.3 | 2 | 6 | testaro:3, alfa:0, axe:0 |
| text and image link not combined | 2.4.4 | 2 | 6 | wave:3, aslint:0, qualWeb:0 |
| text distortion | 3.1.5 | 1 | 5 | testaro:5 |
| aria attribute invalid | 4.1.2 | 4 | 4 | alfa:1, wax:1, axe:0, ibm:0, nuVal:0, qualWeb:0 |
| dialog not named | 4.1.2 | 4 | 4 | aslint:1, wax:1, axe:0 |
| iframe not named | 4.1.2 | 4 | 4 | aslint:1, axe:1, htmlcs:1, ibm:1, qualWeb:1, wax:1, alfa:0 |
| CSS bans page rotation | 1.3.4 | 4 | 4 | aslint:1, qualWeb:0 |
| role redundant | 4.1.2 | 1 | 4 | ibm:2, nuVal:4 |
| attribute invalid | 1.3.1 | 4 | 4 | ibm:1, aslint:0, axe:0, nuVal:0, wax:0 |
| descendant missing | 1.3.1 | 4 | 4 | qualWeb:1, wax:1, alfa:0, axe:0, nuVal:0 |
| landmarks not distinctly named | 1.3.6 | 3 | 3 | axe:1, wax:1, ibm:0 |
| heading-like styles dubious | 1.3.1 | 1 | 3 | htmlcs:1, wave:3, axe:0, ed11y:0 |
| code obsolete | 4.1 | 3 | 3 | ibm:1, nuVal:0 |
| role invalid | 4.1.2 | 3 | 3 | ibm:1, alfa:0, aslint:0, axe:0, nuVal:0, qualWeb:0 |
| element closure invalid | 4.1.1 | 3 | 3 | nuVal:1 |
| box size absolute | 1.4.4 | 3 | 3 | qualWeb:1 |
| role assigned instead of implicit | 4.1.2 | 1 | 3 | testaro:3 |
| heading heads nothing | 1.3.1 | 2 | 2 | alfa:1, wax:0 |
| heading level skipped | 1.3.1 | 2 | 2 | axe:1, ed11y:1, wave:1, alfa:0, wax:0 |
| position sticky | 1.4.10 | 1 | 2 | htmlcs:2, aslint:0 |
| element not focusable | 2.1.1 | 4 | 2 | testaro:1, alfa:0, qualWeb:0 |
| heading names repeated | 1.3.1 | 2 | 2 | wax:1, aslint:0, testaro:0 |
| custom button keyboard-inoperable? | 2.1.1 | 1 | 1 | aslint:1 |
| tabindex redundant | 1.3.1 | 1 | 1 | aslint:1 |
| link destination not URL | 1.3.1 | 1 | 1 | aslint:1 |
| all-italic text | 3.1.5 | 1 | 1 | aslint:1, alfa:0, testaro:0 |
| link name vague | 2.4.4 | 1 | 1 | ed11y:1, aslint:0, wave:0 |
| image name contains image | 1.1.1 | 1 | 1 | ed11y:1 |
| no option focusable | 2.1.1 | 1 | 1 | ibm:1 |
| image link text suspect | 2.4.4 | 1 | 1 | qualWeb:1 |
| filter style | 4.1 | 1 | 1 | testaro:1 |
| title attribute redundant | 1.3.1 | 1 | 1 | testaro:1, aslint:0, qualWeb:0, wave:0 |
| audio or video alternatives missing? | 1.2.2 | 1 | 1 | wave:1 |
| false aria-hidden value risky | 2.4.6 | 0 | 0 | aslint: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: 1488
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: 24
Issue: contrast poor
Impact: Content is difficult to understand
WCAG: 1.4.3
Score: 164
Elements
None identified
Violations of alfa rules
Rule r69
Description: Text outside widget has subminimum contrast
Count of instances: 23
Violations of axe rules
Rule color-contrast
Description: Element has insufficient color contrast
Count of instances: 41
Violations of htmlcs rules
Rule AAA.1_4_6.G18.Fail
Description: Contrast between the text and its background is less than 4.5:1
Count of instances: 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: 22
Violations of qualWeb rules
Rule QW-ACT-R37
Description: Text has less than the minimum contrast
Count of instances: 34
Violations of wave rules
Rule contrast
Description: Very low contrast
Count of instances: 8
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: 7
Issue: attribute value invalid
Impact: Item behaves improperly
WCAG: 1.3.1
Score: 128
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: 32
Issue: image not named
Impact: User cannot get help to know what is in an image
WCAG: 1.1.1
Score: 96
Elements
- /html/body/div[1]/section[4]/div[2]/img
- /html/body/div[1]/section[7]/div[1]/img
- /html/body/div[1]/section[11]/div[1]/img
- /html/body/div[1]/section[13]/div[1]/img
- /html/body/div[1]/section[14]/div/img
- /html/body/div[1]/section[15]/div/div[1]/a/div/div[1]/img
- /html/body/div[1]/section[15]/div/div[2]/a/div/div[1]/img
- /html/body/div[1]/section[17]/div[1]/img
Violations of alfa rules
Rule r2
Description: Image has no accessible name
Count of instances: 12
Violations of axe rules
Rule image-alt
Description: Image has no text alternative
Count of instances: 12
Violations of ed11y rules
Rule altMissing
Description: img element has no alt attribute
Count of instances: 8
Violations of htmlcs rules
Rule AAA.1_1_1.H37
Description: img element has no alt attribute
Count of instances: 12
Violations of ibm rules
Rule img_alt_valid
Description: Image has neither an alt attribute nor an ARIA label or title
Count of instances: 12
Violations of nuVal rules
Rule An img element must have an alt attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
Description: img element has no alt attribute
Count of instances: 24
Violations of qualWeb rules
Rule QW-ACT-R17
Description: Image has no accessible name
Count of instances: 12
Violations of wave rules
Rule alt_missing
Description: Text alternative is missing
Count of instances: 12
Violations of wax rules
Rule Img element missing an alt attribute. Use the alt attribute to specify a short text alternative.
Description: Image has no text alternative
Count of instances: 12
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: presentational child focusable
Impact: Keyboard-only user cannot navigate properly to the operable items
WCAG: 4.1.2
Score: 60
Elements
None identified
Violations of alfa rules
Rule r90
Description: Element has a role making its children presentational but contains a focusable element
Count of instances: 15
Violations of qualWeb rules
Rule QW-ACT-R65
Description: Element with presentational children has focusable content
Count of instances: 15
Issue: parent missing
Impact: Keyboard-only user cannot operate a custom tool
WCAG: 1.3.1
Score: 60
Elements
None identified
Violations of qualWeb rules
Rule QW-ACT-R33
Description: Element has no ARIA required context role
Count of instances: 15
Issue: hover indication poor
Impact: User cannot explore the document reliably with a mouse
WCAG: 3.3.2
Score: 54
Elements
None identified
Violations of testaro rules
Rule hovInd
Description: Hovering is unclearly indicated
Count of instances: 18
Issue: void element has trailing slash
Impact: Document contains invalid code
WCAG: 4.1
Score: 52
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: 52
Issue: content beyond landmarks
Impact: User cannot get help on how some of the document is organized
WCAG: 1.3.6
Score: 48
Elements
None identified
Violations of alfa rules
Rule r57
Description: Perceivable text content is not included in any landmark
Count of instances: 48
Violations of axe rules
Rule region
Description: Some page content is not contained by landmarks
Count of instances: 34
Violations of ibm rules
Rule aria_content_in_landmark
Description: Content is not within a landmark element
Count of instances: 46
Violations of wax rules
Rule Use landmarks to contain page content.
Description: Content is not within a landmark element
Count of instances: 18
Issue: focus indication poor
Impact: Keyboard-only user cannot choose an item to operate
WCAG: 2.4.7
Score: 48
Elements
- /html/body/div[1]/nav/div/ul/li[1]/a
- /html/body/div[1]/nav/div/ul/li[2]/a
- /html/body/div[1]/nav/div/ul/li[3]/a
- /html/body/div[1]/section[3]/div/button[2]
- /html/body/div[1]/section[3]/div/ul/li[1]/button
- /html/body/div[1]/section[4]/div[1]/p/div/iframe
- /html/body/div[1]/section[12]/div[1]/button[1]
- /html/body/div[1]/section[12]/div[2]/button[1]
- /html/body/div[1]/section[12]/div[2]/button[3]
- /html/body/div[1]/section[12]/div[2]/button[4]
- /html/body/div[1]/section[15]/div/div[1]/a
- /html/body/div[1]/section[16]/div[2]/div[2]/div[1]/h4/a
Violations of testaro rules
Rule focInd
Description: Focused element displays a nonstandard or no focus indicator
Count of instances: 12
Issue: skip method missing or invalid
Impact: Keyboard-only user cannot easily reach the specific content of the document
WCAG: 2.4.1
Score: 48
Elements
None identified
Violations of wax rules
Rule Ensure that any common navigation elements can be bypassed; for instance, by use of skip links, header elements, or ARIA landmark roles.
Description: Page provides no way to quickly navigate to the main content
Count of instances: 1
Issue: control child of link or button
Impact: User cannot reliably choose an item to click or tap
WCAG: 2.5.5
Score: 45
Elements
None identified
Violations of axe rules
Rule nested-interactive
Description: Interactive controls are nested
Count of instances: 15
Violations of wax rules
Rule Avoid nesting interactive controls to prevent screen reader and focus issues.
Description: Interactive controls are nested
Count of instances: 15
Issue: line height low
Impact: Text is difficult to read
WCAG: 1.4.8
Score: 36
Elements
- /html/body/div[1]
- /html/body/div[1]/header/div[1]/div/h1
- /html/body/div[1]/header/div[1]/div/h1/a
- /html/body/div[1]/section[3]/div/div/div/figure[1]/div[2]/h1
- /html/body/div[1]/section[3]/div/div/div/figure[2]/div[2]/h1
- /html/body/div[1]/section[3]/div/div/div/figure[2]/div[2]/p
- /html/body/div[1]/section[3]/div/div/div/figure[3]/div[2]/h1
- /html/body/div[1]/section[3]/div/div/div/figure[3]/div[2]/p
- /html/body/div[1]/section[4]/div[1]/h2
- /html/body/div[1]/section[7]/div[2]/h2
- /html/body/div[1]/section[8]/div[2]/h1
- /html/body/div[1]/section[11]/div[2]/h2
- /html/body/div[1]/section[11]/div[2]/h2/strong
- /html/body/div[1]/section[15]/h1
- /html/body/div[1]/section[15]/div/div[1]/a/div/div[2]/h2
- /html/body/div[1]/section[15]/div/div[2]/a/div/div[2]/h2
- /html/body/div[1]/section[15]/nav/a
- /html/body/div[1]/section[16]/h1
Violations of alfa rules
Rule r73
Description: Text line height is not at least 1.5
Count of instances: 2
Violations of testaro rules
Rule lineHeight
Description: Text has a line height less than 1.5 times its font size
Count of instances: 18
Issue: invalid landmark child of navigation role
Impact: User cannot get help on how some of the document is organized
WCAG: 1.3.6
Score: 36
Elements
None identified
Violations of aslint rules
Rule navigation_landmark_restrictions
Description: Element with a navigation role contains a landmark other than region and search
Count of instances: 9
Issue: text contrast improvable
Impact: Content is not easy to understand
WCAG: 1.4.6
Score: 33
Elements
None identified
Violations of alfa rules
Rule r66
Description: Text contrast less than AAA requires
Count of instances: 26
Violations of aslint rules
Rule color_contrast_aaa7
Description: Text has contrast less than 7:1
Count of instances: 21
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: 23
Violations of qualWeb rules
Rule QW-ACT-R76
Description: Text has less than the enhanced minimum contrast
Count of instances: 33
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: 12
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: color missing
Impact: Content is impossible to perceive under some conditions
WCAG: 1.4.3
Score: 28
Elements
None identified
Violations of qualWeb rules
Rule QW-WCAG-T31
Description: Foreground or background color is specified but not both
Count of instances: 7
Issue: target small
Impact: User cannot reliably choose an item to click or tap
WCAG: 2.5.5
Score: 26
Elements
- /html/body/div[1]/nav/button
- /html/body/div[1]/section[3]/div/ul/li[1]/button
- /html/body/div[1]/section[3]/div/ul/li[2]/button
- /html/body/div[1]/section[3]/div/ul/li[3]/button
- /html/body/div[1]/section[12]/div[1]/button[1]
- /html/body/div[1]/section[12]/div[1]/button[2]
- /html/body/div[1]/section[12]/div[2]/button[1]
- /html/body/div[1]/section[12]/div[2]/button[2]
- /html/body/div[1]/section[12]/div[2]/button[3]
- /html/body/div[1]/section[12]/div[2]/button[4]
- /html/body/div[1]/section[15]/nav/a
- /html/body/div[1]/section[17]/div[2]/p[2]/a
- /html/body/div[1]/section[18]/a
- /html/body/div[1]/section[22]/div[2]/div/a
- /html/body/footer/div[1]/div/div/div/div/div/div[3]/a
- /html/body/footer/div[1]/div/div/div/div/div/div[4]/a
- /html/body/footer/div[1]/div/div/div/div/div/div[5]/a
- /html/body/footer/div[2]/div[1]/span[2]/a
- /html/body/footer/div[2]/div[1]/span[3]/a
- /html/body/footer/div[2]/div[2]/div/span/a[1]
- /html/body/footer/div[2]/div[2]/div/span/a[2]
- /html/body/footer/div[2]/div[2]/div/span/a[3]
- /html/body/footer/div[2]/div[2]/div/span/a[4]
- /html/body/footer/div[2]/div[2]/div/span/a[5]
- /html/body/footer/div[2]/div[2]/div/span/a[6]
- /html/body/footer/div[2]/div[2]/div/span/a[7]
Violations of alfa rules
Rule r111
Description: Target size is suboptimal
Count of instances: 15
Violations of testaro rules
Rule targetSize
Description: Button, input, or non-inline link is smaller than 44 px wide and high
Count of instances: 26
Issue: button not named
Impact: User cannot get help explaing a button
WCAG: 4.1.2
Score: 24
Elements
None identified
Violations of alfa rules
Rule r12
Description: button element has no accessible name
Count of instances: 4
Violations of aslint rules
Rule empty_button_description
Description: button element has no visible accessible name
Count of instances: 6
Violations of axe rules
Rule button-name
Description: button element has no discernible text
Count of instances: 4
Violations of htmlcs rules
Rule AAA.4_1_2.H91.Button.Name
Description: button element has no accessible name
Count of instances: 2
Violations of qualWeb rules
Rule QW-ACT-R11
Description: button element has no accessible name
Count of instances: 4
Violations of wave rules
Rule button_empty
Description: button element is empty or has no value text
Count of instances: 4
Violations of wax rules
Rule This button element does not have a name available to an accessibility API. Valid names are: title , element content, aria-label , aria-labelledby , aria-description , aria-describedby .
Description: button element has no accessible name
Count of instances: 4
Issue: parent invalid
Impact: User cannot properly operate an item
WCAG: 1.3.1
Score: 24
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: 6
Issue: all-capital text
Impact: Text is difficult to read
WCAG: 3.1.5
Score: 22
Elements
- /html/body/div[1]/section[3]/div/div/div/figure[1]/div[2]/h1
- /html/body/div[1]/header/div[1]/div/h1/a
- /html/body/div[1]/nav/div/ul/li[3]/a
- /html/body/div[1]/nav/div/ul/li[4]/a
Violations of aslint rules
Rule capital_letters_words
Description: Element or its title has entirely upper-case words
Count of instances: 22
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: 4
Issue: section heading missing
Impact: User cannot understand the topic of a part of the document
WCAG: 1.3.1
Score: 22
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: 22
Issue: overflow hidden?
Impact: User may be unable to enlarge the text for readability
WCAG: 1.4.4
Score: 20
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: 20
Issue: control not named
Impact: User cannot get help on how to operate a form item
WCAG: 4.1.2
Score: 16
Elements
None identified
Violations of ibm rules
Rule input_label_exists
Description: Element with the role of a form control has no associated label
Count of instances: 4
Issue: title attribute invalid
Impact: User cannot hover to get help explaining an item
WCAG: 1.3.1
Score: 16
Elements
- /html/body/footer/div[1]/div/div/div/div/div/div[3]/a
- /html/body/footer/div[1]/div/div/div/div/div/div[4]/a
- /html/body/footer/div[1]/div/div/div/div/div/div[5]/a
- /html/body/a
Violations of testaro rules
Rule titledEl
Description: title attribute belongs to an inappropriate element
Count of instances: 4
Issue: font small
Impact: Text is difficult to read
WCAG: 1.4
Score: 15
Elements
None identified
Violations of aslint rules
Rule minimum_font_size
Description: Font size is smaller than 10 pixels
Count of instances: 5
Issue: tab-opening link action unstated
Impact: Following a link opens a new window, surprising a user
WCAG: 3.2.5
Score: 14
Elements
- /html/body/div[1]/nav/div/ul/li[4]/a
- /html/body/footer/div[2]/div[1]/span[2]/a
- /html/body/footer/div[2]/div[2]/div/span/a[1]
- /html/body/footer/div[2]/div[2]/div/span/a[2]
- /html/body/footer/div[2]/div[2]/div/span/a[3]
- /html/body/footer/div[2]/div[2]/div/span/a[4]
- /html/body/footer/div[2]/div[2]/div/span/a[5]
- /html/body/footer/div[2]/div[2]/div/span/a[6]
- /html/body/footer/div[2]/div[2]/div/span/a[7]
Violations of ed11y rules
Rule linkNewWindow
Description: Link opens a new window or tab without prior notice
Count of instances: 9
Issue: inconsistent heading, link, or button styles
Impact: User cannot easily distinguish items of different types
WCAG: 3.2.4
Score: 13
Elements
None identified
Violations of testaro rules
Rule styleDiff
Description: Heading, link, and button style inconsistencies
Count of instances: 13
Issue: interactive component not named
Impact: User cannot get help understanding a custom item
WCAG: 4.1.2
Score: 12
Elements
None identified
Violations of ibm rules
Rule aria_widget_labelled
Description: Interactive component has no programmatically associated name
Count of instances: 3
Issue: operable element not focusable
Impact: Keyboard-only user cannot navigate properly to an operable item
WCAG: 2.1.1
Score: 12
Elements
- /html/body/div[1]/nav/div/ul
- /html/body/div[1]/section[3]/div/ul
- /html/body/div[1]/section[3]/div/ul/li[2]/button
Violations of testaro rules
Rule opFoc
Description: Operable element is not Tab-focusable
Count of instances: 3
Issue: item makes testing inconclusive
Impact: Item prevents a conclusive accessibility test
WCAG: 4.1
Score: 10
Elements
None identified
Violations of alfa rules
Rule cantTell
Description: Test could not give a conclusive result
Count of instances: 10
Issue: text contrast not testable
Impact: Text may be difficult to read
WCAG: 1.4.3
Score: 10
Elements
None identified
Violations of alfa rules
Rule cantTellTextContrast
Description: Test of text contrast could not give a conclusive result
Count of instances: 10
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: 2
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: 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: links named identically
Impact: User cannot get help differentiating links
WCAG: 2.4.4
Score: 10
Elements
None identified
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
Issue: tab-opening link action unstated?
Impact: Following a link opens a new window, possibly surprising a user
WCAG: 3.2.5
Score: 9
Elements
- /html/body/div[1]/nav/div/ul/li[4]/a
- /html/body/footer/div[2]/div[1]/span[2]/a
- /html/body/footer/div[2]/div[2]/div/span/a[1]
- /html/body/footer/div[2]/div[2]/div/span/a[2]
- /html/body/footer/div[2]/div[2]/div/span/a[3]
- /html/body/footer/div[2]/div[2]/div/span/a[4]
- /html/body/footer/div[2]/div[2]/div/span/a[5]
- /html/body/footer/div[2]/div[2]/div/span/a[6]
- /html/body/footer/div[2]/div[2]/div/span/a[7]
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: 9
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: 7
Violations of testaro rules
Rule linkExt
Description: Link opens a new window or tab
Count of instances: 9
Issue: svg image not named
Impact: User cannot get help understanding an image
WCAG: 1.1.1
Score: 8
Elements
None identified
Violations of aslint rules
Rule accessible_svg
Description: Element has no title, description, text, attribute label, or role description
Count of instances: 2
Violations of ibm rules
Rule svg_graphics_labelled
Description: Element is svg but has no accessible name
Count of instances: 2
Issue: image dubiously named
Impact: Helper may describe an image inadequately
WCAG: 1.1.1
Score: 8
Elements
None identified
Violations of aslint rules
Rule alt_color_convey_information
Description: Text alternative may fail to give information provided by colors
Count of instances: 2
Violations of qualWeb rules
Rule QW-WCAG-T8
Description: Text alternative is suspect
Count of instances: 8
Violations of wave rules
Rule alt_suspicious
Description: Image text alternative is suspect
Count of instances: 1
Issue: background image invalid
Impact: Background image is displayed improperly
WCAG: 4.1
Score: 8
Elements
None identified
Violations of nuVal rules
Rule ^CSS: background-image: .+ is not a background-image value.*$
Description: CSS background image is misdefined
Count of instances: 2
Issue: z-index not zero
Impact: User cannot predict the effect of clicking
WCAG: 1.4
Score: 7
Elements
- /html/body/div[1]/section[3]/div/button[1]
- /html/body/div[1]/section[3]/div/div/div/figure[2]
- /html/body/div[1]/section[3]/div/button[2]
- /html/body/div[1]/section[3]/div/ul
- /html/body/div[1]/section[4]/div[1]
- /html/body/div[1]/section[7]/div[2]
- /html/body/div[1]/section[12]/div[1]/button[2]
Violations of testaro rules
Rule zIndex
Description: Element has a nondefault z-index value
Count of instances: 7
Issue: attribute obsolete
Impact: Document includes obsolete code that the browser may fail to process
WCAG: 4.1
Score: 6
Elements
None identified
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: 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: navigations not distinctly named
Impact: User cannot get help on how some of the document is organized
WCAG: 1.3.6
Score: 6
Elements
None identified
Violations of ibm rules
Rule aria_navigation_label_unique
Description: Multiple elements with the navigation role do not have unique labels
Count of instances: 2
Issue: link indication poor
Impact: User cannot differentiate a link from plain text
WCAG: 1.3.3
Score: 6
Elements
- /html/body/div[1]/section[15]/nav/a
- /html/body/div[1]/section[18]/a
- /html/body/div[1]/section[22]/div[2]/div/a
Violations of testaro rules
Rule linkUl
Description: Inline links are not underlined
Count of instances: 3
Issue: text and image link not combined
Impact: Keyboard-only user expends extra effort to skip a link
WCAG: 2.4.4
Score: 6
Elements
None identified
Violations of wave rules
Rule link_redundant
Description: Adjacent links go to the same URL
Count of instances: 3
Issue: text distortion
Impact: Text is difficult to read
WCAG: 3.1.5
Score: 5
Elements
- /html/body/div[1]/section[3]/div/button[1]
- /html/body/div[1]/section[3]/div/div
- /html/body/div[1]/section[3]/div/button[2]
- /html/body/div[1]/section[12]/div[1]/button[1]
- /html/body/div[1]/section[12]/div[1]/button[2]
Violations of testaro rules
Rule distortion
Description: Element text is distorted by a transform style property
Count of instances: 5
Issue: aria attribute invalid
Impact: Item behavior violates user expectations
WCAG: 4.1.2
Score: 4
Elements
None identified
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: 1
Violations of wax rules
Rule Apply aria-roledescription only to elements with a valid ARIA role.
Description: Element has no valid ARIA role but has an aria-roledescription attribute
Count of instances: 1
Issue: dialog not named
Impact: User cannot get help explaining a pop-up window
WCAG: 4.1.2
Score: 4
Elements
None identified
Violations of aslint rules
Rule aria_role_dialog
Description: Element has a dialog role but has no accessible name
Count of instances: 1
Violations of wax rules
Rule Add accessible names to ARIA dialog and alertdialog elements.
Description: Node is ARIA dialog or alertdialog but has no accessible name
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 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 axe rules
Rule frame-title
Description: Frame has no accessible name
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 ibm rules
Rule frame_title_exists
Description: Inline frame has no title attribute
Count of instances: 1
Violations of qualWeb rules
Rule QW-ACT-R19
Description: iframe element has no accessible name
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: 1
Issue: CSS bans page rotation
Impact: User must read sideways after rotating a device
WCAG: 1.3.4
Score: 4
Elements
None identified
Violations of aslint rules
Rule orientation
Description: CSS media query specifies an orientation
Count of instances: 1
Issue: role redundant
Impact: Document includes unnecessary code
WCAG: 4.1.2
Score: 4
Elements
None identified
Violations of ibm rules
Rule aria_role_redundant
Description: Explicitly assigned ARIA role is redundant with the implicit role of the element
Count of instances: 2
Violations of nuVal rules
Rule ^The .+ role is unnecessary for element .+$
Description: explicit role is redundant for its element
Count of instances: 4
Issue: attribute invalid
Impact: Item behaves improperly
WCAG: 1.3.1
Score: 4
Elements
None identified
Violations of ibm rules
Rule aria_attribute_valid
Description: ARIA attribute is invalid for the role of its element
Count of instances: 1
Issue: descendant missing
Impact: Keyboard-only user cannot operate a custom tool
WCAG: 1.3.1
Score: 4
Elements
None identified
Violations of qualWeb rules
Rule QW-ACT-R38
Description: Element has no ARIA required owned element
Count of instances: 1
Violations of wax rules
Rule Ensure elements with ARIA roles contain required child roles.
Description: Element does not contain a child required by its ARIA role
Count of instances: 1
Issue: landmarks not distinctly named
Impact: User cannot get help on how some of the document is organized
WCAG: 1.3.6
Score: 3
Elements
None identified
Violations of axe rules
Rule landmark-unique
Description: Landmark has a role and an accessible name that are identical to another
Count of instances: 1
Violations of wax rules
Rule Provide unique role or role/label/title combinations for landmarks.
Description: Landmark is indistinguishable from another by role, label, or title
Count of instances: 1
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: 3
Elements
None identified
Violations of htmlcs rules
Rule AAA.1_3_1.H42
Description: Heading coding is not used but the element may be intended as a heading
Count of instances: 1
Violations of wave rules
Rule heading_possible
Description: Possible heading
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: 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: 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: box size absolute
Impact: User cannot enlarge the content of an item for readability
WCAG: 1.4.4
Score: 3
Elements
None identified
Violations of qualWeb rules
Rule QW-BP15
Description: Element width is specified in an absolute value
Count of instances: 1
Issue: role assigned instead of implicit
Impact: User may misunderstand the purpose of an item
WCAG: 4.1.2
Score: 3
Elements
- /html/body/div[1]/nav
- /html/body/footer/div[2]/div[1]/span[3]/a
- /html/body/div[2]
Violations of testaro rules
Rule role
Description: Explicitly assigned ARIA role is also an implicit element role
Count of instances: 3
Issue: heading heads nothing
Impact: Helper misdescribes the document
WCAG: 1.3.1
Score: 2
Elements
None identified
Violations of alfa rules
Rule r78
Description: No content between two headings of the same level
Count of instances: 1
Issue: heading level skipped
Impact: Helper misdescribes the document
WCAG: 1.3.1
Score: 2
Elements
- /html/body/div[1]/section[16]/div[2]/div[1]/div[1]/h4
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
Violations of wave rules
Rule heading_skipped
Description: Skipped heading level
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: 2
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: 2
Issue: element not focusable
Impact: Keyboard-only user cannot choose an item to operate
WCAG: 2.1.1
Score: 2
Elements
None identified
Violations of testaro rules
Rule focAll
Description: Discrepancy between elements that should be and that are Tab-focusable
Count of instances: 1
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: custom button keyboard-inoperable?
Impact: Custom item may prevent a keyboard-only user from operating it
WCAG: 2.1.1
Score: 1
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: 1
Issue: tabindex redundant
Impact: Revision risks interfering with navigation by a keyboard-only user
WCAG: 1.3.1
Score: 1
Elements
None identified
Violations of aslint rules
Rule misused_tabindex_attribute
Description: Element has an implicit tabIndex value 0, but also has a tabindex attribute
Count of instances: 1
Issue: link destination not URL
Impact: Helper cannot properly explain a link to a user
WCAG: 1.3.1
Score: 1
Elements
None identified
Violations of aslint rules
Rule unclear_anchor_uri
Description: Link destination is #, a script, or empty
Count of instances: 1
Issue: all-italic text
Impact: Text is difficult to read
WCAG: 3.1.5
Score: 1
Elements
None identified
Violations of aslint rules
Rule font_style_italic
Description: Text longer than 80 characters has an italic font style
Count of instances: 1
Issue: link name vague
Impact: User may misunderstand what a link points to
WCAG: 2.4.4
Score: 1
Elements
- /html/body/div[1]/section[17]/div[2]/p[2]/a
Violations of ed11y rules
Rule linkTextIsGeneric
Description: Element is a link but has generic content
Count of instances: 1
Issue: image name contains image
Impact: User is redundantly told an image is an image
WCAG: 1.1.1
Score: 1
Elements
- /html/body/div[1]/section[21]/div[1]/img
Violations of ed11y rules
Rule altImageOf
Description: alt attribute of the element states the image is an image
Count of instances: 1
Issue: no option focusable
Impact: Keyboard-only user cannot choose an option
WCAG: 2.1.1
Score: 1
Elements
None identified
Violations of ibm rules
Rule aria_child_tabbable
Description: No descendent element with an option role is tabbable
Count of instances: 1
Issue: image link text suspect
Impact: Keyboard-only user may misunderstand the effect of following a link
WCAG: 2.4.4
Score: 1
Elements
None identified
Violations of qualWeb rules
Rule QW-WCAG-T10
Description: Link name repeats its image name and/or that name is suspect
Count of instances: 1
Issue: filter style
Impact: Item is too distorted for understandability
WCAG: 4.1
Score: 1
Elements
- /html/body/div[1]/section[12]/div[1]/button[1]
Violations of testaro rules
Rule filter
Description: Element styles include filter
Count of instances: 1
Issue: title attribute redundant
Impact: Helper repeats the explanation of an item
WCAG: 1.3.1
Score: 1
Elements
- /html/body/a
Violations of testaro rules
Rule linkTitle
Description: Link title value is also contained in the link text
Count of instances: 1
Issue: audio or video alternatives missing?
Impact: User may be unable to get help reading video content as text
WCAG: 1.2.2
Score: 1
Elements
None identified
Violations of wave rules
Rule youtube_video
Description: YouTube video may have no or incorrect captions
Count of instances: 1
Issue: false aria-hidden value risky
Impact: User may be misled by erroneously hidden or revealed document content
WCAG: 2.4.6
Score: 0
Elements
None identified
Violations of aslint rules
Rule aria_hidden_false
Description: aria-hidden attribute has the value false
Count of instances: 1
Elements with issues
Elements exhibiting issues:
Element /html/body/a
- title attribute invalid
- title attribute redundant
Element /html/body/div[1]
- line height low
Element /html/body/div[1]/header/div[1]/div/h1
- line height low
Element /html/body/div[1]/header/div[1]/div/h1/a
- all-capital text
- line height low
Element /html/body/div[1]/nav
- role assigned instead of implicit
Element /html/body/div[1]/nav/button
- target small
Element /html/body/div[1]/nav/div/ul
- operable element not focusable
Element /html/body/div[1]/nav/div/ul/li[1]/a
- focus indication poor
Element /html/body/div[1]/nav/div/ul/li[2]/a
- focus indication poor
Element /html/body/div[1]/nav/div/ul/li[3]/a
- all-capital text
- focus indication poor
Element /html/body/div[1]/nav/div/ul/li[4]/a
- all-capital text
- tab-opening link action unstated
- tab-opening link action unstated?
Element /html/body/div[1]/section[11]/div[1]/img
- image not named
Element /html/body/div[1]/section[11]/div[2]/h2
- line height low
Element /html/body/div[1]/section[11]/div[2]/h2/strong
- line height low
Element /html/body/div[1]/section[12]/div[1]/button[1]
- filter style
- focus indication poor
- target small
- text distortion
Element /html/body/div[1]/section[12]/div[1]/button[2]
- target small
- text distortion
- z-index not zero
Element /html/body/div[1]/section[12]/div[2]/button[1]
- focus indication poor
- target small
Element /html/body/div[1]/section[12]/div[2]/button[2]
- target small
Element /html/body/div[1]/section[12]/div[2]/button[3]
- focus indication poor
- target small
Element /html/body/div[1]/section[12]/div[2]/button[4]
- focus indication poor
- target small
Element /html/body/div[1]/section[13]/div[1]/img
- image not named
Element /html/body/div[1]/section[14]/div/img
- image not named
Element /html/body/div[1]/section[15]/div/div[1]/a
- focus indication poor
Element /html/body/div[1]/section[15]/div/div[1]/a/div/div[1]/img
- image not named
Element /html/body/div[1]/section[15]/div/div[1]/a/div/div[2]/h2
- line height low
Element /html/body/div[1]/section[15]/div/div[2]/a/div/div[1]/img
- image not named
Element /html/body/div[1]/section[15]/div/div[2]/a/div/div[2]/h2
- line height low
Element /html/body/div[1]/section[15]/h1
- line height low
Element /html/body/div[1]/section[15]/nav/a
- line height low
- link indication poor
- target small
Element /html/body/div[1]/section[16]/div[2]/div[1]/div[1]/h4
- heading level skipped
Element /html/body/div[1]/section[16]/div[2]/div[2]/div[1]/h4/a
- focus indication poor
Element /html/body/div[1]/section[16]/h1
- line height low
Element /html/body/div[1]/section[17]/div[1]/img
- image not named
Element /html/body/div[1]/section[17]/div[2]/p[2]/a
- link name vague
- target small
Element /html/body/div[1]/section[18]/a
- link indication poor
- target small
Element /html/body/div[1]/section[21]/div[1]/img
- image name contains image
Element /html/body/div[1]/section[22]/div[2]/div/a
- link indication poor
- target small
Element /html/body/div[1]/section[3]/div/button[1]
- text distortion
- z-index not zero
Element /html/body/div[1]/section[3]/div/button[2]
- focus indication poor
- text distortion
- z-index not zero
Element /html/body/div[1]/section[3]/div/div
- text distortion
Element /html/body/div[1]/section[3]/div/div/div/figure[1]/div[2]/h1
- all-capital text
- line height low
Element /html/body/div[1]/section[3]/div/div/div/figure[2]
- z-index not zero
Element /html/body/div[1]/section[3]/div/div/div/figure[2]/div[2]/h1
- line height low
Element /html/body/div[1]/section[3]/div/div/div/figure[2]/div[2]/p
- line height low
Element /html/body/div[1]/section[3]/div/div/div/figure[3]/div[2]/h1
- line height low
Element /html/body/div[1]/section[3]/div/div/div/figure[3]/div[2]/p
- line height low
Element /html/body/div[1]/section[3]/div/ul
- operable element not focusable
- z-index not zero
Element /html/body/div[1]/section[3]/div/ul/li[1]/button
- focus indication poor
- target small
Element /html/body/div[1]/section[3]/div/ul/li[2]/button
- operable element not focusable
- target small
Element /html/body/div[1]/section[3]/div/ul/li[3]/button
- target small
Element /html/body/div[1]/section[4]/div[1]
- z-index not zero
Element /html/body/div[1]/section[4]/div[1]/h2
- line height low
Element /html/body/div[1]/section[4]/div[1]/p/div/iframe
- focus indication poor
Element /html/body/div[1]/section[4]/div[2]/img
- image not named
Element /html/body/div[1]/section[7]/div[1]/img
- image not named
Element /html/body/div[1]/section[7]/div[2]
- z-index not zero
Element /html/body/div[1]/section[7]/div[2]/h2
- line height low
Element /html/body/div[1]/section[8]/div[2]/h1
- line height low
Element /html/body/div[2]
- role assigned instead of implicit
Element /html/body/footer/div[1]/div/div/div/div/div/div[3]/a
- target small
- title attribute invalid
Element /html/body/footer/div[1]/div/div/div/div/div/div[4]/a
- target small
- title attribute invalid
Element /html/body/footer/div[1]/div/div/div/div/div/div[5]/a
- target small
- title attribute invalid
Element /html/body/footer/div[2]/div[1]/span[2]/a
- tab-opening link action unstated
- tab-opening link action unstated?
- target small
Element /html/body/footer/div[2]/div[1]/span[3]/a
- role assigned instead of implicit
- target small
Element /html/body/footer/div[2]/div[2]/div/span/a[1]
- tab-opening link action unstated
- tab-opening link action unstated?
- target small
Element /html/body/footer/div[2]/div[2]/div/span/a[2]
- tab-opening link action unstated
- tab-opening link action unstated?
- target small
Element /html/body/footer/div[2]/div[2]/div/span/a[3]
- tab-opening link action unstated
- tab-opening link action unstated?
- target small
Element /html/body/footer/div[2]/div[2]/div/span/a[4]
- tab-opening link action unstated
- tab-opening link action unstated?
- target small
Element /html/body/footer/div[2]/div[2]/div/span/a[5]
- tab-opening link action unstated
- tab-opening link action unstated?
- target small
Element /html/body/footer/div[2]/div[2]/div/span/a[6]
- tab-opening link action unstated
- tab-opening link action unstated?
- target small
Element /html/body/footer/div[2]/div[2]/div/span/a[7]
- tab-opening link action unstated
- tab-opening link action unstated?
- target small