Accessibility digest
Contents
| Page | Scott Morrow;Democratic;Wyoming |
|---|---|
| URL | https://morrowforwyoming.com/ |
| Test date | 2024/09/22 |
| Score | 1167 |
| 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-2k.json |
Introduction
How accessible is the Scott Morrow;Democratic;Wyoming web page at https://morrowforwyoming.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 1167, the sum of 320 for the count of issues, 366 for specific issues, 0 for unclassified rule violations, 71 for tool-by-tool ratings, 76 for the count of violating elements, 300 for the page preventing tools from running, 34 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 |
|---|---|---|---|---|
| main missing | 1.3.6 | 2 | 62 | axe:1 |
| line height low | 1.4.8 | 2 | 38 | alfa:1, testaro:19 |
| content beyond landmarks | 1.3.6 | 1 | 36 | alfa:36, axe:4, ibm:9, wax:0 |
| CSS invalid | 4.1 | 3 | 36 | nuVal:12 |
| void element has trailing slash | 4.1 | 1 | 31 | nuVal:31 |
| parent invalid | 1.3.1 | 4 | 24 | nuVal:6, ibm:0 |
| title attribute invalid | 1.3.1 | 4 | 24 | testaro:6 |
| link indication poor | 1.3.3 | 2 | 16 | testaro:8, alfa:0, axe:0 |
| links named identically | 2.4.4 | 2 | 14 | aslint:3, qualWeb:7, testaro:3 |
| contrast poor | 1.4.3 | 4 | 12 | axe:2, ibm:3, qualWeb:2, wave:2, alfa:0, aslint:0, htmlcs:0, wax:0 |
| element in head invalid | 4.1.1 | 3 | 12 | testaro:4, aslint:0 |
| target small | 2.5.5 | 1 | 9 | alfa:9, testaro:9 |
| text contrast improvable | 1.4.6 | 1 | 7 | alfa:4, aslint:6, axe:4, htmlcs:4, qualWeb:7, wax:0 |
| text and image link not combined | 2.4.4 | 2 | 6 | wave:3, aslint:0, qualWeb:0 |
| text contrast not testable | 1.4.3 | 1 | 4 | alfa:4, aslint:0, htmlcs:0 |
| figure not named | 1.1.1 | 4 | 4 | ibm:1 |
| inconsistent heading, link, or button styles | 3.2.4 | 1 | 4 | testaro:4 |
| link name vague | 2.4.4 | 1 | 3 | aslint:3, ed11y:3, wave:3 |
| 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 |
| overflow hidden? | 1.4.4 | 1 | 3 | qualWeb:3 |
| z-index not zero | 1.4 | 1 | 3 | testaro:3 |
| all-capital text | 3.1.5 | 1 | 2 | aslint:2, testaro:1, alfa:0, ed11y:0 |
| type redundant | 1.3.1 | 1 | 2 | nuVal:2 |
| item makes testing inconclusive | 4.1 | 1 | 1 | alfa:1 |
| links dubiously share name | 2.4.4 | 1 | 1 | axe:1 |
| image dubiously marked decorative | 1.1.1 | 1 | 1 | htmlcs:1 |
| heading-like styles dubious | 1.3.1 | 1 | 1 | htmlcs:1, axe:0, ed11y:0, wave:0 |
| image dubiously named | 1.1.1 | 1 | 1 | qualWeb:1, aslint:0, wave:0 |
| all-italic text | 3.1.5 | 1 | 1 | testaro:1, alfa:0, aslint:0 |
| text distortion | 3.1.5 | 1 | 1 | testaro:1 |
| noscript element not equivalent? | 4.1 | 1 | 1 | wave:1 |
Itemized issues
The reported rule violations are itemized below, issue by issue. Additional details can be inspected in the full report.
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: line height low
Impact: Text is difficult to read
WCAG: 1.4.8
Score: 38
Elements
- /html/body/div[1]/div/div[1]/div[2]/h1
- /html/body/div[1]/div/div[2]/div/div/p
- /html/body/div[1]/div/div[2]/div/div/p/em[1]
- /html/body/div[1]/div/div[2]/div/div/p/em[2]
- /html/body/div[1]/div/div[2]/div/div/p/em[3]
- /html/body/div[1]/div/div[2]/div/div/p/em[4]
- /html/body/div[1]/div/div[2]/div/div/p/a
- /html/body/div[1]/div/div[3]/div/div[1]/h2
- /html/body/div[1]/div/div[3]/div/div[1]/h2/strong
- /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[1]/h2
- /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[1]/h2/a
- /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[2]/h2
- /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[2]/h2/a
- /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[3]/h2
- /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[3]/h2/a
- /html/body/div[1]/div/div[3]/div/div[2]/h2
- /html/body/div[1]/div/div[3]/div/div[2]/h2/strong
- /html/body/div[1]/footer/div[1]/h1
- /html/body/div[1]/footer/div[1]/h1/a
Violations of alfa rules
Rule r73
Description: Text line height is not at least 1.5
Count of instances: 1
Violations of testaro rules
Rule lineHeight
Description: Text has a line height less than 1.5 times its font size
Count of instances: 19
Issue: content beyond landmarks
Impact: User cannot get help on how some of the document is organized
WCAG: 1.3.6
Score: 36
Elements
None identified
Violations of alfa rules
Rule r57
Description: Perceivable text content is not included in any landmark
Count of instances: 36
Violations of axe rules
Rule region
Description: Some page content is not contained by landmarks
Count of instances: 4
Violations of ibm rules
Rule aria_content_in_landmark
Description: Content is not within a landmark element
Count of instances: 9
Issue: CSS invalid
Impact: Document cannot be properly displayed
WCAG: 4.1
Score: 36
Elements
None identified
Violations of nuVal rules
Rule ^CSS: .+: Property .+ doesn't exist.*$
Description: Invalid property in CSS
Count of instances: 4
Rule ^CSS: .+: .+ is not a .+ value.*$
Description: Invalid value in CSS
Count of instances: 2
Rule ^CSS: .+: Parse Error.*$
Description: Invalid CSS
Count of instances: 6
Issue: void element has trailing slash
Impact: Document contains invalid code
WCAG: 4.1
Score: 31
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: 31
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: title attribute invalid
Impact: User cannot hover to get help explaining an item
WCAG: 1.3.1
Score: 24
Elements
- /html/head/link[1]
- /html/head/link[2]
- /html/head/link[7]
- /html/head/link[8]
- /html/head/link[11]
- /html/head/link[12]
Violations of testaro rules
Rule titledEl
Description: title attribute belongs to an inappropriate element
Count of instances: 6
Issue: link indication poor
Impact: User cannot differentiate a link from plain text
WCAG: 1.3.3
Score: 16
Elements
- /html/body/div[1]/div/div[1]/div[2]/div/div[1]/a
- /html/body/div[1]/div/div[1]/div[2]/div/div[2]/a
- /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[1]/h2/a
- /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[2]/h2/a
- /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[3]/h2/a
- /html/body/div[1]/div/div[3]/div/div[1]/div/div/div/a
- /html/body/div[1]/div/div[3]/div/div[2]/div/div/a
- /html/body/div[1]/footer/div[1]/h1/a
Violations of testaro rules
Rule linkUl
Description: Inline links are not underlined
Count of instances: 8
Issue: links named identically
Impact: User cannot get help differentiating links
WCAG: 2.4.4
Score: 14
Elements
- /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[2]/div[2]/p[2]/a
- /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[3]/div[2]/p[2]/a
- /html/body/div[1]/footer/div[1]/h1/a
Violations of aslint rules
Rule links_same_content_different_url
Description: Links with the same text content have different destination URLs
Count of instances: 3
Violations of qualWeb rules
Rule QW-ACT-R9
Description: Links with identical accessible names have different purposes
Count of instances: 5
Rule QW-ACT-R44
Description: Links with identical accessible names and context serve different purposes
Count of instances: 2
Violations of testaro rules
Rule linkAmb
Description: Links with the same text content have different destinations
Count of instances: 3
Issue: contrast poor
Impact: Content is difficult to understand
WCAG: 1.4.3
Score: 12
Elements
None identified
Violations of axe rules
Rule color-contrast
Description: Element has insufficient color contrast
Count of instances: 2
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: 3
Violations of qualWeb rules
Rule QW-ACT-R37
Description: Text has less than the minimum contrast
Count of instances: 2
Violations of wave rules
Rule contrast
Description: Very low contrast
Count of instances: 2
Issue: element in head invalid
Impact: Browser processes the document improperly
WCAG: 4.1.1
Score: 12
Elements
None identified
Violations of testaro rules
Rule headEl
Description: Elements in the head are not allowed there
Count of instances: 4
Issue: target small
Impact: User cannot reliably choose an item to click or tap
WCAG: 2.5.5
Score: 9
Elements
- /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[1]/h2/a
- /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[1]/div[2]/p[2]/a
- /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[2]/h2/a
- /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[2]/div[2]/p[2]/a
- /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[3]/h2/a
- /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[3]/div[2]/p[2]/a
- /html/body/div[1]/div/div[3]/div/div[1]/div/div/div/a
- /html/body/div[1]/div/div[3]/div/div[2]/div/div/a
- /html/body/div[1]/footer/div[1]/h1/a
Violations of alfa rules
Rule r111
Description: Target size is suboptimal
Count of instances: 9
Violations of testaro rules
Rule targetSize
Description: Button, input, or non-inline link is smaller than 44 px wide and high
Count of instances: 9
Issue: text contrast improvable
Impact: Content is not easy to understand
WCAG: 1.4.6
Score: 7
Elements
None identified
Violations of alfa rules
Rule r66
Description: Text contrast less than AAA requires
Count of instances: 4
Violations of aslint rules
Rule color_contrast_aaa4
Description: Text has contrast less than 4.5:1
Count of instances: 1
Rule color_contrast_aaa7
Description: Text has contrast less than 7:1
Count of instances: 5
Violations of axe rules
Rule color-contrast-enhanced
Description: Element has insufficient color contrast (Level AAA)
Count of instances: 4
Violations of htmlcs rules
Rule AAA.1_4_6.G17.Fail
Description: Text has insufficient contrast
Count of instances: 4
Violations of qualWeb rules
Rule QW-ACT-R76
Description: Text has less than the enhanced minimum contrast
Count of instances: 7
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 contrast not testable
Impact: Text may be difficult to read
WCAG: 1.4.3
Score: 4
Elements
None identified
Violations of alfa rules
Rule cantTellTextContrast
Description: Test of text contrast could not give a conclusive result
Count of instances: 4
Issue: figure not named
Impact: User cannot get help on the topic of a figure
WCAG: 1.1.1
Score: 4
Elements
None identified
Violations of ibm rules
Rule figure_label_exists
Description: figure element has no associated label
Count of instances: 1
Issue: inconsistent heading, link, or button styles
Impact: User cannot easily distinguish items of different types
WCAG: 3.2.4
Score: 4
Elements
None identified
Violations of testaro rules
Rule styleDiff
Description: Heading, link, and button style inconsistencies
Count of instances: 4
Issue: link name vague
Impact: User may misunderstand what a link points to
WCAG: 2.4.4
Score: 3
Elements
- /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[1]/div[2]/p[2]/a
- /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[2]/div[2]/p[2]/a
- /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[3]/div[2]/p[2]/a
Violations of aslint rules
Rule link_with_unclear_purpose
Description: Element is a link but has vague or generic content
Count of instances: 3
Violations of ed11y rules
Rule linkTextIsGeneric
Description: Element is a link but has generic content
Count of instances: 3
Violations of wave rules
Rule link_suspicious
Description: Suspicious link text
Count of instances: 3
Issue: role invalid
Impact: User cannot get help on the nature of an item
WCAG: 4.1.2
Score: 3
Elements
None identified
Violations of ibm rules
Rule aria_contentinfo_misuse
Description: Element with a contentinfo role is present without an element with a main role
Count of instances: 1
Issue: 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: overflow hidden?
Impact: User may be unable to enlarge the text for readability
WCAG: 1.4.4
Score: 3
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: 3
Issue: z-index not zero
Impact: User cannot predict the effect of clicking
WCAG: 1.4
Score: 3
Elements
- /html/body/div[1]/div/div[1]/span
- /html/body/div[1]/div/div[1]/div[1]
- /html/body/div[1]/div/div[1]/div[2]
Violations of testaro rules
Rule zIndex
Description: Element has a nondefault z-index value
Count of instances: 3
Issue: all-capital text
Impact: Text is difficult to read
WCAG: 3.1.5
Score: 2
Elements
- /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[2]/h2/a
Violations of aslint rules
Rule capital_letters_words
Description: Element or its title has entirely 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: 1
Issue: type redundant
Impact: Document includes unnecessary code
WCAG: 1.3.1
Score: 2
Elements
None identified
Violations of nuVal rules
Rule The type attribute for the style element is not needed and should be omitted.
Description: type attribute is unnecessary for a style element
Count of instances: 2
Issue: item makes testing inconclusive
Impact: Item prevents a conclusive accessibility test
WCAG: 4.1
Score: 1
Elements
None identified
Violations of alfa rules
Rule cantTell
Description: Test could not give a conclusive result
Count of instances: 1
Issue: links dubiously share name
Impact: User may be unable to get help differentiating links
WCAG: 2.4.4
Score: 1
Elements
None identified
Violations of axe rules
Rule identical-links-same-purpose
Description: Links with the same accessible name may serve dissimilar purposes
Count of instances: 1
Issue: image dubiously marked decorative
Impact: Helper ignores an image that is apparently informative
WCAG: 1.1.1
Score: 1
Elements
None identified
Violations of htmlcs rules
Rule AAA.1_1_1.H67.2
Description: Image marked as decorative may be informative
Count of instances: 1
Issue: heading-like styles dubious
Impact: User may be unable to understand the topic of a part of the document
WCAG: 1.3.1
Score: 1
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
Issue: image dubiously named
Impact: Helper may describe an image inadequately
WCAG: 1.1.1
Score: 1
Elements
None identified
Violations of qualWeb rules
Rule QW-WCAG-T8
Description: Text alternative is suspect
Count of instances: 1
Issue: all-italic text
Impact: Text is difficult to read
WCAG: 3.1.5
Score: 1
Elements
- /html/body/div[1]/footer/div[1]/p/em
Violations of testaro rules
Rule allSlanted
Description: Element has a text substring of at least 40 italic or oblique characters
Count of instances: 1
Issue: text distortion
Impact: Text is difficult to read
WCAG: 3.1.5
Score: 1
Elements
- /html/body/div[1]/div/div[1]/div[2]/div/div[2]
Violations of testaro rules
Rule distortion
Description: Element text is distorted by a transform style property
Count of instances: 1
Issue: noscript element not equivalent?
Impact: User who has disabled JavaScript may be denied some content
WCAG: 4.1
Score: 1
Elements
None identified
Violations of wave rules
Rule noscript
Description: noscript element may fail to contain an accessible equivalent or alternative
Count of instances: 1
Elements with issues
Elements exhibiting issues:
Element /html/body/div[1]/div/div[1]/div[1]
- z-index not zero
Element /html/body/div[1]/div/div[1]/div[2]
- z-index not zero
Element /html/body/div[1]/div/div[1]/div[2]/div/div[1]/a
- link indication poor
Element /html/body/div[1]/div/div[1]/div[2]/div/div[2]
- text distortion
Element /html/body/div[1]/div/div[1]/div[2]/div/div[2]/a
- link indication poor
Element /html/body/div[1]/div/div[1]/div[2]/h1
- line height low
Element /html/body/div[1]/div/div[1]/span
- z-index not zero
Element /html/body/div[1]/div/div[2]/div/div/p
- line height low
Element /html/body/div[1]/div/div[2]/div/div/p/a
- line height low
Element /html/body/div[1]/div/div[2]/div/div/p/em[1]
- line height low
Element /html/body/div[1]/div/div[2]/div/div/p/em[2]
- line height low
Element /html/body/div[1]/div/div[2]/div/div/p/em[3]
- line height low
Element /html/body/div[1]/div/div[2]/div/div/p/em[4]
- line height low
Element /html/body/div[1]/div/div[3]/div/div[1]/div/div/div/a
- link indication poor
- target small
Element /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[1]/div[2]/p[2]/a
- link name vague
- target small
Element /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[1]/h2
- line height low
Element /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[1]/h2/a
- line height low
- link indication poor
- target small
Element /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[2]/div[2]/p[2]/a
- link name vague
- links named identically
- target small
Element /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[2]/h2
- line height low
Element /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[2]/h2/a
- all-capital text
- line height low
- link indication poor
- target small
Element /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[3]/div[2]/p[2]/a
- link name vague
- links named identically
- target small
Element /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[3]/h2
- line height low
Element /html/body/div[1]/div/div[3]/div/div[1]/div/ul/li[3]/h2/a
- line height low
- link indication poor
- target small
Element /html/body/div[1]/div/div[3]/div/div[1]/h2
- line height low
Element /html/body/div[1]/div/div[3]/div/div[1]/h2/strong
- line height low
Element /html/body/div[1]/div/div[3]/div/div[2]/div/div/a
- link indication poor
- target small
Element /html/body/div[1]/div/div[3]/div/div[2]/h2
- line height low
Element /html/body/div[1]/div/div[3]/div/div[2]/h2/strong
- line height low
Element /html/body/div[1]/footer/div[1]/h1
- line height low
Element /html/body/div[1]/footer/div[1]/h1/a
- line height low
- link indication poor
- links named identically
- target small
Element /html/body/div[1]/footer/div[1]/p/em
- all-italic text
Element /html/head/link[11]
- title attribute invalid
Element /html/head/link[12]
- title attribute invalid
Element /html/head/link[1]
- title attribute invalid
Element /html/head/link[2]
- title attribute invalid
Element /html/head/link[7]
- title attribute invalid
Element /html/head/link[8]
- title attribute invalid