[Skip navigation links]

Site Report

This tab shows accessibility issues, indicating problems for older users, people with disabilities or accessibility needs. Automated testing cannot detect all accessibility issues, so should be used alongside human testing.

Level	WCAG 2.1	Section 508 - 2017	Key
A			Pages with level A issues are unusable for some people
AA			Pages with level AA issues are very difficult to use
AAA			Pages with level AAA issues can be difficult to use

Priority	Description and URL	Guideline and Line#	Count
Level A 4 issues on 1 pages
	All `fieldset` elements should be labeled with `legend` elements.	WCAG 2.1 A H71 Section 508 (2017) A H71	1 pages
	The first child element inside a `fieldset` must be a `legend` element, which provides a label or description for the group. `legend` elements in other positions may be ignored.
	https://geocams.pl/	Line 87
	Duplicate `id` - the same ID is used on more than one element.	HTML5 WCAG 2.1 A 4.1.1 Section 508 (2017) A 4.1.1	1 pages

	`id=gmap` `id=gmap` https://geocams.pl/	Line 121 150
	Each `a` element must contain text or an `img` with an `alt` attribute.	WCAG 2.1 A F89 Section 508 (2017) A F89	1 pages
	A link name allows screen readers to voice what the links does. If there is no link text / `alt` text, or the text / image is hidden by CSS, screen readers have nothing to read, so read out the URL instead. To add a name do one of the following: Add text between the `a` element start and end tags Add an `aria-label` attribute Add an `aria-labelledby` attribute Add an `img alt` attribute if the link contains an `img` element
	https://geocams.pl/	Line 82 91
	`img` elements must have an accessible name.	WCAG 2.1 A F65 Section 508 (2017) A F65	1 pages
	Add an `alt` attribute describing the image, which screen readers voice instead of the image. Spacer images and purely decorative images should use `alt=""`. Do not use `alt` text containing only spaces since that's voiced as an unlabeled image. Impact on users: NVDA 2019.2 Chrome 79 Windows 10 Reading: Image unlabeled. NVDA 2019.2 FF68 Windows 10 Reading: Image ignored. NVDA 2019.2 IE11 Windows 10 Reading: Image ignored. NVDA 2018.4 Chrome 73 Windows 10 Reading: Image ignored. NVDA 2018.4 FF60 Windows 10 Reading: Image ignored. NVDA 2018.4 IE11 Windows 10 Reading: Image ignored. JAWS 2019.1912.1 Chrome 79 Windows 10 Reading: Image unlabeled. JAWS 2019.1912.1 FF68 Windows 10 Reading: Image ignored. JAWS 2019.1912.1 IE11 Windows 10 Reading: Image ignored. JAWS 2018.1811.2 Chrome 73 Windows 10 Reading: Image ignored. JAWS 2018.1811.2 FF60 Windows 10 Reading: Image ignored. JAWS 2018.1811.2 IE11 Windows 10 Reading: Image ignored. VoiceOver macOS 11.5 Safari 15.0 macOS 11.5.2 Reading: Image filename read out. VoiceOver macOS 10.15 Safari 14.1 macOS 10.15.7 Reading: Image filename read out. VoiceOver macOS 10.14 Safari 13.0 macOS 10.14.6 Reading: Image filename read out. VoiceOver macOS 10.13 Safari 12.1 macOS 10.13.6 Reading: Image filename read out. VoiceOver iOS 14.7 Safari iOS 14.7 iOS 14.7 Touch: Image filename read out. VoiceOver iOS 13.3 Safari iOS 13.3 iOS 13.3 Touch: Image filename read out. VoiceOver iOS 12.4 Safari iOS 12.4 iOS 12.4.1 Touch: Image filename read out. VoiceOver iOS 11.4 Safari iOS 11.4 iOS 11.4.1 Touch: Image filename read out.
	https://geocams.pl/	Line 511 512 513 514 515 ...
Informative These messages are for information only and do not indicate errors or conformance problems
	`role` is ignored on this element.	ARIA 1.1 Role Conflict	1 pages
	The presentational roles `role=presentation` and `role=none` are ignored when applied to interactive elements like `button` and elements with global aria attributes like `aria-label`. This also happens when `img alt=''` is used with global aria attributes.
	https://geocams.pl/	Line 511 512 513 514 515 ...
	Expand all 5 issues