Accessibility digest

Contents

Synopsis
PageKirsten Gillibrand;Democratic;New York
URLhttps://kirstengillibrand.com/
Test date2024/09/22
Score1430
Configuration
Redirectionspermitted
Tool isolationno
Report format(s)standard
Requester
Devicedefault
Browser typewebkit
Reduced motionnot requested
Tested byTestaro, procedure senate2024
Scored byTestilo, procedure tsp50
Digested byTestilo, procedure tdp50
Full report 240915T1658-ikz-1k.json

Introduction

How accessible is the Kirsten Gillibrand;Democratic;New York web page at https://kirstengillibrand.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 1430, the sum of 380 for the count of issues, 745 for specific issues, 0 for unclassified rule violations, 83 for tool-by-tool ratings, 186 for the count of violating elements, 0 for the page preventing tools from running, 36 for browser warnings, and 0 for delayed page responses.

How the page was scored

Introduction

This is an explanation of the scoring of the page.

Motivations for scoring

Why score? Specifically, why aggregate many facts about a page into a single number?

One motivation is to simplify comparison and tracking. If you want to compare a page with other pages, or if you want to track changes in a page over time, aggregating many test results for each page into one page score simplifies the task. It becomes possible to say things like Page A is more accessible than page B or Page A is becoming more accessible over time.

Another motivation is to influence behavior. A score arises from decisions about importance, urgency, and other attributes. People may use scores to award benefits, impose costs, or prioritize work. So, scoring can influence who gets and does what.

How to score?

Scoring is subjective. Accessibility testing tools use various scoring procedures, based on various ideas.

The built-in scoring procedures of Testilo are based on the idea that multiple attributes should affect a web-page accessibility score, including:

Some ideas found elsewhere in accessibility scoring are rejected by the Testilo procedures:

Scoring method summary

The scoring method is found in the code of the procedure. The file for any procedure tspnn is in the file procs/score/tspnn.js within the Testilo package.

The score computed by this procedure for any page is a non-negative number. The numbers represent accessibility faults, so a higher-scoring page is considered less accessible than a lower-scoring page. The best possible score is 0.

The procedure makes the score of a page the sum of 7 components:

Scoring method details

The above component descriptions omit various details.

About a thousand tool rules are classified into issues in the tic50.js file used by this procedure. Each of those rules has a quality, ranging from 0 to 1. When the issue score is computed, the count of violations of each rule is multiplied by the quality of that rule. Whichever tool has the largest quality-weighted violation count for an issue, that count is treated as the instance count for the issue. Thus, if 8 tools each report 15 violations within the issue, and their rule qualities are all 1, the instance count is 15, not 120. Moreover, the issue itself has a weight, ranging from 1 to 4, representing its importance. This instance count is multiplied by that weight. That product is further multiplied by the issueCountWeight value, namely 10. That final product is further adjusted if the issue is inherently limited in instance count. For example, if the issue is that the page html element has no lang attribute, the instance count is limited to 1. If there is such a limit, the maxWeight value, namely 30, is divided by the actual instance count and the quotient is added to 1. That product (or 1 if there is no limit) is multiplied by the instance count, and then the result is treated as the contribution of the issue to the issue score.

Each solo (not yet issue-classified) rule violation is multiplied by the sum of 1 and the ordinal severity of the rule, to produce the solo score.

Each rule violation reported by each tool is severity-weighted in the same way as solo rule violations are. Then the sum of those violations is multiplied by the toolWeight value, namely 0.1, to produce the tool score.

The count of elements reported as violators of any rule is multiplied by the elementWeight value, namely 2, to produce the element score.

The count of prevented Testaro rules is multiplied by the testaroRulePreventionWeight quantity, namely 30, and the count of other prevented tools is multiplied by the preventionWeight value, namely 300, to produce the prevention score.

The log score is the sum of several components:

Each of these components is multiplied by a weight found in the logWeights object.

Finally, the latency score is based on how much longer it took for the page to become loaded and stable than expected. The expected total duration in seconds is the normalLatency value, namely 22 seconds (that is 2 seconds per visit, multiplied by the 11 visits of the 11 tools). This is subtracted from the actual total latency, and that difference is multiplied by the latencyWeight amount, namely 2.

Issue summary

Details about this summary

The summary

Sorting is by score.

How many violations each tool reported, by issue
IssueWCAGWeightScoreInstance counts
meta bans zoom1.4.44248alfa:1, aslint:1, axe:1, nuVal:2, qualWeb:1, wax:1
focus indication poor2.4.7468testaro:17, alfa:0, aslint:0
line height low1.4.8250testaro:25, alfa:0
src empty1.3.1448nuVal:12
figure not named1.1.1440ibm:10
font small1.4336aslint:12, wave:1, alfa:0, testaro:0
type redundant1.3.1129nuVal:29
void element has trailing slash4.1126nuVal:26
link indication poor1.3.3218testaro:9, alfa:0, axe:0
link not named2.4.4416alfa:4, axe:4, ibm:4, qualWeb:4, ed11y:0, htmlcs:0, wave:0, wax:0
tab-opening link action unstated?3.2.5116aslint:16, htmlcs:12, testaro:16
link not named2.4.4416aslint:4, ed11y:4, htmlcs:4, qualWeb:4, wave:4, wax:4
element beyond display when focused1.4.10315testaro:5
tab-opening link action unstated3.2.5311ed11y:7
overflow hidden?1.4.4110qualWeb:10
target small2.5.519alfa:1, testaro:9
all-capital text3.1.518aslint:8, testaro:1, alfa:0, ed11y:0
links named identically2.4.428aslint:4, qualWeb:0, testaro:0
image not named1.1.148nuVal:1, wave:2, wax:2, alfa:0, axe:0, ed11y:0, htmlcs:0, ibm:0, qualWeb:0
text distortion3.1.518testaro:8
code obsolete4.136ibm:2, nuVal:0
navigations not distinctly named1.3.636ibm:2
meta invalid1.3.136nuVal:2
element not focusable2.1.146testaro:3, alfa:0, qualWeb:0
text contrast not testable1.4.315alfa:4, htmlcs:5, aslint:0
contrast poor1.4.344axe:1, alfa:0, aslint:0, htmlcs:0, ibm:0, qualWeb:0, wave:0, wax:0
attribute value invalid1.3.144nuVal:1, ibm:0, wax:0
inconsistent heading, link, or button styles3.2.414testaro:4
landmarks not distinctly named1.3.633axe:1, ibm:1, wax:1
z-index not zero1.413testaro:3
aside child of landmark1.3.622axe:1, qualWeb:0, wax:0
noscript element not equivalent?4.112wave:2
image dubiously marked decorative1.1.111htmlcs:1
position sticky1.4.1011htmlcs:1, aslint:0
content beyond landmarks1.3.611ibm:1, alfa:0, axe:0, wax:0
complementary not named1.3.611ibm:1
image link text suspect2.4.411qualWeb:1
image dubiously named1.1.111qualWeb:1, aslint:0, wave:0

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

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: focus indication poor

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

WCAG: 2.4.7

Score: 68

Elements

Violations of testaro rules

Rule focInd

Description: Focused element displays a nonstandard or no focus indicator

Count of instances: 17

Issue: line height low

Impact: Text is difficult to read

WCAG: 1.4.8

Score: 50

Elements

Violations of testaro rules

Rule lineHeight

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

Count of instances: 25

Issue: src empty

Impact: Image, audio, or video to be shown cannot be found

WCAG: 1.3.1

Score: 48

Elements

None identified

Violations of nuVal rules

Rule ^Bad value for attribute src on element .+: Must be non-empty.*$

Description: src attribute is empty

Count of instances: 12

Issue: figure not named

Impact: User cannot get help on the topic of a figure

WCAG: 1.1.1

Score: 40

Elements

Violations of ibm rules

Rule figure_label_exists

Description: figure element has no associated label

Count of instances: 10

Issue: font small

Impact: Text is difficult to read

WCAG: 1.4

Score: 36

Elements

Violations of aslint rules

Rule minimum_font_size

Description: Font size is smaller than 10 pixels

Count of instances: 12

Violations of wave rules

Rule text_small

Description: Text is very small

Count of instances: 1

Issue: type redundant

Impact: Document includes unnecessary code

WCAG: 1.3.1

Score: 29

Elements

None identified

Violations of nuVal rules

Rule The type attribute is unnecessary for JavaScript resources.

Description: type attribute is unnecessary for a JavaScript resource

Count of instances: 23

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

Issue: void element has trailing slash

Impact: Document contains invalid code

WCAG: 4.1

Score: 26

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

Issue: link indication poor

Impact: User cannot differentiate a link from plain text

WCAG: 1.3.3

Score: 18

Elements

Violations of testaro rules

Rule linkUl

Description: Inline links are not underlined

Count of instances: 9

Issue: link not named

Impact: User cannot get help understanding what a link points to

WCAG: 2.4.4

Score: 16

Elements

Violations of alfa rules

Rule r11

Description: Link has no accessible name

Count of instances: 4

Violations of axe rules

Rule link-name

Description: Link has no discernible text

Count of instances: 4

Violations of ibm rules

Rule a_text_purpose

Description: Hyperlink has no link text, label, or image with a text alternative

Count of instances: 4

Violations of qualWeb rules

Rule QW-ACT-R12

Description: Link has no accessible name

Count of instances: 4

Issue: tab-opening link action unstated?

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

WCAG: 3.2.5

Score: 16

Elements

Violations of aslint rules

Rule links_new_window_mark

Description: Indicator that the link opens a new window or tab may be missing

Count of instances: 16

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

Violations of testaro rules

Rule linkExt

Description: Link opens a new window or tab

Count of instances: 16

Issue: link not named

Impact: User cannot get help understanding what a link points to

WCAG: 2.4.4

Score: 16

Elements

Violations of aslint rules

Rule img_empty_alt_in_link

Description: Element is an image in a link but has no text alternative

Count of instances: 4

Violations of ed11y rules

Rule altEmptyLinked

Description: Link name is only an image with no text alternative

Count of instances: 4

Violations of htmlcs rules

Rule AAA.1_1_1.H30.2

Description: img element is the only link content but has no text alternative

Count of instances: 4

Violations of qualWeb rules

Rule QW-WCAG-T21

Description: Accessible name is not provided for an image which is the only content in a link

Count of instances: 4

Violations of wave rules

Rule alt_link_missing

Description: Linked image has no text alternative

Count of instances: 4

Violations of wax rules

Rule Img element is the only content of the link, but is missing alt text. The alt text should describe the purpose of the link.

Description: Link content is an image without a text alternative describing the link purpose

Count of instances: 4

Issue: element beyond display when focused

Impact: Keyboard-only user cannot navigate properly to the operable items

WCAG: 1.4.10

Score: 15

Elements

Violations of testaro rules

Rule focVis

Description: Element when focused is off the display

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

Elements

Violations of ed11y rules

Rule linkNewWindow

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

Count of instances: 7

Issue: overflow hidden?

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

WCAG: 1.4.4

Score: 10

Elements

Violations of qualWeb rules

Rule QW-ACT-R40

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

Count of instances: 10

Issue: target small

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

WCAG: 2.5.5

Score: 9

Elements

Violations of alfa rules

Rule r111

Description: Target size is suboptimal

Count of instances: 1

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: all-capital text

Impact: Text is difficult to read

WCAG: 3.1.5

Score: 8

Elements

Violations of aslint rules

Rule capital_letters_words

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

Count of instances: 8

Violations of testaro rules

Rule allCaps

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

Count of instances: 1

Issue: links named identically

Impact: User cannot get help differentiating links

WCAG: 2.4.4

Score: 8

Elements

Violations of aslint rules

Rule links_same_content_different_url

Description: Links with the same text content have different destination URLs

Count of instances: 4

Issue: image not named

Impact: User cannot get help to know what is in an image

WCAG: 1.1.1

Score: 8

Elements

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

Violations of wave rules

Rule alt_spacer_missing

Description: Spacer image has no text alternative

Count of instances: 2

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

Issue: text distortion

Impact: Text is difficult to read

WCAG: 3.1.5

Score: 8

Elements

Violations of testaro rules

Rule distortion

Description: Element text is distorted by a transform style property

Count of instances: 8

Issue: code obsolete

Impact: Document contains code that is no longer standard

WCAG: 4.1

Score: 6

Elements

Violations of ibm rules

Rule element_attribute_deprecated

Description: Element or attribute is obsolete

Count of instances: 2

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

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: meta invalid

Impact: Document fails to include needed data

WCAG: 1.3.1

Score: 6

Elements

None identified

Violations of nuVal rules

Rule A meta element with an http-equiv attribute whose value is X-UA-Compatible must have a content attribute with the value IE=edge.

Description: Element with http-equiv="X-UA-Compatible" has no content="IE=edge"

Count of instances: 2

Issue: element not focusable

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

WCAG: 2.1.1

Score: 6

Elements

None identified

Violations of testaro rules

Rule focAll

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

Count of instances: 3

Issue: text contrast not testable

Impact: Text may be difficult to read

WCAG: 1.4.3

Score: 5

Elements

Violations of alfa rules

Rule cantTellTextContrast

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

Count of instances: 4

Violations of htmlcs rules

Rule AAA.1_4_3_F24.F24.FGColour

Description: Inline foreground color may lack a complementary background color

Count of instances: 1

Rule AAA.1_4_6.G17.Abs

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

Count of instances: 2

Rule AAA.1_4_6.G18.Abs

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

Count of instances: 2

Issue: contrast poor

Impact: Content is difficult to understand

WCAG: 1.4.3

Score: 4

Elements

Violations of axe rules

Rule color-contrast

Description: Element has insufficient color contrast

Count of instances: 1

Issue: attribute value invalid

Impact: Item behaves improperly

WCAG: 1.3.1

Score: 4

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: 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: landmarks not distinctly named

Impact: User cannot get help on how some of the document is organized

WCAG: 1.3.6

Score: 3

Elements

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 ibm rules

Rule aria_landmark_name_unique

Description: Multiple landmarks with the same parent region are not distinguished from one 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: z-index not zero

Impact: User cannot predict the effect of clicking

WCAG: 1.4

Score: 3

Elements

Violations of testaro rules

Rule zIndex

Description: Element has a nondefault z-index value

Count of instances: 3

Issue: aside child of landmark

Impact: User cannot get help on how some of the document is organized

WCAG: 1.3.6

Score: 2

Elements

Violations of axe rules

Rule landmark-complementary-is-top-level

Description: complementary landmark (aside) is contained in another landmark

Count of instances: 1

Issue: noscript element not equivalent?

Impact: User who has disabled JavaScript may be denied some content

WCAG: 4.1

Score: 2

Elements

Violations of wave rules

Rule noscript

Description: noscript element may fail to contain an accessible equivalent or alternative

Count of instances: 2

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: 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: content beyond landmarks

Impact: User cannot get help on how some of the document is organized

WCAG: 1.3.6

Score: 1

Elements

Violations of ibm rules

Rule aria_content_in_landmark

Description: Content is not within a landmark element

Count of instances: 1

Issue: complementary not named

Impact: User cannot get help on how some of the document is organized

WCAG: 1.3.6

Score: 1

Elements

Violations of ibm rules

Rule aria_complementary_labelled

Description: Element with a complementary role has no label

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

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: image dubiously named

Impact: Helper may describe an image inadequately

WCAG: 1.1.1

Score: 1

Elements

Violations of qualWeb rules

Rule QW-WCAG-T8

Description: Text alternative is suspect

Count of instances: 1

Elements with issues

Elements exhibiting issues:

Element /html/body/a
Element /html/body/div[1]/header
Element /html/body/div[1]/header/div
Element /html/body/div[1]/header/div/a
Element /html/body/div[1]/header/div/a/div
Element /html/body/div[1]/header/div/a/img
Element /html/body/div[1]/header/nav[1]
Element /html/body/div[1]/header/nav[1]/a[1]
Element /html/body/div[1]/header/nav[1]/a[1]/span
Element /html/body/div[1]/header/nav[1]/a[2]
Element /html/body/div[1]/header/nav[1]/a[2]/span[1]
Element /html/body/div[1]/header/nav[2]
Element /html/body/div[1]/header/nav[2]/ul
Element /html/body/div[1]/header/nav[2]/ul/li[1]/a
Element /html/body/div[1]/header/nav[2]/ul/li[2]
Element /html/body/div[1]/header/nav[2]/ul/li[2]/a
Element /html/body/div[1]/header/nav[2]/ul/li[3]/a
Element /html/body/div[1]/header/nav[2]/ul/li[3]/a/span
Element /html/body/div[1]/header/nav[2]/ul/li[4]/a
Element /html/body/div[1]/header/nav[2]/ul/li[4]/a/span
Element /html/body/div[2]/main/article/div/aside
Element /html/body/div[2]/main/article/div/div[1]/figure[1]
Element /html/body/div[2]/main/article/div/div[1]/figure[1]/a
Element /html/body/div[2]/main/article/div/div[1]/figure[1]/a/img
Element /html/body/div[2]/main/article/div/div[1]/figure[2]
Element /html/body/div[2]/main/article/div/div[1]/figure[2]/a
Element /html/body/div[2]/main/article/div/div[1]/figure[2]/a/img
Element /html/body/div[2]/main/article/div/div[1]/figure[3]
Element /html/body/div[2]/main/article/div/div[1]/figure[3]/a
Element /html/body/div[2]/main/article/div/div[1]/figure[3]/a/img
Element /html/body/div[2]/main/article/div/div[1]/figure[4]
Element /html/body/div[2]/main/article/div/div[1]/figure[4]/a
Element /html/body/div[2]/main/article/div/div[1]/figure[4]/a/img
Element /html/body/div[2]/main/article/div/div[2]/div[1]/figure
Element /html/body/div[2]/main/article/div/div[2]/div[2]/figure
Element /html/body/div[2]/main/article/div/div[2]/div[3]/a
Element /html/body/div[2]/main/article/div/div[2]/div[3]/a/span[1]
Element /html/body/div[2]/main/article/div/div[2]/div[3]/a/span[2]
Element /html/body/div[2]/main/article/div/div[2]/div[4]/figure
Element /html/body/div[2]/main/article/div/div[2]/div[5]/figure
Element /html/body/div[2]/main/article/div/div[2]/div[6]/figure
Element /html/body/div[2]/main/article/div/div[2]/div[7]/a
Element /html/body/div[2]/main/article/div/div[2]/div[7]/a/span[1]
Element /html/body/div[2]/main/article/div/div[2]/div[7]/a/span[2]
Element /html/body/div[2]/main/article/div/div[2]/div[8]/figure
Element /html/body/div[2]/main/article/div/div[2]/div[9]/a
Element /html/body/div[2]/main/article/div/div[2]/div[9]/a/span[1]
Element /html/body/div[2]/main/article/div/div[2]/div[9]/a/span[2]
Element /html/body/div[2]/main/article/header/div[1]
Element /html/body/div[2]/main/article/header/h1
Element /html/body/footer/div
Element /html/body/footer/nav
Element /html/body/footer/nav/ul
Element /html/body/footer/nav/ul/li[1]
Element /html/body/footer/nav/ul/li[1]/a
Element /html/body/footer/nav/ul/li[2]
Element /html/body/footer/nav/ul/li[2]/a
Element /html/body/footer/nav/ul/li[3]
Element /html/body/footer/nav/ul/li[3]/a
Element /html/body/footer/nav/ul/li[4]
Element /html/body/footer/ul
Element /html/body/footer/ul/li[1]
Element /html/body/footer/ul/li[1]/a
Element /html/body/footer/ul/li[1]/a/span[2]
Element /html/body/footer/ul/li[2]
Element /html/body/footer/ul/li[2]/a
Element /html/body/footer/ul/li[2]/a/span[2]
Element /html/body/footer/ul/li[3]
Element /html/body/footer/ul/li[3]/a
Element /html/body/footer/ul/li[3]/a/span[2]
Element /html/body/footer/ul/li[4]
Element /html/body/footer/ul/li[4]/a
Element /html/body/footer/ul/li[4]/a/span[2]
Element /html/body/footer/ul/li[5]
Element /html/body/footer/ul/li[5]/a
Element /html/body/footer/ul/li[5]/a/span[2]
Element /html/body/img[1]
Element /html/body/img[2]
Element /html/body/noscript[1]
Element /html/body/noscript[2]
Element /html/head/link[13]
Element /html/head/meta[2]
Element /html/head/meta[3]