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 14 issues on 7 pages
	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	7 pages

	`id=header__menu-list` `id=header__menu-list` `id=header__menu-list` `id=header__menu-list` http://xlib.info/	Line 187 187 228 245
	`id=header__menu-list` `id=header__menu-list` `id=header__menu-list` `id=header__menu-list` http://xlib.info/dobavit-rasskaz	Line 187 187 228 245
	`id=header__menu-list` `id=header__menu-list` `id=header__menu-list` `id=header__menu-list` http://xlib.info/genre	Line 187 187 228 245
	`id=header__menu-list` `id=header__menu-list` `id=header__menu-list` `id=header__menu-list` http://xlib.info/srch	Line 187 187 228 245
	This issue was found on another 3 pages. The trial version is limited to showing issues on 4 pages.
	Each `a` element must contain text or an `img` with an `alt` attribute.	WCAG 2.1 A F89 Section 508 (2017) A F89	7 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 a descriptive `img alt` attribute if the link contains an `img` element	2.4.4 2.4.9 4.1.2
	http://xlib.info/	Line 2531 3415
	http://xlib.info/dobavit-rasskaz	Line 754 1630
	http://xlib.info/genre	Line 708 25455
	http://xlib.info/srch	Line 1217 2093
	This issue was found on another 3 pages. The trial version is limited to showing issues on 4 pages.
	Element `a` not allowed as child element in this context.	HTML5 WCAG 2.1 A 4.1.1 Section 508 (2017) A 4.1.1	7 pages

	http://xlib.info/	Line 2501 2507 2510 3492 3527
	http://xlib.info/dobavit-rasskaz	Line 1707 1742
	http://xlib.info/genre	Line 639 641 643 645 647 ...
	http://xlib.info/srch	Line 630 641 652 663 674 ...
	This issue was found on another 3 pages. The trial version is limited to showing issues on 4 pages.
	Element `button` not allowed as child element in this context.	HTML5 WCAG 2.1 A 4.1.1 Section 508 (2017) A 4.1.1	7 pages

	http://xlib.info/	Line 3139
	http://xlib.info/dobavit-rasskaz	Line 1362
	http://xlib.info/genre	Line 25187
	http://xlib.info/srch	Line 1825
	This issue was found on another 3 pages. The trial version is limited to showing issues on 4 pages.
	Element `input` not allowed as child element in this context.	HTML5 WCAG 2.1 A 4.1.1 Section 508 (2017) A 4.1.1	7 pages

	http://xlib.info/	Line 561
	http://xlib.info/dobavit-rasskaz	Line 561 574 586 598 602 ...
	http://xlib.info/genre	Line 561
	http://xlib.info/srch	Line 561
	This issue was found on another 3 pages. The trial version is limited to showing issues on 4 pages.
	Element `select` not allowed as child element in this context.	HTML5 WCAG 2.1 A 4.1.1 Section 508 (2017) A 4.1.1	1 pages

	http://xlib.info/dobavit-rasskaz	Line 628
	Element `textarea` not allowed as child element in this context.	HTML5 WCAG 2.1 A 4.1.1 Section 508 (2017) A 4.1.1	7 pages

	http://xlib.info/	Line 3115
	http://xlib.info/dobavit-rasskaz	Line 717 1338
	http://xlib.info/genre	Line 25163
	http://xlib.info/srch	Line 1801
	This issue was found on another 3 pages. The trial version is limited to showing issues on 4 pages.
	HTML form control has no accessible name.	WCAG 2.1 A F68 Section 508 (2017) A F68	7 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	4.1.2
	http://xlib.info/	Line 309 318
	http://xlib.info/dobavit-rasskaz	Line 574 586 598 602 616 ...
	http://xlib.info/genre	Line 309 318
	http://xlib.info/srch	Line 309 318
	This issue was found on another 3 pages. The trial version is limited to showing issues on 4 pages.
	`iframe` and `frame` elements must have a `title` attribute.	WCAG 2.1 A 4.1.2 Section 508 (2017) A 4.1.2	2 pages
	Add a `title` attribute or ARIA label to each `iframe` and `frame` element (e.g. `title='Main Content'`). Without a title some screen readers read out the frame filename, which is usually meaningless. Impact on users: VoiceOver macOS 12.5 Safari 15.6 macOS 12.5.1 Reading: Meaningless frame title read out. VoiceOver macOS 11.5 Safari 15.0 macOS 11.5.2 Reading: Meaningless frame title read out. VoiceOver macOS 10.15 Safari 14.1 macOS 10.15.7 Reading: Meaningless frame title read out. VoiceOver macOS 10.14 Safari 13.0 macOS 10.14.6 Reading: Meaningless frame title read out.
	http://xlib.info/genre/minet	Line 672 2599
	http://xlib.info/t/trahnul-jenu-rogatogo-kretina	Line 956 1111
	`img` elements must have an accessible name.	WCAG 2.1 A F65 Section 508 (2017) A F65	7 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 2022.2 Chrome 105 Windows 10 Reading: Image ignored. NVDA 2022.2 FF102 Windows 10 Reading: Image ignored. NVDA 2022.2 Edge 105 Windows 10 Reading: Image ignored. NVDA 2021.2 Chrome 94 Windows 10 Reading: Image ignored. NVDA 2021.2 FF91 Windows 10 Reading: Image ignored. NVDA 2021.2 Edge 94 Windows 10 Reading: Image ignored. NVDA 2020.2 Chrome 86 Windows 10 Reading: Image ignored. NVDA 2020.2 FF78 Windows 10 Reading: Image ignored. NVDA 2020.2 Edge 92 Windows 10 Reading: Image ignored. NVDA 2019.2 Chrome 79 Windows 10 Reading: Image unlabeled. NVDA 2019.2 FF68 Windows 10 Reading: Image ignored. JAWS 2022.2207.25 Chrome 105 Windows 10 Reading: Image ignored. JAWS 2022.2207.25 FF102 Windows 10 Reading: Image ignored. JAWS 2022.2207.25 Edge 105 Windows 10 Reading: Image ignored. JAWS 2021.2107.12 Chrome 94 Windows 10 Reading: Image ignored. JAWS 2021.2107.12 FF91 Windows 10 Reading: Image ignored. JAWS 2021.2107.12 Edge 94 Windows 10 Reading: Image ignored. JAWS 2020.2008.24 Chrome 86 Windows 10 Reading: Image ignored. JAWS 2020.2008.24 FF78 Windows 10 Reading: Image ignored. JAWS 2020.2008.24 Edge 92 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. VoiceOver macOS 12.5 Safari 15.6 macOS 12.5.1 Reading: Image filename read out. 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 iOS 15.6 Safari iOS 15.6 iOS 15.6 Touch: 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.	1.1.1
	http://xlib.info/	Line 2532 3416
	http://xlib.info/dobavit-rasskaz	Line 755 1631
	http://xlib.info/genre	Line 25456
	http://xlib.info/srch	Line 1218 2094
	This issue was found on another 3 pages. The trial version is limited to showing issues on 4 pages.
	Removing the underline from links makes it hard for color-blind users to see them.	WCAG 2.1 A F73 Section 508 (2017) A F73	7 pages
	Remove the `text-decoration:none` property from your link styles, or add other style attributes in addition to color changes to make links visible to people without color vision.	1.4.1
	http://xlib.info/	Line 3385 3390 3395 3400
	http://xlib.info/dobavit-rasskaz	Line 1600 1605 1610 1615
	http://xlib.info/genre	Line 713 718 723 728 733 ...
	http://xlib.info/srch	Line 2063 2068 2073 2078
	This issue was found on another 3 pages. The trial version is limited to showing issues on 4 pages.
	This `input` button has no `value` attribute and no label.	WCAG 2.1 A 4.1.2 Section 508 (2017) A 4.1.2	7 pages
	A label (or name) allows screen readers to tell users what the control does. To add a name do one of the following: Add a `value` attribute saying what the button does Add a `title` attribute Add an `aria-label` attribute Add an `aria-labelledby` attribute
	http://xlib.info/	Line 561
	http://xlib.info/dobavit-rasskaz	Line 561
	http://xlib.info/genre	Line 561
	http://xlib.info/srch	Line 561
	This issue was found on another 3 pages. The trial version is limited to showing issues on 4 pages.
	Use semantic markup like `strong` instead of using the CSS `font-weight` property.	WCAG 2.1 A F2 Section 508 (2017) A F2	1 pages
	Use the `strong` element instead of the `span` element for bold text.	1.3.1
	http://xlib.info/t/trahnul-jenu-rogatogo-kretina	Line 1327
	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	7 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://xlib.info/	Line 3
	http://xlib.info/dobavit-rasskaz	Line 3
	http://xlib.info/genre	Line 3
	http://xlib.info/srch	Line 3
	This issue was found on another 3 pages. The trial version is limited to showing issues on 4 pages.
Level AA 4 issues on 7 pages
	Ensure that text and background colors have enough contrast.	WCAG 2.1 AA 1.4.3 Section 508 (2017) AA 1.4.3	7 pages
	Some users find it hard to read light gray text on a white background, dark gray text on a black background and white text on a red background. The contrast ratio should be 3.0 or more for 18 point text, or larger The contrast ratio should be 3.0 or more for 14 point bold text, or larger The contrast ratio should be 4.5 or more for all other text	1.4.6
	The text color to background color contrast ratio after composition is: 2.32 with `color: rgb(170,170,170);background-color: rgb(255,255,255);font-size: 8.25pt;font-weight: 700;` 2.32 with `color: rgb(170,170,170);background-color: rgb(255,255,255);font-size: 8.25pt;font-weight: 700;` 2.32 with `color: rgb(170,170,170);background-color: rgb(255,255,255);font-size: 8.25pt;font-weight: 700;` 2.32 with `color: rgb(170,170,170);background-color: rgb(255,255,255);font-size: 8.25pt;font-weight: 700;` 2.32 with `color: rgb(170,170,170);background-color: rgb(255,255,255);font-size: 8.25pt;font-weight: 700;` http://xlib.info/	Line 696 700 704 708 712 ...
	The text color to background color contrast ratio after composition is: 4.22 with `color: rgb(119,119,119);background-color: rgb(248,248,248);font-size: 9.75pt;font-weight: 400;` 4.22 with `color: rgb(119,119,119);background-color: rgb(248,248,248);font-size: 9.75pt;font-weight: 400;` 4.22 with `color: rgb(119,119,119);background-color: rgb(248,248,248);font-size: 9.75pt;font-weight: 400;` 4.22 with `color: rgb(119,119,119);background-color: rgb(248,248,248);font-size: 9.75pt;font-weight: 400;` 4.22 with `color: rgb(119,119,119);background-color: rgb(248,248,248);font-size: 9.75pt;font-weight: 400;` http://xlib.info/dobavit-rasskaz	Line 1204 1208 1212 1216 1220 ...
	The text color to background color contrast ratio after composition is: http://xlib.info/genre	Line 25204 25211 25218 25225 25232 ...
	The text color to background color contrast ratio after composition is: 4.22 with `color: rgb(119,119,119);background-color: rgb(248,248,248);font-size: 9.75pt;font-weight: 400;` 4.22 with `color: rgb(119,119,119);background-color: rgb(248,248,248);font-size: 9.75pt;font-weight: 400;` 4.22 with `color: rgb(119,119,119);background-color: rgb(248,248,248);font-size: 9.75pt;font-weight: 400;` 4.22 with `color: rgb(119,119,119);background-color: rgb(248,248,248);font-size: 9.75pt;font-weight: 400;` 4.22 with `color: rgb(119,119,119);background-color: rgb(248,248,248);font-size: 9.75pt;font-weight: 400;` http://xlib.info/srch	Line 1667 1671 1675 1679 1683 ...
	This issue was found on another 3 pages. The trial version is limited to showing issues on 4 pages.
	If you set any of the colors on the `body` or `a` elements you must set all of them.	WCAG 2.1 AA F24 Section 508 (2017) AA F24	7 pages
	In HTML the color attributes are `text`, `bgcolor`, `link`, `alink` and `vlink`. In CSS the attributes are `color` and `background-color`. Some users have browser defaults set to white text on a black background, so setting one color without setting the others can result in black text on a black background.	1.4.3 1.4.6 1.4.8
	The colors used are: `color: rgb(122,122,122)` and `background: rgb(255,255,255)` from browser settings `color: rgb(122,122,122)` and `background: rgb(255,255,255)` from browser settings `color: rgb(122,122,122)` and `background: rgb(255,255,255)` from browser settings `color: rgb(122,122,122)` and `background: rgb(255,255,255)` from browser settings `color: rgb(122,122,122)` and `background: rgb(255,255,255)` from browser settings http://xlib.info/	Line 3156 3163 3170 3177 3184 ...
	The colors used are: `color: rgb(122,122,122)` and `background: rgb(255,255,255)` from browser settings `color: rgb(122,122,122)` and `background: rgb(255,255,255)` from browser settings `color: rgb(122,122,122)` and `background: rgb(255,255,255)` from browser settings `color: rgb(122,122,122)` and `background: rgb(255,255,255)` from browser settings `color: rgb(122,122,122)` and `background: rgb(255,255,255)` from browser settings http://xlib.info/dobavit-rasskaz	Line 1379 1386 1393 1400 1407 ...
	The colors used are: `color: rgb(122,122,122)` and `background: rgb(255,255,255)` from browser settings `color: rgb(122,122,122)` and `background: rgb(255,255,255)` from browser settings `color: rgb(122,122,122)` and `background: rgb(255,255,255)` from browser settings `color: rgb(122,122,122)` and `background: rgb(255,255,255)` from browser settings `color: rgb(122,122,122)` and `background: rgb(255,255,255)` from browser settings http://xlib.info/genre	Line 25204 25211 25218 25225 25232 ...
	The colors used are: `color: rgb(122,122,122)` and `background: rgb(255,255,255)` from browser settings `color: rgb(122,122,122)` and `background: rgb(255,255,255)` from browser settings `color: rgb(122,122,122)` and `background: rgb(255,255,255)` from browser settings `color: rgb(122,122,122)` and `background: rgb(255,255,255)` from browser settings `color: rgb(122,122,122)` and `background: rgb(255,255,255)` from browser settings http://xlib.info/srch	Line 1842 1849 1856 1863 1870 ...
	This issue was found on another 3 pages. The trial version is limited to showing issues on 4 pages.
	The CSS outline or border style on this element makes it difficult or impossible to see the dotted link focus outline.	WCAG 2.1 AA F78 Section 508 (2017) AA F78	7 pages
	Do not remove the default outline style, and change any border styles to avoid obscuring the focus outline around focusable elements. Using a border or outline style that obscures the focus ring causes problems for keyboard-only users in: Chrome (obscures the focus indicator on links, buttons, dropdowns and range controls) Firefox (obscures the focus indicator on links) Internet Explorer (obscures the focus indicator on links, buttons and range controls)	1.4.11 2.4.7
	`:focus` and `:not(:focus)` have same outline: `:focus` and `:not(:focus)` have same outline: `:focus` and `:not(:focus)` have same outline: `:focus` and `:not(:focus)` have same outline: `:focus` and `:not(:focus)` have same outline: http://xlib.info/	Line 342 605 696 700 704 ...
	`:focus` and `:not(:focus)` have same outline: `:focus` and `:not(:focus)` have same outline: `:focus` and `:not(:focus)` have same outline: `:focus` and `:not(:focus)` have same outline: `:focus` and `:not(:focus)` have same outline: http://xlib.info/dobavit-rasskaz	Line 342 1204 1208 1212 1216 ...
	http://xlib.info/genre	Line 342 639 641 643 645 ...
	`:focus` and `:not(:focus)` have same outline: `:focus` and `:not(:focus)` have same outline: `:focus` and `:not(:focus)` have same outline: `:focus` and `:not(:focus)` have same outline: `:focus` and `:not(:focus)` have same outline: http://xlib.info/srch	Line 342 1667 1671 1675 1679 ...
	This issue was found on another 3 pages. The trial version is limited to showing issues on 4 pages.
	User interface controls must have a contrast ratio of at least 3:1 against adjacent colors.	WCAG 2.1 1.4.11	7 pages
	If the control has a visible edge, make sure this has sufficient contrast against the area outside the control.
	The contrast ratio between the control edge and surrounding area is: 2.32 with `border-color: rgb(170,170,170);background-color: rgb(249,249,249);` box margin `rgb(255,255,255);` 2.32 with `border-color: rgb(170,170,170);background-color: rgb(249,249,249);` box margin `rgb(255,255,255);` http://xlib.info/	Line 309 318
	The contrast ratio between the control edge and surrounding area is: 2.32 with `border-color: rgb(170,170,170);background-color: rgb(249,249,249);` box margin `rgb(255,255,255);` 2.32 with `border-color: rgb(170,170,170);background-color: rgb(249,249,249);` box margin `rgb(255,255,255);` http://xlib.info/dobavit-rasskaz	Line 309 318
	The contrast ratio between the control edge and surrounding area is: 2.32 with `border-color: rgb(170,170,170);background-color: rgb(249,249,249);` box margin `rgb(255,255,255);` 2.32 with `border-color: rgb(170,170,170);background-color: rgb(249,249,249);` box margin `rgb(255,255,255);` http://xlib.info/genre	Line 309 318
	The contrast ratio between the control edge and surrounding area is: 2.32 with `border-color: rgb(170,170,170);background-color: rgb(249,249,249);` box margin `rgb(255,255,255);` 2.32 with `border-color: rgb(170,170,170);background-color: rgb(249,249,249);` box margin `rgb(255,255,255);` http://xlib.info/srch	Line 309 318
	This issue was found on another 3 pages. The trial version is limited to showing issues on 4 pages.
Level AAA 4 issues on 7 pages
	Avoid specifying a new window as the target of a link with `target=_blank`.	WCAG 2.1 AAA F22	7 pages
	Displaying new windows without warning can be very confusing to non-sighted and mobile users. Some screen readers and mobile devices give very little indication a new tab or window has opened. If you cannot avoid displaying a new window, insert an "opens in a new window" warning into the link text or add the warning to the link using a `title` attribute or `aria-label` attribute.	3.2.5
	http://xlib.info/	Line 265 3385 3390 3400 3560 ...
	http://xlib.info/dobavit-rasskaz	Line 265 1600 1605 1615 1775 ...
	http://xlib.info/genre	Line 265 25425 25430 25440 25600 ...
	http://xlib.info/srch	Line 265 2063 2068 2078 2238 ...
	This issue was found on another 3 pages. The trial version is limited to showing issues on 4 pages.
	Don't use CSS animations or transitions in interactions without giving the user a way to turn them off.	WCAG 2.1 2.3.3	7 pages
	Use the `@media (prefers-reduced-motion)` media query to respect user preferences.
	`:hover transition: all 0.2s` `:hover transition: all 0.2s` `:hover transition: all 0.2s` `:hover transition: all 0.2s` `:hover transition: all 0.2s` http://xlib.info/	Line 605 732 867 982 1113 ...
	`:hover transition: all 0.2s` `:hover transition: all 0.2s` `:hover transition: all 0.2s` `:hover transition: all 0.2s` `:hover transition: all 0.2s` http://xlib.info/dobavit-rasskaz	Line 1204 1208 1212 1216 1220 ...
	`:hover transition: all 0.15s` `:hover transition: all 0.15s` `:hover transition: all 0.15s` `:hover transition: all 0.2s` `:hover transition: all 0.2s` http://xlib.info/genre	Line 187 228 245 446 452
	`:hover transition: all 0.2s` `:hover transition: all 0.2s` `:hover transition: all 0.2s` `:hover transition: all 0.2s` `:hover transition: all 0.2s` http://xlib.info/srch	Line 1667 1671 1675 1679 1683 ...
	This issue was found on another 3 pages. The trial version is limited to showing issues on 4 pages.
	Ensure that text and background colors have a 7:1 contrast ratio.	WCAG 2.1 AAA 1.4.6	7 pages
	Some users find it hard to read light gray text on a white background, dark gray text on a black background and white text on a red background. The contrast ratio should be 4.5 or more for 18 point text, or larger The contrast ratio should be 4.5 or more for 14 point bold text, or larger The contrast ratio should be 7.0 or more for all other text
	The text color to background color contrast ratio after composition is: 5.65 with `color: rgb(255,255,255);background-color: rgb(24,105,180);font-size: 11.25pt;font-weight: 400;` 5.65 with `color: rgb(255,255,255);background-color: rgb(24,105,180);font-size: 11.25pt;font-weight: 400;` 5.65 with `color: rgb(255,255,255);background-color: rgb(24,105,180);font-size: 11.25pt;font-weight: 400;` 4.61 with `color: rgb(111,111,111);background-color: rgb(245,245,245);font-size: 12pt;font-weight: 700;` 4.61 with `color: rgb(111,111,111);background-color: rgb(245,245,245);font-size: 12pt;font-weight: 700;` http://xlib.info/	Line 195 235 252 605 732 ...
	The text color to background color contrast ratio after composition is: 5.65 with `color: rgb(255,255,255);background-color: rgb(24,105,180);font-size: 11.25pt;font-weight: 400;` 5.65 with `color: rgb(255,255,255);background-color: rgb(24,105,180);font-size: 11.25pt;font-weight: 400;` 5.65 with `color: rgb(255,255,255);background-color: rgb(24,105,180);font-size: 11.25pt;font-weight: 400;` 5.15 with `color: rgb(221,0,0);background-color: rgb(255,255,255);font-size: 11.25pt;font-weight: 400;` 4.77 with `color: rgb(217,6,96);background-color: rgb(248,248,248);font-size: 9.75pt;font-weight: 400;` http://xlib.info/dobavit-rasskaz	Line 195 235 252 721 1286 ...
	The text color to background color contrast ratio after composition is: 5.65 with `color: rgb(255,255,255);background-color: rgb(24,105,180);font-size: 11.25pt;font-weight: 400;` 5.65 with `color: rgb(255,255,255);background-color: rgb(24,105,180);font-size: 11.25pt;font-weight: 400;` 5.65 with `color: rgb(255,255,255);background-color: rgb(24,105,180);font-size: 11.25pt;font-weight: 400;` 5.07 with `color: rgb(217,6,96);background-color: rgb(255,255,255);font-size: 8.25pt;font-weight: 400;` 5.07 with `color: rgb(217,6,96);background-color: rgb(255,255,255);font-size: 11.25pt;font-weight: 400;` http://xlib.info/genre	Line 195 235 252 593 25425 ...
	The text color to background color contrast ratio after composition is: 5.65 with `color: rgb(255,255,255);background-color: rgb(24,105,180);font-size: 11.25pt;font-weight: 400;` 5.65 with `color: rgb(255,255,255);background-color: rgb(24,105,180);font-size: 11.25pt;font-weight: 400;` 5.65 with `color: rgb(255,255,255);background-color: rgb(24,105,180);font-size: 11.25pt;font-weight: 400;` 5.07 with `color: rgb(217,6,96);background-color: rgb(255,255,255);font-size: 8.25pt;font-weight: 400;` 4.77 with `color: rgb(217,6,96);background-color: rgb(248,248,248);font-size: 9.75pt;font-weight: 400;` http://xlib.info/srch	Line 195 235 252 574 1749 ...
	This issue was found on another 3 pages. The trial version is limited to showing issues on 4 pages.
	Many people with cognitive disabilities (including dyslexia) find text styled with `text-align:justify` hard to read.	WCAG 2.1 AAA F88	7 pages
	Justified text aligned to both the left and the right margins creates rivers of white running down the page due to extra word spacing. This makes justified text difficult to read for some people. The best way to avoid the problem is avoid justified text.	1.4.8
	http://xlib.info/	Line 593 719 854 965 2515 ...
	http://xlib.info/dobavit-rasskaz	Line 571 583 595 613 625 ...
	http://xlib.info/genre	Line 589
	http://xlib.info/srch	Line 570 615 634 645 1201 ...
	This issue was found on another 3 pages. The trial version is limited to showing issues on 4 pages.
	Expand all 22 issues

Site Report

Level A

Level AA

Level AAA