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 5 issues on 6 pages
	An image with a null `alt` attribute should not have `title`, `aria-label` or `aria-labelledby` attributes.	WCAG 2.1 A F39 Section 508 (2017) A F39	2 pages
	If the image should be voiced use a descriptive `alt` attribute. If the image is purely decorative remove any `title` and ARIA label attributes. Impact on users: JAWS : Ignores all images with `alt=''`. NVDA : Reads some images with `alt=''` and a `title` or ARIA label. VoiceOver : Reads images with `alt=''` and a `title` or ARIA label.
	http://what.in.ua/	Line 239
	http://what.in.ua/page/vistavka-lenerdzhi-krashhi-foto-prirodi	Line 391
	Each `a` element must contain text or an `img` with an `alt` attribute.	WCAG 2.1 A F89 Section 508 (2017) A F89	2 pages
	A link name allows screen readers to voice what the links does. If there is no link text or the `alt` text is blank, 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
	http://what.in.ua/category/art	Line 103
	http://what.in.ua/category/cultural-events	Line 103
	HTML form control has no label.	WCAG 2.1 A F68 Section 508 (2017) A F68	6 pages
	A label (or name) linked to the control allows screen readers to voice the label correctly when reading the control. To add a label do one of the following: Use a `label` element with the `for` attribute set to the ID of the form control Wrap a `label` element around the form control Add a `title` attribute Add an `aria-label` attribute Add an `aria-labelledby` attribute
	http://what.in.ua/	Line 201
	http://what.in.ua/category/art	Line 990
	http://what.in.ua/category/cultural-events	Line 989
	http://what.in.ua/page/vistavka-lenerdzhi-krashhi-foto-prirodi	Line 321 343 683
	This issue was found on another 2 pages. The trial version is limited to showing issues on 4 pages.
	`img` elements must have an accessible name.	WCAG 2.1 A F65 Section 508 (2017) A F65	3 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 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 macOS 10.12 Safari 10.1.2 macOS 10.12.6 Reading: 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. VoiceOver iOS 10.3 Safari iOS 10.3 iOS 10.3 Touch: Image filename read out.
	http://what.in.ua/	Line 56
	http://what.in.ua/category/art	Line 104
	http://what.in.ua/category/cultural-events	Line 104
	Use the `lang` attribute to identify the language of the page.	WCAG 2.1 A 3.1.1 Section 508 (2017) A 3.1.1	6 pages
	In HTML add a `lang` attribute containing a language code to the `html` tag, and in PDF set the language using Document Properties in Acrobat. This allows screen readers to pronounce words correctly.
	http://what.in.ua/	Line 2
	http://what.in.ua/category/art	Line 3
	http://what.in.ua/category/cultural-events	Line 3
	http://what.in.ua/page/vistavka-lenerdzhi-krashhi-foto-prirodi	Line 3
	This issue was found on another 2 pages. The trial version is limited to showing issues on 4 pages.
Level AA 1 issues on 6 pages
	Phrases in a different language should be in a `span` or `div` with a `lang` attribute.	WCAG 2.1 AA 3.1.2 Section 508 (2017) AA 3.1.2	6 pages
	Non-English phrases in English text, or English phrases in non-English text, will be mispronounced by a screen reader unless they are identified with a `lang` attribute.
	HTML language: `lang=` http://what.in.ua/	Line 256
	HTML language: `lang=` http://what.in.ua/category/art	Line 1106
	HTML language: `lang=` http://what.in.ua/category/cultural-events	Line 1105
	HTML language: `lang=` http://what.in.ua/page/vistavka-lenerdzhi-krashhi-foto-prirodi	Line 799
	This issue was found on another 2 pages. The trial version is limited to showing issues on 4 pages.
	Expand all 6 issues

Site Report

Level A

Level AA