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 | Description and URL | Guideline and Line# | Count |
|---|
Level A
11 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 | 8 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://www.nytimes.com/pages/todayspaper/index.html | Line 225 1899 | |
| https://www.nytimes.com/ | Line 2392 2476 2907 3119 3143
...
| |
| https://www.nytimes.com/es/ | Line 343 394 448 499 | |
| https://www.nytimes.com/video | Line 1451 1523 1595 1667 1813
...
| |
| This issue was found on another 4 pages.
The trial version is limited to showing issues on 4 pages.
| | |
| | Frame titles must not be the same as the frame file name. | Section 508 (2000) 1194.22 (i) WCAG 2.0 A 2.4.1 Section 508 (2017) A 2.4.1 | 2 pages |
|
Change the TITLE text to a short description of the frame content.
IFRAMEs using a filename as a title cause problems in:
- NVDA 2016.2 with Firefox 48 (the filename is read, which usually sounds like gibberish)
- NVDA 2016.2 with IE 11 (the filename is read, which usually sounds like gibberish)
- JAWS 17 with Firefox 48 (the filename is read, which usually sounds like gibberish)
- WindowEyes 9.2 with IE 11 (the filename is read, which usually sounds like gibberish)
- VoiceOver with Safari Mac 9.1.2 (the filename is read, which usually sounds like gibberish)
| | |
| https://www.nytimes.com/section/nyregion | Line 1102 | |
| https://www.nytimes.com/section/politics | Line 982 | |
| | IMG elements must have an ALT attribute. | Section 508 (2000) 1194.22 (a) WCAG 2.0 A F65 Section 508 (2017) A F65 | 4 pages |
|
Add an ALT attribute describing each image, which screen readers read aloud.
Spacer images and purely decorative images should use ALT=''. Impact on users: - NVDA 2015.2 FF40 Windows 7 Reading: Image ignored.
- JAWS 16.0.4350 FF40 Windows 7 Reading: Image ignored.
- WindowEyes 8.4 IE11 Windows 7 Reading: Image ignored.
- VoiceOver Safari OSX 10.10 Reading: Image filename read out.
- VoiceOver Safari iOS 7.1 Touch: Image filename read out.
- SaToGo 3.4.96.0 IE11 Windows 7 Reading: Image ignored.
| | |
| http://www.nytimes.com/pages/todayspaper/index.html | Line 166 | |
| https://www.nytimes.com/ | Line 1203 2869 2883 2897 2907 | |
| https://www.nytimes.com/content/help/site/ie9-support.html | Line 202 | |
| https://www.nytimes.com/video | Line 377 | |
| | INPUT TYPE=IMAGE elements must have a descriptive ALT attribute. | Section 508 (2000) 1194.22 (a) WCAG 2.0 A F65 Section 508 (2017) A F65 | 1 pages |
|
Add an ALT attribute describing the button action, which screen readers read aloud. Impact on users: - NVDA 2015.2 FF40 Windows 7 Reading: Reads "button" without saying what button does.
- NVDA 2015.2 IE11 Windows 7 Reading: Reads "button" without saying what button does.
- JAWS 16.0.4350 FF40 Windows 7 Reading: Reads image filename without saying what button does.
- JAWS 16.0.4350 IE11 Windows 7 Reading: Reads image filename without saying what button does.
- JAWS 15.0.9023 FF28 Windows 7 Reading: Reads image filename without saying what button does.
- JAWS 15.0.9023 IE11 Windows 7 Reading: Reads image filename without saying what button does.
- WindowEyes 8.4 IE11 Windows 7 Reading: Reads image pathname without saying what button does.
- WindowEyes 8.4 IE11 Windows 7 Tabbing: Reads previous heading as button label.
- VoiceOver Safari OSX 10.10 Reading: Reads "submit" as button label without saying what button does.
- VoiceOver Safari iOS 7.1 Touch: Reads image filename without saying what button does.
- SaToGo 3.4.96.0 IE11 Windows 7 Reading: Reads "button" without saying what button does.
| | |
| https://www.nytimes.com/content/help/site/ie9-support.html | Line 130 | |
| | 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 | 1 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)
| | |
| https://www.nytimes.com/ | Line 55 | |
| | Provide a way to skip repetitive navigation links. | Section 508 (2000) 1194.22 (o) | 1 pages |
|
Without skip links, keyboard users must tab through the navigation links to get to page content.
Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users.
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>
| | |
| https://www.nytimes.com/video | Line 707 780 853 926 1063
...
| |
| | This form control has no programmatically determined name. | WCAG 2.0 A F68 Section 508 (2017) A F68 Section 508 (2000) 1194.22 (n) | 1 pages |
|
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 a TITLE attribute
- Add an ARIA-LABELLEDBY attribute (not supported in all screen readers)
- Add an ARIA-LABEL attribute (not supported in all screen readers)
| | |
| https://www.nytimes.com/es/ | Line 1736 | |
| | This page has duplicate IDs which cause problems in screen readers. | WCAG 2.0 A F77 Section 508 (2017) A F77 | 4 pages |
|
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://www.nytimes.com/pages/todayspaper/index.html | Line 519 | |
| https://www.nytimes.com/ | Line 1005 | |
| https://www.nytimes.com/es/ | Line 761 | |
| https://www.nytimes.com/section/world | Line 1723 | |
| | This page has markup errors, causing screen readers to miss content. | WCAG 2.0 A F70 Section 508 (2017) A F70 | 7 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://www.nytimes.com/pages/todayspaper/index.html | Line 519 | |
| https://www.nytimes.com/ | Line 1005 | |
| https://www.nytimes.com/es/ | Line 749 761 | |
| https://www.nytimes.com/video | Line 251 2321 | |
| This issue was found on another 3 pages.
The trial version is limited to showing issues on 4 pages.
| | |
| | Use the LANG attribute to identify the language of the page. | WCAG 2.0 A 3.1.1 Section 508 (2017) A 3.1.1 | 1 pages |
|
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. | | |
| https://www.nytimes.com/video | Line 7 | |
| | Using ALT text which duplicates link text in the same link or the following link results in screen readers stuttering as the same text is read out twice. | WCAG 2.0 A H2 Section 508 (2017) A H2 | 1 pages |
|
Use ALT='' when the image is part of a link containing text, or change the redundant ALT text if the links are separate. | | |
| https://www.nytimes.com/es/ | Line 315 366 420 471 | |
Level AA
4 issues on 8 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 255, 255, 255 foreground color to 98, 136, 165 background color
contrast ratio is 3.70000004768372 with
10.5 point text.
https://www.nytimes.com/ | Line 808 5238 5246 5247 5254
...
| |
| | Form field labels should be unique on a page, or enclosed in a FIELDSET with a LEGEND that makes the label unique. | WCAG 2.0 AA 2.4.6 Section 508 (2017) AA 2.4.6 | 1 pages |
|
When a form contains items with the same label, screen reader users find it difficult to tell them apart.
Adding a fieldset with a legend differentiates the controls, because the legend text is announced along
with the label text. For example:
<legend> Gift wrapped: </legend>
<label> Yes </label>
<label> No </label>
<legend> Express delivery: </legend>
<label> Yes </label>
<label> No </label>
| | |
| Label used: "enter keyword or date"
http://www.nytimes.com/pages/todayspaper/index.html | Line 521 521 1862 1862 | |
| | Headings should not be empty. | WCAG 2.0 AA G130 Section 508 (2017) AA G130 | 7 pages |
|
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. Impact on users: - SaToGo 3.4.96.0 IE11 Windows 7 Heading: Reads following paragraph as heading.
| | |
| https://www.nytimes.com/ | Line 2812 2863 | |
| https://www.nytimes.com/es/ | Line 1762 | |
| https://www.nytimes.com/section/world | Line 308 | |
| https://www.nytimes.com/video | Line 433 509 | |
| This issue was found on another 3 pages.
The trial version is limited to showing issues on 4 pages.
| | |
| | Use relative rather than absolute units in CSS property values. | WCAG 2.0 AA 1.4.4 Section 508 (2017) AA 1.4.4 | 6 pages |
|
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, and a lot of people over 50, increase the browser default font size to make text
easier to read. Absolute units ignore this user choice.
Relative units like EM and percentages "stretch" according to the screen size and/or
user's preferred font size, and work on a large range of devices. | | |
| https://www.nytimes.com/ | Line 693 702 767 775 899
...
| |
| https://www.nytimes.com/es/ | Line 111 | |
| https://www.nytimes.com/section/us | Line 162 | |
| https://www.nytimes.com/section/world | Line 162 | |
| This issue was found on another 2 pages.
The trial version is limited to showing issues on 4 pages.
| | |
| Expand all 15 issues | | |