[Skip navigation links]

8% of pages8%of pages

Accessibility

3 pages with accessibility issues

better than average8% of the pages on this site have accessibility issues, which is better than average. The percentage of pages with accessibility issues averages 12% on other sites.

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.

WCAG 2.2

Level A8% Pages with level A issues have critical accessibility barriers and are unusable by some people.

Level AA0% Pages with level AA issues have major accessibility barriers and are very difficult to use.

Level AAA3% Pages with level AAA issues have minor accessibility barriers and can be difficult to use.

Section 508

Level A8% Pages with level A issues have critical accessibility barriers and are unusable by some people.

Level AA0% Pages with level AA issues have major accessibility barriers and are very difficult to use.

ARIA

Errors0% Errors indicate conformance errors, and appear when mandatory specification requirements are not met.

Warnings0% Warnings do not indicate conformance errors, but appear when optional specification requirements are not met.

PriorityDescription and URLGuideline and Line NumberCount

Level A

3 issues on 3 pages

Pages with level A issues have critical accessibility barriers and are unusable by some people.

CriticalHTML form control has no accessible name. WCAG A F68 WCAG 4.1.2 508 A F68 1 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
Rule: AccHtmlControlLabelMissing
<textarea placeholder='Сообщение' rows='5'></textarea>
Line 98

https://onpoints.ru/feedback

CriticalLinks must have an accessible name. WCAG A F89 WCAG 2.4.4 WCAG 2.4.9 WCAG 4.1.2 508 A F89 3 pages

A link name allows screen readers to voice what the links does. If there is no link content, or the link content 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 labeling the link if it contains an img element
img elements with role=presentation or role=none are not included in the link's accessible name.		Rule: AccHtmlLinkTextBlank
<a href='/'><img src='/images/logo.png' alt='' class='logo-module__-...'></a>
Line 78
<a href='/'><img src='/images/logo.png' alt='' class='logo-module__-...'></a>
Line 816

https://onpoints.ru/

<a href='/'><img src='/images/logo.png' alt='' class='logo-module__-...'></a>
Line 57
<a href='/'><img src='/images/logo.png' alt='' class='logo-module__-...'></a>
Line 104

https://onpoints.ru/faq

<a href='/'><img src='/images/logo.png' alt='' class='logo-module__-...'></a>
Line 61
<a href='/'><img src='/images/logo.png' alt='' class='logo-module__-...'></a>
Line 128

https://onpoints.ru/feedback

CriticalUse HTML headings instead of applying CSS heading styles to non-headings. WCAG A F2 WCAG 1.3.1 508 A F2 1 pages
Screen reader users rely on headings to navigate within pages. Either add role=heading with aria-level or use h1-h6 elements to identify the element as a heading to screen readers. Rule: AccWcag2-F2-1
<div class='info-item-module__gIpOoq__title'>Вопросы?</div>
Line 80

https://onpoints.ru/faq

Level AAA

2 issues on 1 pages

Pages with level AAA issues have minor accessibility barriers and can be difficult to use.

ImportantAvoid specifying a new window as the target of a link with target=_blank. WCAG AAA F22 WCAG 3.2.5 1 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-describedby attribute. Rule: AccHtmlLinkTargetNew
<a href='....apple.com/ru/app/id6472654371' target='_blank'>...</a>
Line 116
<a href='....apple.com/ru/app/id6472654371' target='_blank'>...</a>
Line 772
<a href='...ls?id=com.atpoints.application' target='_blank'>...</a>
Line 120
<a href='...g/app/com.atpoints.application' target='_blank'>...</a>
Line 124
<a href='...ls?id=com.atpoints.application' target='_blank'>...</a>
Line 776

https://onpoints.ru/

ImportantEach section of content should begin with a heading element (h1, h2, h3), but this page has no headings. WCAG AAA 2.4.10 1 pages
In HTML place headings before each section of content, making sure the main heading is h1, sub-headings are h2 and so on. For PDFs produced from Word, use the Heading 1, Heading 2 and Heading 3 styles. Rule: AccPageNoHeadings
<body class='roboto_6e093269-...'><div hidden=''></div>...</body>
Line 67

https://onpoints.ru/

Expand all 5 issues