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.
49
Images must have alternate text [1.1.1]
209
Certain ARIA roles must contain particular children [1.3.1]
209
Certain ARIA roles must be contained by particular parents [1.3.1]
10
<ul> and <ol> must only directly contain <li>, <script> or <template> elements [1.3.1]
112
<li> elements must be contained in a <ul> or <ol> [1.3.1]
1
All cells in a table element that use the headers attribute must only refer to other cells of that same table [1.3.1]
1
All th elements and elements with role=columnheader/rowheader must have data cells they describe [1.3.1]
1
ARIA hidden element must not contain focusable elements [1.3.1, 4.1.2]
1
Form elements must have labels [1.3.1, 4.1.2]
62
Inline text spacing must be adjustable with custom stylesheets [1.4.1.2, 2.1.a.a]
247
,
59
Elements must have sufficient color contrast [1.4.3]
1
Page must have means to bypass repeated blocks [2.4.1]
1
Frames must have title attribute [2.4.1, 4.1.2]
1
Documents must have <title> element to aid in navigation [2.4.2]
202
Links must have discernible text [2.4.4, 4.1.2]
149
,
4
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]
1
Form field should not have multiple label elements [3.3.2]
1
IDs used in ARIA and labels must be unique [4.1.1]
157
id attribute value must be unique [4.1.1]
4
Elements must only use allowed ARIA attributes [4.1.2]
2
aria-hidden='true' must not be present on the document body [4.1.2]
209
Required ARIA attributes must be provided [4.1.2]
209
ARIA roles used must conform to valid values [4.1.2]
4
ARIA attributes must conform to valid values [4.1.2]
4
ARIA attributes must conform to valid names [4.1.2]
5
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
(49 occurences)
Any of: 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
(209 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
(209 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
(10 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
(112 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: Info and Relationships)
Ensure that each cell in a table using the headers refers to another cell in that table
(1 occurrence)
All of: The headers attribute is exclusively used to refer to other cells in the table.
Checked Elements: td
Ensure that each cell in a table using the headers refers to another cell in that table
Understanding Success Criterion 1.3.1: Info and Relationships(Test for Success Criterion 1.3.1: Info and Relationships)
Ensure that each table header in a data table refers to data cells
(1 occurrence)
All of: All table header cells refer to data cells.
Checked Elements: th
Ensure that each table header in a data table refers to data cells
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
(1 occurrence)
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
(62 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
(59 occurences)
Any of: Unable to determine contrast ratio; 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's background color could not be determined because it's partially obscured by another element.
Code
<li style="white-space: nowrap; float: left; padding: 0px 7px; line-height: 49px; display: block;"><span class="ogolne">Ogólne</span> Brak powiadomień</li>
Code
<li style="white-space: nowrap; float: left; padding: 0px 7px; line-height: 49px; display: block;">
Code
<li style="white-space: nowrap; float: left; padding: 0px 7px; line-height: 49px; display: block;">
Code
<li style="white-space: nowrap; float: left; padding: 0px 7px; line-height: 49px; display: block;"><span class="stany-wod">Stany wód</span> Rzeka: Wisła, miejscowość: Zawichost poziom wody: 412</li>
Code
<li style="white-space: nowrap; float: left; padding: 0px 7px; line-height: 49px; display: block;"><span class="stany-wod">Stany wód</span> Rzeka: Wisła, miejscowość: Puławy poziom wody: 263</li>
Code
<li style="white-space: nowrap; float: left; padding: 0px 7px; line-height: 49px; display: block;"><span class="stany-wod">Stany wód</span> Rzeka: Wisła, miejscowość: Dęblin poziom wody: 247</li>
Code
<li style="white-space: nowrap; float: left; padding: 0px 7px; line-height: 49px; display: block;"><span class="stany-wod">Stany wód</span> Rzeka: Wieprz, miejscowość: Krasnystaw poziom wody: 411</li>
Code
<li style="white-space: nowrap; float: left; padding: 0px 7px; line-height: 49px; display: block;"><span class="stany-wod">Stany wód</span> Rzeka: Wieprz, miejscowość: Lubartów poziom wody: 286</li>
Code
<li style="white-space: nowrap; float: left; padding: 0px 7px; line-height: 49px; display: block;"><span class="stany-wod">Stany wód</span> Rzeka: Wieprz, miejscowość: Kośmin poziom wody: 278</li>
Code
<li style="white-space: nowrap; float: left; padding: 0px 7px; line-height: 49px; display: block;"><span class="stany-wod">Stany wód</span> Rzeka: Tyśmienica, miejscowość: Tchórzew poziom wody: 273</li>
Code
<li style="white-space: nowrap; float: left; padding: 0px 7px; line-height: 49px; display: block;"><span class="stany-wod">Stany wód</span> Rzeka: Bug, miejscowość: Kryłów poziom wody: 326</li>
Code
<li style="white-space: nowrap; float: left; padding: 0px 7px; line-height: 49px; display: block;"><span class="stany-wod">Stany wód</span> Rzeka: Bug, miejscowość: Włodawa poziom wody: 255</li>
Code
<li style="white-space: nowrap; float: left; padding: 0px 7px; line-height: 49px; display: block;"><span class="stany-wod">Stany wód</span> Rzeka: Bug, miejscowość: Krzyczew poziom wody: 363</li>
Code
<li style="white-space: nowrap; float: left; padding: 0px 7px; line-height: 49px; display: block;"><span class="stany-wod">Stany wód</span> Rzeka: Bug, miejscowość: Dorohusk poziom wody: 320</li>
Code
<li style="white-space: nowrap; float: left; padding: 0px 7px; line-height: 49px; display: block;"><span class="stany-wod">Stany wód</span> Rzeka: Bug, miejscowość: Strzyżów poziom wody: 562</li>
Code
<li class="last" style="white-space: nowrap; float: left; padding: 0px 7px; line-height: 49px; display: block;"><span class="stany-wod">Stany wód</span> Rzeka: Bug, miejscowość: Strzyżów poziom wody: 561</li>
Code
<span class="day">15</span>
Code
<span class="month">03</span>
Code
<span class="year">2023</span>
Code
<span class="year">13:08</span>
Code
<a href="https://milejow.pl/szkolenie-zasady-przyznawania-platnosci-w-ramach-ekoschematow/" rel="bookmark" role="link">Szkolenie: Zasady przyznawania płatności w ramach ekoschematów</a>
Code
<a href="https://milejow.pl/category/aktualnosci/" rel="category tag" role="link">Aktualności</a>
Code
<strong>
Code
<span class="year">09:02</span>
Code
<span class="day">07</span>
Code
<span class="month">09</span>
Code
<span class="year">2022</span>
Code
<strong>V Wojewódzka Wystawa Koni Ras Zimnokrwistych</strong>
Code
<span class="year">09:44</span>
Code
<span class="day">06</span>
Code
<span class="month">07</span>
Code
<span class="year">2022</span>
Code
<strong>Złote gody – rocznica niezwykła</strong>
Code
<span class="year">08:20</span>
Code
<span class="day">23</span>
Code
<span class="month">04</span>
Code
<span class="year">2021</span>
Code
<strong>„Tu rodziła się Solidarność Rolników” – wystawa IPN</strong>
Code
<strong>STA „Nad Wieprzem”</strong>
Code
<strong>Wirtualne Powiaty</strong>
Code
<strong>STA „Nad Wieprzem”</strong>
Code
<strong>LGD "Dolina Giełczwi"</strong>
Code
<strong>CEIDG</strong>
Code
<strong>IMGW-PIB</strong>
Code
<strong>Rządowe Centrum Bezpieczeństwa</strong>
Code
<strong>Forum Kobiet Gminy Milejów</strong>
Code
<strong class="heading">Dane kontaktowe</strong>
Code
<p><strong>Adres:</strong> ul. Partyzancka 13a, 21-020 Milejów</p>
Code
<strong>Adres:</strong>
Code
<strong>Telefon:</strong>
Code
<a href="tel:814787610" role="link">814787610</a>
Code
<strong>E-mail:</strong>
Code
<a href="mailto:sekretariat@milejow.pl" role="link">sekretariat@milejow.pl</a>
Code
<a href="http://milejow.pl/?page_id=131" role="link">Załatwianie spraw w urzędzie</a>
Code
<a href="https://mapa.inspire-hub.pl/#/gmina_milejow" role="link">Miejscowy Plan Zagospodarowania Przestrzennego</a>
Code
<a href="https://milejow.ezamawiajacy.pl/servlet/HomeServlet" role="link">Zamówienia Publiczne</a>
Code
<a href="https://ugmilejow.bip.lubelskie.pl/index.php?id=6" role="link">Biuletyn Informacji Publicznej</a>
Code
<a href="https://epuap.gov.pl/wps/portal/strefa-klienta/katalog-spraw/profil-urzedu/3470nkowc6" role="link">Elektroniczna skrzynka podawcza EPUAP</a>
Code
<a href="https://edziennik.lublin.uw.gov.pl/" role="link">Dziennik Urzędowy Województwa Lubelskiego</a>
Ensures the contrast between foreground and background colors meets WCAG 2 AA contrast ratio thresholds
(247 occurences)
Any of: Element has sufficient color contrast of 15.29; Element has sufficient color contrast of 7.2; Element has sufficient color contrast of 8.41; Element has sufficient color contrast of 9.73; Element has sufficient color contrast of 11.17; Element has sufficient color contrast of 6.6; Element has sufficient color contrast of 21; Element has sufficient color contrast of 7.45; Element has sufficient color contrast of 7.39; Element has sufficient color contrast of 5.48; Element has sufficient color contrast of 12.63; Element has sufficient color contrast of 15.42; Element has sufficient color contrast of 7.08; Element has sufficient color contrast of 7.86; Element has sufficient color contrast of 5.42; Element has sufficient color contrast of 14.65.
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.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 landmark region; 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.1, 4.1.2: Bypass Blocks)
Ensures <iframe> and <frame> elements contain a non-empty title attribute
(1 occurrence)
Any of: Element has a title attribute.
Checked Elements: iframe,frame
Ensures <iframe> and <frame> elements contain a non-empty title attribute
Understanding Success Criterion 2.4.1, 4.1.2: 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
(202 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
(4 occurences)
All of: Check that links have the same purpose, or are intentionally ambiguous..
Code
<a href="https://milejow.pl/szkolenie-zasady-przyznawania-platnosci-w-ramach-ekoschematow/" rel="bookmark" role="link">Szkolenie: Zasady przyznawania płatności w ramach ekoschematów</a>
Code
<a href="https://milejow.pl/zalatwianie-spraw-w-urzedzie/" role="link">Załatwianie spraw w urzędzie</a>
Code
<a href="https://milejow.pl/informacja-w-z-l-z-s-w-lublinie/" rel="bookmark" role="link">Informacja W.Z.L.Z.S. w Lublinie</a>
Code
<a href="https://milejow.pl/obwieszczenie-o-przystapieniu-do-sporzadzania-zmiany-w-czesci-tekstowej-miejscowego-planu-zagospodarowania-przestrzennego-gminy-milejow/" rel="bookmark" role="link">
Ensure that links with the same accessible name serve a similar purpose
(149 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
(1 occurrence)
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 used in ARIA and in labels is unique
(1 occurrence)
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
(157 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
(4 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.
(2 occurences)
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
(209 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
(209 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
(4 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
(4 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
(5 occurences)
Any of: Element's default semantics were overriden with role="presentation"; Element has inner text that is visible to screen readers; Element has a title attribute.
Checked Elements: button
Ensures buttons have discernible text
Understanding Success Criterion 4.1.2: Name, Role, Value