Please note that the automatic score is based on tests carried out automatically. About 20% of the conceivable tests can be automated, and the tool covers a part of these tests. The score from user tests are based on a limited set of questions and will also not cover all possible tests. Therefore, the evaluated pages may contain barriers not reported by any of the tools. For reference see the list of. currently implemented tests. Full disclaimer.
Fail, Verify and Pass results are not displayed.
21
Images must have alternate text [1.1.1]
40
Certain ARIA roles must contain particular children [1.3.1]
40
Certain ARIA roles must be contained by particular parents [1.3.1]
8
<ul> and <ol> must only directly contain <li>, <script> or <template> elements [1.3.1]
21
<li> elements must be contained in a <ul> or <ol> [1.3.1]
1
ARIA hidden element must not contain focusable elements [1.3.1, 4.1.2]
5
Form elements must have labels [1.3.1, 4.1.2]
37
Inline text spacing must be adjustable with custom stylesheets [1.4.1.2, 2.1.a.a]
33
,
1
,
35
Elements must have sufficient color contrast [1.4.3]
1
Ensure that scrollable region has keyboard access [2.1.1]
1
Page must have means to bypass repeated blocks [2.4.1]
1
Documents must have <title> element to aid in navigation [2.4.2]
27
Links must have discernible text [2.4.4, 4.1.2]
21
,
3
Links with the same name have a similar purpose [2.4.9]
1
<html> element must have a lang attribute [3.1.1]
1
<html> element must have a valid value for the lang attribute [3.1.1]
5
Form field should not have multiple label elements [3.3.2]
4
IDs of active elements must be unique [4.1.1]
7
IDs used in ARIA and labels must be unique [4.1.1]
73
id attribute value must be unique [4.1.1]
19
Elements must only use allowed ARIA attributes [4.1.2]
1
aria-hidden='true' must not be present on the document body [4.1.2]
40
Required ARIA attributes must be provided [4.1.2]
40
ARIA roles used must conform to valid values [4.1.2]
19
ARIA attributes must conform to valid values [4.1.2]
19
ARIA attributes must conform to valid names [4.1.2]
18
Buttons must have discernible text [4.1.2]
Select a test to display the details
(Test for Success Criterion 1.1.1: Non-text Content:)
Ensures <img> elements have alternate text or a role of none or presentation
(21 occurences)
Any of: Element's default semantics were overriden with role="presentation"; Element has an alt attribute. None of: Element has a valid alt attribute value.
Checked Elements: img
Ensures <img> elements have alternate text or a role of none or presentation
Understanding Success Criterion 1.1.1: Non-text Content:(Test for Success Criterion 1.3.1: Info and Relationships)
Ensures elements with an ARIA role that require child roles contain them
(40 occurences)
Any of: Required ARIA children are present.
Checked Elements: all
Ensures elements with an ARIA role that require child roles contain them
Understanding Success Criterion 1.3.1: Info and Relationships(Test for Success Criterion 1.3.1: Info and Relationships)
Ensures elements with an ARIA role that require parent roles are contained by them
(40 occurences)
Any of: Required ARIA parent role present.
Checked Elements: all
Ensures elements with an ARIA role that require parent roles are contained by them
Understanding Success Criterion 1.3.1: Info and Relationships(Test for Success Criterion 1.3.1: Info and Relationships)
Ensures that lists are structured correctly
(8 occurences)
None of: List element only has direct children that are allowed inside <li> elements.
Checked Elements: all
Ensures that lists are structured correctly
Understanding Success Criterion 1.3.1: Info and Relationships(Test for Success Criterion 1.3.1: Info and Relationships)
Ensures <li> elements are used semantically
(21 occurences)
Any of: List item has a <ul>, <ol> or role="list" parent element.
Checked Elements: li
Ensures <li> elements are used semantically
Understanding Success Criterion 1.3.1: Info and Relationships(Test for Success Criterion 1.3.1, 4.1.2)
Ensures aria-hidden elements do not contain focusable elements
(1 occurrence)
All of: No focusable elements while a modal is open; No focusable elements contained within element.
Checked Elements:
In development. This information will be added shortly
Understanding Success Criterion 1.3.1, 4.1.2: None(Test for Success Criterion 1.3.1, 4.1.2: Info and Relationships)
Ensures every form element has a label
(5 occurences)
Any of: Form element has an explicit <label>. None of: Form element has a visible explicit <label>.
Checked Elements: all
Ensures every form element has a label
Understanding Success Criterion 1.3.1, 4.1.2: Info and Relationships(Test for Success Criterion 1.4.1.2, 2.1.a.a)
Ensure that text spacing set through style attributes can be adjusted with custom stylesheets
(37 occurences)
All of: No inline styles with '!important' that affect text spacing has been specified.
Checked Elements:
In development. This information will be added shortly
Understanding Success Criterion 1.4.1.2, 2.1.a.a: None(Test for Success Criterion 1.4.3: Contrast (Minimum))
Ensures the contrast between foreground and background colors meets WCAG 2 AA contrast ratio thresholds
(1 occurrence)
Any of: Element has insufficient color contrast of 3.23 (foreground color: #ffffff, background color: #e96656, font size: 10.5pt (14px), font weight: normal). Expected contrast ratio of 4.5:1.
Code
<button type="submit" name="wpforms[submit]" class="wpforms-submit " id="wpforms-submit-1469" value="wpforms-submit" aria-live="assertive" data-alt-text="Wysyłanie" data-submit-text="Wyślij">Wyślij</button>
Ensures the contrast between foreground and background colors meets WCAG 2 AA contrast ratio thresholds
(35 occurences)
Any of: Element's background color could not be determined because element contains an image node; Element's background color could not be determined due to a background image; Element has a 1:1 contrast ratio with the background; Element's background color could not be determined because it is overlapped by another element; Element's background color could not be determined because it's partially obscured by another element.
Code
<a href="https://accessibility-helper.co.il/" target="_blank" title="Accessibility by WP Accessibility Helper Team" data-wahfont="12" role="link">Accessibility by WAH</a>
Code
<h1 class="intro-text" data-wahfont="55">ZESPÓŁ PRZEDSZKOLI NR 1 W POZNANIU</h1>
Code
<a href="http://zp1poznan.pl/przedszkole-nr-16/" class="btn btn-primary custom-button red-btn" data-wahfont="14" role="link"><img src="http://zp1poznan.pl/wp-content/uploads/2019/08/logo-p16.png" alt="Przedszkole nr 16 - logo"><br>Przedszkole nr 16</a>
Code
<a href="http://zp1poznan.pl/przedszkole-nr-141/" class="btn btn-primary custom-button green-btn" data-wahfont="14" role="link"><img src="http://zp1poznan.pl/wp-content/uploads/2019/08/Przechwytywanie.png" alt="Przedszkole nr 141 - logo"><br>Przedszkole nr 141</a>
Code
<h3 class="red-border-bottom" data-wahfont="17">
INFORMACJE DLA RODZICÓW </h3>
Code
<p data-wahfont="14">Informacje dla rodziców</p>
Code
<h3 class="red-border-bottom" data-wahfont="17">
Przedszkole nr 16 </h3>
Code
<p data-wahfont="14">Przedszkole nr 16</p>
Code
<h3 class="red-border-bottom" data-wahfont="17">
Przedszkole nr 141 </h3>
Code
<p data-wahfont="14">Przedszkole nr 141</p>
Code
<h3 class="red-border-bottom" data-wahfont="17">
O nas </h3>
Code
<p data-wahfont="14">O nas</p>
Code
<div class="big-intro" data-scrollreveal="enter left after 0s over 1s" style="-webkit-transform: translatex(-60px);-moz-transform: translatex(-60px);-ms-transform: translatex(-60px);transform: translatex(-60px);opacity: 0;" data-sr-init="true">ZESPÓŁ PRZEDSZKOLI NR 1 W POZNANIU</div>
Code
<p data-wahfont="14">
Code
<span id="przedszkola" data-wahfont="17">2</span>
Code
<label>Przedszkola</label>
Code
<span id="opiekunow" data-wahfont="17">14</span>
Code
<label>OPIEKUNÓW</label>
Code
<span id="dzieci-pod-opieka" data-wahfont="17">188</span>
Code
<label>DZIECI POD OPIEKĄ</label>
Code
<span id="procent-zadowolenia" data-wahfont="17">100</span>
Code
<label>PROCENT ZADOWOLENIA</label>
Code
<label class="wpforms-field-label" for="wpforms-1469-field_1">Imię <span class="wpforms-required-label" data-wahfont="16">*</span></label>
Code
<input type="text" id="wpforms-1469-field_1" class="wpforms-field-medium wpforms-field-required" name="wpforms[fields][1]" required="">
Code
<label class="wpforms-field-label" for="wpforms-1469-field_2">E-mail <span class="wpforms-required-label" data-wahfont="16">*</span></label>
Code
<input type="text" id="wpforms-1469-field_2" class="wpforms-field-medium wpforms-field-required" name="wpforms[fields][2]" required="">
Code
<label class="wpforms-field-label" for="wpforms-1469-field_3">Temat <span class="wpforms-required-label" data-wahfont="16">*</span></label>
Code
<input type="text" id="wpforms-1469-field_3" class="wpforms-field-medium wpforms-field-required" name="wpforms[fields][3]" required="">
Code
<label class="wpforms-field-label" for="wpforms-1469-field_6">Treść <span class="wpforms-required-label" data-wahfont="16">*</span></label>
Code
<input type="text" id="wpforms-1469-field_6" class="wpforms-field-medium wpforms-field-required" name="wpforms[fields][6]" placeholder="Tutaj napisz wiadomość..." required="">
Code
<label class="wpforms-field-label" for="wpforms-1469-field_7">Zgoda <span class="wpforms-required-label" data-wahfont="16">*</span></label>
Code
<label class="wpforms-field-label-inline" for="wpforms-1469-field_7_1">Wyrażam zgodę na odpowiedź na mój adres mailowy</label>
Code
<div class="leaflet-control-attribution leaflet-control"><a href="http://leafletjs.com" title="A JS library for interactive maps" data-wahfont="11" role="link">Leaflet</a>, \r\n© <a href="http://www.openstreetmap.org/copyright" data-wahfont="11" role="link">OpenStreetMap</a> contributors</div>
Code
<a href="http://leafletjs.com" title="A JS library for interactive maps" data-wahfont="11" role="link">Leaflet</a>
Code
<a href="http://www.openstreetmap.org/copyright" data-wahfont="11" role="link">OpenStreetMap</a>
Ensures the contrast between foreground and background colors meets WCAG 2 AA contrast ratio thresholds
(33 occurences)
Any of: Element has sufficient color contrast of 4.86; Element has sufficient color contrast of ${data.contrastRatio}; Element has sufficient color contrast of 21; Element has sufficient color contrast of 10.36; Element has sufficient color contrast of 15.71; Element has sufficient color contrast of 14.93; Element has sufficient color contrast of 7.03.
Checked Elements: all
Ensures the contrast between foreground and background colors meets WCAG 2 AA contrast ratio thresholds
Understanding Success Criterion 1.4.3: Contrast (Minimum)(Test for Success Criterion 2.1.1)
Elements that have scrollable content should be accessible by keyboard
(1 occurrence)
Any of: Element contains focusable elements.
Checked Elements:
In development. This information will be added shortly
Understanding Success Criterion 2.1.1: None(Test for Success Criterion 2.4.1: Bypass Blocks)
Ensures each page has at least one mechanism for a user to bypass navigation and jump straight to the content
(1 occurrence)
Any of: Page has a heading; Valid skip link found.
Checked Elements: all
Ensures each page has at least one mechanism for a user to bypass navigation and jump straight to the content
Understanding Success Criterion 2.4.1: Bypass Blocks(Test for Success Criterion 2.4.2: Page Titled)
Ensures each HTML document contains a non-empty <title> element
(1 occurrence)
Any of: Document has a non-empty <title> element.
Checked Elements: title
Ensures each HTML document contains a non-empty <title> element
Understanding Success Criterion 2.4.2: Page Titled(Test for Success Criterion 2.4.4, 4.1.2: Name, Role, Value)
Ensures links have discernible text
(27 occurences)
Any of: Element has text that is visible to screen readers. None of: Element is not in tab order or has accessible text.
Checked Elements: all
Ensures links have discernible text
Understanding Success Criterion 2.4.4, 4.1.2: Name, Role, Value(Test for Success Criterion 2.4.9)
Ensure that links with the same accessible name serve a similar purpose
(3 occurences)
All of: Check that links have the same purpose, or are intentionally ambiguous..
Code
<a href="http://zp1poznan.pl/przedszkole-nr-16/" data-wahfont="16" role="link">Przedszkole nr 16</a>
Code
<a href="http://zp1poznan.pl/przedszkole-nr-16/kronika-2019-2020/" data-wahfont="16" role="link">Kronika</a>
Code
<a href="http://zp1poznan.pl/przedszkole-nr-141/" data-wahfont="16" role="link">Przedszkole nr 141</a>
Ensure that links with the same accessible name serve a similar purpose
(21 occurences)
All of: There are no other links with the same name, that go to a different URL.
Checked Elements:
In development. This information will be added shortly
Understanding Success Criterion 2.4.9: None(Test for Success Criterion 3.1.1: Language of Page)
Ensures every HTML document has a lang attribute
(1 occurrence)
Any of: The <html> element has a lang attribute.
Checked Elements: html
Ensures every HTML document has a lang attribute
Understanding Success Criterion 3.1.1: Language of Page(Test for Success Criterion 3.1.1: Language of Page)
Ensures the lang attribute of the <html> element has a valid value
(1 occurrence)
None of: Value of lang attribute is included in the list of valid languages.
Checked Elements: html
Ensures the lang attribute of the <html> element has a valid value
Understanding Success Criterion 3.1.1: Language of Page(Test for Success Criterion 3.3.2)
Ensures form field does not have multiple label elements
(5 occurences)
None of: Form field does not have multiple label elements.
Checked Elements:
In development. This information will be added shortly
Understanding Success Criterion 3.3.2: None(Test for Success Criterion 4.1.1: Parsing)
Ensures every id attribute value of active elements is unique
(4 occurences)
Any of: Document has no active elements that share the same id attribute.
Checked Elements: all
Ensures every id attribute value of active elements is unique
Understanding Success Criterion 4.1.1: Parsing(Test for Success Criterion 4.1.1: Parsing)
Ensures every id attribute value used in ARIA and in labels is unique
(7 occurences)
Any of: Document has no elements referenced with ARIA or labels that share the same id attribute.
Checked Elements: all
Ensures every id attribute value used in ARIA and in labels is unique
Understanding Success Criterion 4.1.1: Parsing(Test for Success Criterion 4.1.1: Parsing)
Ensures every id attribute value is unique
(73 occurences)
Any of: Document has no static elements that share the same id attribute.
Checked Elements: all
Ensures every id attribute value is unique
Understanding Success Criterion 4.1.1: Parsing(Test for Success Criterion 4.1.2: Name, Role, Value)
Ensures ARIA attributes are allowed for an element's role
(19 occurences)
Any of: ARIA attributes are used correctly for the defined role. None of: ARIA attribute is supported.
Checked Elements: all
Ensures ARIA attributes are allowed for an element's role
Understanding Success Criterion 4.1.2: Name, Role, Value(Test for Success Criterion 4.1.2: Name, Role, Value)
Ensures aria-hidden='true' is not present on the document body.
(1 occurrence)
Any of: No aria-hidden attribute is present on document body.
Checked Elements: body
Ensures aria-hidden='true' is not present on the document body.
Understanding Success Criterion 4.1.2: Name, Role, Value(Test for Success Criterion 4.1.2: Parsing)
Ensures elements with ARIA roles have all required ARIA attributes
(40 occurences)
Any of: All required ARIA attributes are present.
Checked Elements: all
Ensures elements with ARIA roles have all required ARIA attributes
Understanding Success Criterion 4.1.2: Parsing(Test for Success Criterion 4.1.2: Info and Relationships)
Ensures all elements with a role attribute use a valid value
(40 occurences)
None of: Only one role value used; ARIA role is supported; Abstract roles are not used; ARIA role is valid.
Checked Elements: all
Ensures all elements with a role attribute use a valid value
Understanding Success Criterion 4.1.2: Info and Relationships(Test for Success Criterion 4.1.2: Info and Relationships)
Ensures all ARIA attributes have valid values
(19 occurences)
All of: ARIA attribute values are valid; Uses a supported aria-errormessage technique.
Checked Elements: all
Ensures all ARIA attributes have valid values
Understanding Success Criterion 4.1.2: Info and Relationships(Test for Success Criterion 4.1.2: Parsing)
Ensures attributes that begin with aria- are valid ARIA attributes
(19 occurences)
Any of: ARIA attribute name is valid.
Checked Elements: all
Ensures attributes that begin with aria- are valid ARIA attributes
Understanding Success Criterion 4.1.2: Parsing(Test for Success Criterion 4.1.2: Name, Role, Value)
Ensures buttons have discernible text
(18 occurences)
Any of: Element has inner text that is visible to screen readers; Element has a title attribute; aria-label attribute exists and is not empty.
Checked Elements: button
Ensures buttons have discernible text
Understanding Success Criterion 4.1.2: Name, Role, Value