Accessibility digest

Contents

Synopsis
PageLaird Hamblin;Unaffiliated;Utah
URLhttps://lairdsenate.us/
Test date2024/09/22
Score2797
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-26.json

Introduction

How accessible is the Laird Hamblin;Unaffiliated;Utah web page at https://lairdsenate.us/?

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 2797, the sum of 400 for the count of issues, 1333 for specific issues, 0 for unclassified rule violations, 338 for tool-by-tool ratings, 150 for the count of violating elements, 300 for the page preventing tools from running, 276 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
color missing1.4.34200qualWeb:50
contrast poor1.4.34188alfa:47, axe:47, htmlcs:1, ibm:47, qualWeb:47, wave:47, aslint:0, wax:0
attribute value invalid1.3.14180nuVal:45, ibm:0, wax:0
focus indication poor2.4.74160testaro:40, alfa:0, aslint:0
not exactly 1 h1 heading1.3.12124nuVal:2, aslint:0, axe:0, wave:0
overflow hidden?1.4.4175qualWeb:75
text contrast improvable1.4.6148alfa:48, aslint:48, axe:1, htmlcs:47, qualWeb:48, wax:0
target small2.5.5147alfa:47, testaro:3
all-capital text3.1.5146alfa:1, aslint:46, testaro:34, ed11y:0
line height low1.4.8242alfa:21, testaro:6
type redundant1.3.1132nuVal:32
title attribute invalid1.3.1432testaro:8
void element has trailing slash4.1130nuVal:30
attribute obsolete4.1318aslint:3, nuVal:6, htmlcs:0, ibm:0, testaro:0, wave:0
figure not named1.1.1416ibm:4
code obsolete4.1312ibm:4, nuVal:0
font size absolute1.4.4210alfa:5, qualWeb:4
CSS bans page rotation1.3.448aslint:2, qualWeb:0
parent invalid1.3.148nuVal:2, ibm:0
navigations not distinctly named1.3.636ibm:2
tab-opening link action unstated3.2.535ed11y:3
svg image not named1.1.144aslint:1, alfa:0, axe:0, ibm:0, qualWeb:0, wax:0
role redundant4.1.214ibm:2, nuVal:4
link indication poor1.3.324testaro:2, alfa:0, axe:0
tab-opening link action unstated?3.2.513aslint:3, htmlcs:3, testaro:3
landmarks not distinctly named1.3.633axe:1, ibm:0, wax:0
heading-like styles dubious1.3.113htmlcs:3, wave:2, axe:0, ed11y:0
text contrast not testable1.4.313htmlcs:3, alfa:0, aslint:0
element beyond display when focused1.4.1033testaro:1
audio or video alternatives missing?1.2.213wave:3
image dubiously marked decorative1.1.112htmlcs:2
nav links not list1.3.122htmlcs:1
section heading missing1.3.112nuVal:2
image link text suspect2.4.412qualWeb:2
image dubiously named1.1.112qualWeb:2, aslint:0, wave:0
role assigned instead of implicit4.1.212testaro:2
item makes testing inconclusive4.111alfa:1
content beyond landmarks1.3.611ibm:1, alfa:0, axe:0, wax:0
inconsistent heading, link, or button styles3.2.411testaro:1
z-index not zero1.411testaro:1

Itemized issues

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

Issue: color missing

Impact: Content is impossible to perceive under some conditions

WCAG: 1.4.3

Score: 200

Elements

None identified

Violations of qualWeb rules

Rule QW-WCAG-T31

Description: Foreground or background color is specified but not both

Count of instances: 50

Issue: contrast poor

Impact: Content is difficult to understand

WCAG: 1.4.3

Score: 188

Elements

None identified

Violations of alfa rules

Rule r69

Description: Text outside widget has subminimum contrast

Count of instances: 47

Violations of axe rules

Rule color-contrast

Description: Element has insufficient color contrast

Count of instances: 47

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

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

Violations of qualWeb rules

Rule QW-ACT-R37

Description: Text has less than the minimum contrast

Count of instances: 47

Violations of wave rules

Rule contrast

Description: Very low contrast

Count of instances: 47

Issue: attribute value invalid

Impact: Item behaves improperly

WCAG: 1.3.1

Score: 180

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

Issue: focus indication poor

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

WCAG: 2.4.7

Score: 160

Elements

Violations of testaro rules

Rule focInd

Description: Focused element displays a nonstandard or no focus indicator

Count of instances: 40

Issue: not exactly 1 h1 heading

Impact: User cannot understand the topic of the document

WCAG: 1.3.1

Score: 124

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

Issue: overflow hidden?

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

WCAG: 1.4.4

Score: 75

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

Issue: text contrast improvable

Impact: Content is not easy to understand

WCAG: 1.4.6

Score: 48

Elements

None identified

Violations of alfa rules

Rule r66

Description: Text contrast less than AAA requires

Count of instances: 48

Violations of aslint rules

Rule color_contrast_aaa7

Description: Text has contrast less than 7:1

Count of instances: 47

Rule color_contrast_aaa4

Description: Text has contrast less than 4.5:1

Count of instances: 1

Violations of axe rules

Rule color-contrast-enhanced

Description: Element has insufficient color contrast (Level AAA)

Count of instances: 1

Violations of htmlcs rules

Rule AAA.1_4_6.G17.Fail

Description: Text has insufficient contrast

Count of instances: 47

Violations of qualWeb rules

Rule QW-ACT-R76

Description: Text has less than the enhanced minimum contrast

Count of instances: 48

Issue: target small

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

WCAG: 2.5.5

Score: 47

Elements

Violations of alfa rules

Rule r111

Description: Target size is suboptimal

Count of instances: 47

Violations of testaro rules

Rule targetSize

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

Count of instances: 3

Issue: all-capital text

Impact: Text is difficult to read

WCAG: 3.1.5

Score: 46

Elements

Violations of alfa rules

Rule r72

Description: Paragraph text is uppercased

Count of instances: 1

Violations of aslint rules

Rule capital_letters_words

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

Count of instances: 46

Violations of testaro rules

Rule allCaps

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

Count of instances: 34

Issue: line height low

Impact: Text is difficult to read

WCAG: 1.4.8

Score: 42

Elements

Violations of alfa rules

Rule r73

Description: Text line height is not at least 1.5

Count of instances: 21

Violations of testaro rules

Rule lineHeight

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

Count of instances: 6

Issue: type redundant

Impact: Document includes unnecessary code

WCAG: 1.3.1

Score: 32

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

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

Issue: title attribute invalid

Impact: User cannot hover to get help explaining an item

WCAG: 1.3.1

Score: 32

Elements

Violations of testaro rules

Rule titledEl

Description: title attribute belongs to an inappropriate element

Count of instances: 8

Issue: void element has trailing slash

Impact: Document contains invalid code

WCAG: 4.1

Score: 30

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

Issue: attribute obsolete

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

WCAG: 4.1

Score: 18

Elements

None identified

Violations of aslint rules

Rule obsolete_html_attributes

Description: Element has an obsolete attribute

Count of instances: 3

Violations of nuVal rules

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

Description: Attribute is obsolete on its element

Count of instances: 6

Issue: figure not named

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

WCAG: 1.1.1

Score: 16

Elements

None identified

Violations of ibm rules

Rule figure_label_exists

Description: figure element has no associated label

Count of instances: 4

Issue: code obsolete

Impact: Document contains code that is no longer standard

WCAG: 4.1

Score: 12

Elements

None identified

Violations of ibm rules

Rule element_attribute_deprecated

Description: Element or attribute is obsolete

Count of instances: 4

Issue: font size absolute

Impact: User cannot adjust the text size for readability

WCAG: 1.4.4

Score: 10

Elements

None identified

Violations of alfa rules

Rule r74

Description: Paragraph text has an absolute font size

Count of instances: 5

Violations of qualWeb rules

Rule QW-WCAG-T28

Description: Font size set to an absolute unit value

Count of instances: 4

Issue: CSS bans page rotation

Impact: User must read sideways after rotating a device

WCAG: 1.3.4

Score: 8

Elements

None identified

Violations of aslint rules

Rule orientation

Description: CSS media query specifies an orientation

Count of instances: 2

Issue: parent invalid

Impact: User cannot properly operate an item

WCAG: 1.3.1

Score: 8

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

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: tab-opening link action unstated

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

WCAG: 3.2.5

Score: 5

Elements

Violations of ed11y rules

Rule linkNewWindow

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

Count of instances: 3

Issue: svg image not named

Impact: User cannot get help understanding an image

WCAG: 1.1.1

Score: 4

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

Impact: User cannot differentiate a link from plain text

WCAG: 1.3.3

Score: 4

Elements

Violations of testaro rules

Rule linkUl

Description: Inline links are not underlined

Count of instances: 2

Issue: tab-opening link action unstated?

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

WCAG: 3.2.5

Score: 3

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

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

Violations of testaro rules

Rule linkExt

Description: Link opens a new window or tab

Count of instances: 3

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

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

Violations of wave rules

Rule heading_possible

Description: Possible heading

Count of instances: 2

Issue: text contrast not testable

Impact: Text may be difficult to read

WCAG: 1.4.3

Score: 3

Elements

None identified

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

Issue: element beyond display when focused

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

WCAG: 1.4.10

Score: 3

Elements

Violations of testaro rules

Rule focVis

Description: Element when focused is off the display

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

Elements

None identified

Violations of wave rules

Rule youtube_video

Description: YouTube video may have no or incorrect captions

Count of instances: 3

Issue: image dubiously marked decorative

Impact: Helper ignores an image that is apparently informative

WCAG: 1.1.1

Score: 2

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

Issue: nav links not list

Impact: User cannot get help recognizing a list of navigation links

WCAG: 1.3.1

Score: 2

Elements

None identified

Violations of htmlcs rules

Rule AAA.1_3_1.H48

Description: Navigation links are not coded as a list

Count of instances: 1

Issue: section heading missing

Impact: User cannot understand the topic of a part of the document

WCAG: 1.3.1

Score: 2

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

Issue: image link text suspect

Impact: Keyboard-only user may misunderstand the effect of following a link

WCAG: 2.4.4

Score: 2

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

Issue: image dubiously named

Impact: Helper may describe an image inadequately

WCAG: 1.1.1

Score: 2

Elements

None identified

Violations of qualWeb rules

Rule QW-WCAG-T8

Description: Text alternative is suspect

Count of instances: 2

Issue: role assigned instead of implicit

Impact: User may misunderstand the purpose of an item

WCAG: 4.1.2

Score: 2

Elements

Violations of testaro rules

Rule role

Description: Explicitly assigned ARIA role is also an implicit element role

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

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

WCAG: 1.3.6

Score: 1

Elements

None identified

Violations of ibm rules

Rule aria_content_in_landmark

Description: Content is not within a landmark element

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

Elements

None identified

Violations of testaro rules

Rule styleDiff

Description: Heading, link, and button style inconsistencies

Count of instances: 1

Issue: z-index not zero

Impact: User cannot predict the effect of clicking

WCAG: 1.4

Score: 1

Elements

Violations of testaro rules

Rule zIndex

Description: Element has a nondefault z-index value

Count of instances: 1

Elements with issues

Elements exhibiting issues:

Element /html/body/a
Element /html/body/div/div/header/button
Element /html/body/div/div/header/div[1]/div
Element /html/body/div/div/header/div[1]/div/nav/ul/li[10]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[11]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[13]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[14]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[15]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[16]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[17]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[18]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[19]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[1]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[20]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[21]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[22]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[23]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[24]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[25]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[26]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[27]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[28]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[29]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[2]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[30]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[31]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[32]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[33]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[34]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[35]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[36]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[37]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[38]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[39]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[3]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[40]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[41]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[42]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[43]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[44]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[4]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[5]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[6]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[7]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[8]/a
Element /html/body/div/div/header/div[1]/div/nav/ul/li[9]/a
Element /html/body/div/div/header/div[2]/div
Element /html/body/div/div/header/div[2]/div/a
Element /html/body/div/div/section
Element /html/body/div/div/section/div/div/article/div[1]/div/iframe
Element /html/body/div/div/section/div/div/article/div[3]
Element /html/body/div/div/section/div/div/article/div[3]/div[3]/div/a
Element /html/body/div/div/section/div/div/article/div[3]/div[4]/a[1]
Element /html/body/div/div/section/div/div/article/div[3]/div[4]/a[1]/img
Element /html/body/div/div/section/div/div/article/div[3]/div[4]/a[2]
Element /html/body/div/div/section/div/div/article/div[3]/div[4]/a[2]/img
Element /html/body/div/div/section/div/div/article/div[3]/p[2]
Element /html/body/div/div/section/div/div/article/div[3]/p[2]/strong
Element /html/body/div/div/section/div/div/article/div[3]/p[3]
Element /html/head/link[16]
Element /html/head/link[17]
Element /html/head/link[20]
Element /html/head/link[21]
Element /html/head/link[4]
Element /html/head/link[5]