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 |
|---|
 | Document title must not be blank. | WCAG2 A F25 | |
|
For HTML pages change the TITLE tag. For Office documents and PDF documents produced from Office, fill in the Title in Document Properties before saving as PDF. | | |
| http://www.xmedia.in/wp-content/uploads/pdf/xmedia_solutions_profile.pdf | | 1 |
| | Each A tag must contain text or an IMG with an ALT tag. | 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.xmedia.in/ | | 550 634 721 1038 1039
...
|
| http://www.xmedia.in/blog/ | | 102 236 264 291 319
...
|
| http://www.xmedia.in/company | | 1411 2048 2049 2059 2060 |
| http://www.xmedia.in/site-map | | 1411 1923 1924 1934 1935 |
| This issue was found on another 3 pages.
The evaluation version is limited to showing issues on 4 pages.
| | |
| | IFRAME tags must have alternative content. | Section 508 1194.22 (a) | |
|
To cater for screen readers that don't support frames, place some text in the IFRAME tag.
For example:
<iframe src='file.htm'>Alternative content</iframe> | | |
| http://www.xmedia.in/blog/ | | 252 280 307 335 362
...
|
| | 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.xmedia.in/blog/ | | 98 |
| http://www.xmedia.in/company | | 1643 1745 |
| | LABEL elements should be not be blank. | WCAG2 A 4.1.2 | |
|
Add text to the LABEL describing the associated control. | | |
| http://www.xmedia.in/company | | 1699 |
| http://www.xmedia.in/services/web-design | | 1652 |
| http://www.xmedia.in/services/web-design/static-website-design | | 1671 |
| | No TITLE attributes found for the frames on these pages. | Section 508 1194.22 (i) WCAG2 A 2.4.1 | |
|
Add a TITLE attribute to each FRAME and IFRAME element (e.g. TITLE="Main Content"). Screen readers read out the TITLE letting the user decide which frame to visit. | | |
| http://www.xmedia.in/blog/ | | 252 280 307 335 362
...
|
| | PDFs must be tagged to be accessible by screen readers. | Section 508 1194.22 (a) WCAG2 A 1.3.1 | |
|
Enable the "Document structure tags" option in Word, or the "Tagged PDF" option in OpenOffice when exporting, or use the "Make Accessible" plug-in for Adobe Acrobat. | | |
| http://www.xmedia.in/wp-content/uploads/pdf/xmedia_solutions_profile.pdf | | 1 |
| | 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.xmedia.in/site-map | | 1575 1618 1619 1620 1633
...
|
| | This form control has no associated LABEL element. Affects NVDA 2011, Voiceover on OSX 10.6. | WCAG2 A F68 Section 508 1194.22 (n) | |
|
Add a LABEL tag with the FOR attribute set to the ID of this control. This allows screen readers to tell the user what each control does.
Do not wrap LABEL tags around input controls (implicit labels) since this is very unreliable in older screen readers. | | |
| Safari on OSX 10.6 and earlier ignores implicit labels. NVDA 2011 and earlier reads implicit labels twice.
http://www.xmedia.in/company | | 1663 1671 1679 1687 |
| Safari on OSX 10.6 and earlier ignores implicit labels. NVDA 2011 and earlier reads implicit labels twice.
http://www.xmedia.in/services/web-design | | 1610 1618 1626 1634 |
| Safari on OSX 10.6 and earlier ignores implicit labels. NVDA 2011 and earlier reads implicit labels twice.
http://www.xmedia.in/services/web-design/static-website-design | | 1629 1637 1645 1653 |
| | 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.xmedia.in/company | | 1663 1671 1679 1687 |
| http://www.xmedia.in/services/web-design | | 1610 1618 1626 1634 |
| http://www.xmedia.in/services/web-design/static-website-design | | 1629 1637 1645 1653 |
| | This page has duplicate IDs which cause problems in screen readers. | WCAG2 A F77 | |
|
Two or more tags on this page share the same ID. Change the ID so it is unique for each tag. | | |
| http://www.xmedia.in/company | | 1679 |
| http://www.xmedia.in/services | | 1609 |
| http://www.xmedia.in/services/web-design | | 1626 |
| http://www.xmedia.in/site-map | | 1672 |
| This issue was found on another 1 pages.
The evaluation version is limited to showing issues on 4 pages.
| | |
| | This page has links to a PDF file, but does not provide a link to download Acrobat Reader. | Section 508 1194.22 (m) | |
|
You should include a link to download Acrobat Reader.
When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with S1194.21(a) through (l). | | |
| http://www.xmedia.in/ | | 466 |
| http://www.xmedia.in/company | | 1275 |
| http://www.xmedia.in/services | | 1275 |
| http://www.xmedia.in/site-map | | 1275 |
| This issue was found on another 2 pages.
The evaluation version is limited to showing issues on 4 pages.
| | |
| | This page has markup errors, causing screen readers to miss content. | WCAG2 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://www.xmedia.in/ | | 950 954 961 1027 1068
...
|
| http://www.xmedia.in/blog/ | | 204 485 |
| http://www.xmedia.in/company | | 899 1501 1573 1596 1979
...
|
| http://www.xmedia.in/site-map | | 1501 1641 1647 1854 1912
...
|
| This issue was found on another 3 pages.
The evaluation version is limited to showing issues on 4 pages.
| | |
| | Use HTML headings tags instead of applying CSS heading styles to non-headings. | WCAG2 A F2 | |
|
Change the element to an appropriate header element (H1, H2, H3, etc) and apply CSS styles if necessary. | | |
| http://www.xmedia.in/ | | 754 760 764 |
| | Use the LANG attribute to identify the language of the page. | WCAG2 A 3.1.1 | |
|
In HTML add a LANG attribute to the HTML tag, and in PDF set the language using Document Properties in Acrobat. This allows screen readers to pronounce words correctly. | | |
| http://www.xmedia.in/wp-content/uploads/pdf/xmedia_solutions_profile.pdf | | 1 |
| | Headings should not be empty. | WCAG2 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://www.xmedia.in/ | | 652 661 670 |
| | 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.xmedia.in/ | | 46 |
| http://www.xmedia.in/company | | 187 |
| http://www.xmedia.in/services | | 187 |
| http://www.xmedia.in/site-map | | 187 |
| This issue was found on another 2 pages.
The evaluation version is limited to showing issues on 4 pages.
| | |
| 17 issues on 8 pages |
More Info