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 | Section 508 - 2000 | 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
3 issues on 9 pages | |
| | Each A element must contain text or an IMG with an ALT attribute. | WCAG 2.0 A F89 Section 508 (2017) A F89 | 1 pages |
|
Add text to the link, or ALT text if the link contains an image. If there is no link text or the ALT text is blank, screen readers have nothing to read, so read out the URL instead. | | |
| http://ngebom.com/ | Line 204 653 | |
| | No TITLE attributes found for the frames on these pages. | Section 508 (2000) 1194.22 (i) WCAG 2.0 A 2.4.1 Section 508 (2017) A 2.4.1 | 6 pages |
|
Add a TITLE attribute to each FRAME and IFRAME element (e.g. TITLE="Main Content"). Without a TITLE some screen readers read out the FRAME filename, which is usually meaningless.
IFRAMEs with no title cause problems in:
- JAWS 14 and 15 with Firefox (the frame SRC filename is read instead)
- VoiceOver on OSX 10.9 (a meaningless title like "Frame twelve" is read out)
| | |
| http://ngebom.com/cara-order/ | Line 221 | |
| http://ngebom.com/ketentuan/ | Line 276 | |
| http://ngebom.com/portofolio/ | Line 232 | |
| http://ngebom.com/tentang-kami/ | Line 245 | |
| This issue was found on another 2 pages.
The trial version is limited to showing issues on 4 pages.
| | |
| | This page has markup errors, causing screen readers to miss content. | WCAG 2.0 A F70 Section 508 (2017) A F70 | 3 pages |
|
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://ngebom.com/ | Line 204 | |
| http://ngebom.com/layanan-jasa-optimasi-seo/ | Line 149 | |
| http://ngebom.com/paket/ | Line 122 | |
Level AA
2 issues on 9 pages | |
| | Ensure that foreground and background colors have enough contrast. | WCAG 2.0 AA 1.4.3 Section 508 (2017) AA 1.4.3 | 1 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
| | |
| The foreground to background color contrast ratio is: 3.2 with
color: rgb(255, 59, 0);
background-color: rgb(244, 244, 244);
font-size: 10.5pt;
font-weight: 400 3.2 with
color: rgb(255, 59, 0);
background-color: rgb(244, 244, 244);
font-size: 10.5pt;
font-weight: 400 3.2 with
color: rgb(255, 59, 0);
background-color: rgb(244, 244, 244);
font-size: 10.5pt;
font-weight: 400
http://ngebom.com/ | Line 669 673 677 | |
| | If you set any of the colors on the BODY or A elements you must set all of them. | WCAG 2.0 AA F24 Section 508 (2017) AA F24 | 9 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. | | |
| http://ngebom.com/ | Line 44 | |
| http://ngebom.com/layanan-jasa-optimasi-seo/ | Line 44 | |
| http://ngebom.com/paket/ | Line 44 | |
| http://ngebom.com/tentang-kami/ | Line 42 | |
| This issue was found on another 5 pages.
The trial version is limited to showing issues on 4 pages.
| | |
| Expand all 5 issues | | |