| Agency issues beyond the test process |
Removed “use of Heading tags for style instead of structure, and using both an ALT and a TITLE attribute on an image where the two clearly contradict each other” as example of coding error; Added last bullet starting with “The baseline test methodology does not include guidance on managing a testing program. …” |
| Platforms, Browsers and Tools |
Removed support for IE8; IE9, Added support for Windows 10; Added WAT 2015 to tools list; Added information on WAF and Color Contrast Analyser. Added content on the use of WAF, Chrome, and Firefox. Added “Notes on Browsers Differences” and “Notes on WAF”. |
| Various Sections |
Added “Note: In Chrome, Inspect does not reveal the correct information for Flash content” and the note “Interactive Flash and embedded Java content should be tested in IE to determine the accessibility of the coded content” |
| Section 5, Skip Links |
Rationale: Changed title to “Repetitive Content;” changed “To enable equitable use by keyboard only users, there must be a method to skip past repetitive content. This can be provided by adding internal links to bypass repetitive content. Similarly, for screen reader users, if they must read content that is repeated on each page and cannot skip past it, their experience on the page can be very frustrating” to “To enable equitable use by keyboard only users, there must be a method to skip past repetitive content. Similarly, for screen reader users, if they must read content that is repeated on each page and cannot skip past it, their experience on the page can be very frustrating. A common method used to bypass repetitive content is internal (same page) links.” Test Instruction 2: Added various instructions: location of skip target, testing if no skip links are marked, testing skip function, testing if no interactive target. |
| Section 7, Images |
Rationale: Added “If font-based graphics are used to provide information, equivalent information must be provided in an accessible format;” Test Instruction 1: Step a, added bullet: “Look for images that are rendered by using font-based graphics (e.g. up-arrows to indicate sort order, etc.).” |
| Section 8, Color (meaning) |
Advisory: added bullet “WAF’s Greyscale test works in more cases than WAT’s, although there may be some sites where both work only partially or not at all.” |
| Section 9, Color (Contrast) |
Added “minimum” to “There must be contrasting colors/shades at a minimum ratio of 4.5:1 for discerning between background and foreground content.” |
| Section 11, Forms (associated instructions) |
Test Instruction 2: Added “Forms with ARIA labels should be tested in Chrome or Firefox to determine the accessibility of the coded forms.” |
| Section 23, Frames |
Advisory: Repeated content from “Notes on Using WAF” as relates to frames |
| Section 28, Built-in accessibility features |
Rationale: Added Windows 10; Test Instruction 1b: Added Windows 10; Test Instruction 2b: Replaced “Open any text editing application (e.g., MS Word). Attempt to close an edited 2.0file without saving it first. The Sound Sentry indicator should flash” with instructions for Notepad, since previous test did not work reliably in different environments. |
| Throughout |
Removed some references to page numbers and replaced them with references to section names |