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 | Section 508 | Key |
|---|
| A |  | | Priority A - accessibility users will find it impossible to use some pages |
|---|
| AA |  | | Priority AA - accessibility users will find it difficult to use some pages |
|---|
| AAA |  | | Priority AAA - accessibility users will find it somewhat difficult to use some pages |
|---|
| Priority | URL / Description | | Line |
|---|
Priority 1 Issues (Level A) |
| | Each A tag must contain text or an IMG with an ALT attribute. | WCAG 2.0 A F89 | |
|
Add text to the link, or ALT text if the link contains an image. If there is no link text or the ALT tag is blank, screen readers have nothing to read, so read out the URL instead.
Link A elements labelled with a TITLE attribute, and only containing an image don't work in:
- WindowEyes 8.4 with IE11 (the link HREF is read instead)
- VoiceOver on OSX 10.9 (the image filename is read instead)
| | |
| http://rokesh.ir/ | | 522 |
| http://rokesh.ir/blog/ | | 376 513 514 515 |
| http://rokesh.ir/pay/ | | 251 252 253 |
| http://rokesh.ir/wordpress-themes/ | | 306 369 370 371 |
| This issue was found on another 3 pages.
The trial version is limited to showing issues on 4 pages.
| | |
| | Provide a way to skip repetitive navigation links. | Section 508 1194.22 (o) | |
|
Without a skip link, screen readers read out the navigation links on every page before reading the page content.
Headings can be a substitute in limited circumstances, but they're not used by all screen reader users,
and many other assistive technology users have no way to navigate via headings.
Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users:
<a class="accessible" href="#main">[Skip to Content]</a>
| | |
| http://rokesh.ir/ | | 522 |
| http://rokesh.ir/blog/ | | 373 |
| http://rokesh.ir/wordpress-themes/ | | 303 |
| | This form control has no programmatically determined name. | WCAG 2.0 A F68 Section 508 1194.22 (n) | |
|
A programmatically determined name allows screen readers to tell the user what the control does. To add a name 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 an ARIA-LABELLED attribute
- Add a TITLE attribute
- Add an ARIA-LABEL attribute (not supported in all screen readers)
| | |
| http://rokesh.ir/ | | 500 522 |
| http://rokesh.ir/blog/ | | 73 76 126 493 |
| http://rokesh.ir/pay/ | | 72 75 125 231 |
| http://rokesh.ir/wordpress-themes/ | | 70 73 123 349 |
| This issue was found on another 3 pages.
The trial version is limited to showing issues on 4 pages.
| | |
| | This form has fields without LABEL elements or TITLE attributes. | Section 508 1194.22 (n) | |
|
Screen readers use LABEL elements or TITLE attributes to describe form fields to non-sighted users.
Without these, forms are very hard to use with a screen reader.
Forms designed to be completed online shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. | | |
| http://rokesh.ir/ | | 500 |
| http://rokesh.ir/blog/ | | 73 76 126 |
| http://rokesh.ir/pay/ | | 72 75 125 |
| http://rokesh.ir/wordpress-themes/ | | 70 73 123 |
| This issue was found on another 3 pages.
The trial version is limited to showing issues on 4 pages.
| | |
| | This page has duplicate IDs which cause problems in screen readers. | WCAG 2.0 A F77 | |
|
Two or more elements on this page share the same ID, which cause problems in screen readers which use IDs for labeling controls and table headings.
This also causes problems in JavaScript methods like getElementById and querySelector, which behave inconsistently when duplicate IDs are present.
Change the ID so it is unique for each element. | | |
| http://rokesh.ir/ | | 142 217 |
| http://rokesh.ir/blog/ | | 140 |
| http://rokesh.ir/pay/ | | 139 |
| http://rokesh.ir/wordpress-themes/ | | 137 |
| | This page has markup errors, causing screen readers to miss content. | WCAG 2.0 A F70 | |
|
Fix the errors listed on the Standards tab of this report. Markup errors like missing end tags mean screen readers may skip important content. | | |
| http://rokesh.ir/ | | 142 217 |
| http://rokesh.ir/pay/ | | 139 |
| http://rokesh.ir/wp-login.php?action=register | | 15 16 |
| http://rokesh.ir/wp-login.php?redirect_to=http%3A%2F%2Frokesh.ir%2F | | 15 16 |
| This issue was found on another 3 pages.
The trial version is limited to showing issues on 4 pages.
| | |
Priority 2 Issues (Level AA) |
| | Headings should not be empty. | WCAG 2.0 AA G130 | |
|
Add text to the heading, or ALT text if the heading contains an image. Screen readers read out page headings, allowing users to quickly skip to a section, but some older screen readers do not ignore empty headings. | | |
| http://rokesh.ir/wordpress-themes/ | | 171 |
| http://rokesh.ir/wordpress-themes/professional-wordpress-themes/ | | 171 |
Priority 3 Issues (Level AAA) |
| | Avoid specifying a new window as the target of a link with target="_blank". | WCAG 2.0 AAA F22 | |
|
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 a warning into the link text like the following: "opens in a new window". | | |
| http://rokesh.ir/ | | 522 |
| http://rokesh.ir/blog/ | | 382 445 513 514 515
...
|
| http://rokesh.ir/pay/ | | 251 252 253 |
| http://rokesh.ir/wordpress-themes/ | | 369 370 371 |
| This issue was found on another 3 pages.
The trial version is limited to showing issues on 4 pages.
| | |
| | If several links on a page use the same link text, all those links should point to the same destination. | WCAG 2.0 AAA 2.4.9 | |
|
If several links refer to different targets but share the same link text, add additional link text hidden offscreen by CSS. | | |
| This text is used in some of the duplicated links: "قالب های بیشتر"
http://rokesh.ir/ | | 522 |
| 9 issues on 10 pages |