This tab shows accessibility issues, indicating problems for older users, people with disabilities and those with accessibility needs.
| WCAG2 | 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 |
|---|
| Priority | URL / Description | | Line |
|---|
 | All ONMOUSEOUT handlers should have an equivalent ONBLUR handler. | Section 508 1194.22 (l) WCAG2 A F54 | |
|
Some users are unable to use a mouse, so use the keyboard instead. Add an equivalent keyboard event handler to help these users. | | |
| http://www.pktevents.co.uk/ | | 80 |
| | All ONMOUSEOVER handlers should have an equivalent ONFOCUS handler. | Section 508 1194.22 (l) WCAG2 A F54 | |
|
Some users are unable to use a mouse, so use the keyboard instead. Add an equivalent keyboard event handler to help these users. | | |
| http://www.pktevents.co.uk/ | | 80 |
| | Each A tag must contain text or an IMG with an ALT attribute. | WCAG2 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. | | |
| http://www.pktevents.co.uk/page4.html | | 50 53 56 59 65
...
|
| | IMG tags must have an ALT attribute. | Section 508 1194.22 (a) WCAG2 A F65 | |
|
Add an ALT attribute describing each image, which screen readers read aloud.
Spacer images and purely decorative images should use ALT=''. | | |
| http://www.pktevents.co.uk/page4.html | | 50 53 56 59 65
...
|
| | OBJECT tags should contain alternative content. | Section 508 1194.22 (a) WCAG2 A 1.1.1 | |
|
Place alternative content inside the object tag, which is displayed when objects are disabled or unsupported. For example:
<object>Alternative text content</object> | | |
| http://www.pktevents.co.uk/ | | 56 67 |
| | 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://www.pktevents.co.uk/ | | 34 |
| http://www.pktevents.co.uk/page2.html | | 34 |
| http://www.pktevents.co.uk/page3.html | | 33 |
| http://www.pktevents.co.uk/page4.html | | 53 56 59 62 65
...
|
| This issue was found on another 1 pages.
The evaluation version is limited to showing issues on 4 pages.
| | |
| | This form control has no associated LABEL element. | WCAG2 A F68 Section 508 1194.22 (n) | |
|
Add a LABEL tag with the FOR attribute set to the ID of this control, or enclose the control in a LABEL tag. This allows screen readers to tell the user what each control does. | | |
| http://www.pktevents.co.uk/page6.html | | 67 71 75 79 83 |
| | 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://www.pktevents.co.uk/page6.html | | 83 |
| | Provide information about the general layout of a site using a site map or table of contents. | WCAG2 AA 2.4.5 | |
|
You should provide a link labeled 'Site Map' or 'Sitemap' or the equivalent in your language, on every page.
| | |
| http://www.pktevents.co.uk/ | | 1 |
| | This CSS style makes it difficult or impossible to see the dotted link focus outline. | WCAG2 AA F78 | |
|
Change the style to avoid obscuring the focus outline around A elements, which is used when tabbing through links. | | |
| http://www.pktevents.co.uk/ | | 14 |
| http://www.pktevents.co.uk/page2.html | | 14 |
| http://www.pktevents.co.uk/page3.html | | 14 |
| http://www.pktevents.co.uk/page4.html | | 14 |
| This issue was found on another 1 pages.
The evaluation version is limited to showing issues on 4 pages.
| | |
| | Use relative rather than absolute units in CSS property values. | WCAG2 AA 1.4.4 | |
|
Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit,
because it isn't relative the user's preferred font size.
Low-vision users often use the "large fonts" mode of Windows, which makes each pixel larger than usual.
This usually causes problems with pixel based layouts, which also perform badly on handheld
and widescreen displays. Percentage values "stretch" according to screen size and work on a large
range of display sizes. | | |
| http://www.pktevents.co.uk/ | | 17 |
| http://www.pktevents.co.uk/page2.html | | 17 |
| http://www.pktevents.co.uk/page3.html | | 17 |
| http://www.pktevents.co.uk/page4.html | | 17 |
| This issue was found on another 1 pages.
The evaluation version is limited to showing issues on 4 pages.
| | |
| 11 issues on 5 pages |
More Info