[Name of Site or Application]
As Required by 1 TAC 206 and 1 TAC 213
[Evaluator’s Department] [Month 20YY]

Executive Summary

Summarize the findings

Multipage Features

These are features that are present on every page and in most cases will be tested in detail on the first page and confirmed for consistency on a subset of pages.

Language Identification

Test method: Inspect the html element. At the top of the page right click and chose Inspect Element (IE or Chrome). Scan page for any content in another language. Inspect the containing element for an appropriate language attribute.

Expectations:

The html element contains a language attribute and the language specified matches the primary language of the page. (3.1.1 Language of Page)

Content in other languages has a properly defined language attribute on the containing element. (3.1.2 Language of Parts)

Findings:

Page Time Out

Test Method: Wait for the page to time out, this is usually discovered during detailed testing.

Expectation: (2.2.1 Timing Adjustable)

A warning is presented – and focused

A keyboard accessible method for extending the timeout is present

CAPTCHA

Test Method: Identify all methods available to complete a CAPTCHA

Expectation: Methods exist to complete the CAPTCHA using different sense and modalities. (1.1.1 Non-Text Content)

Findings:

Header

Logo

Test Method: Code inspection, use a tool that reveals the alt text

Expectations: (1.1.1 Non-Text Content)

The alternative text will include the text in the logo and identify the entity that owns the site.

Findings:

Search Form

Expectations:

Labelled “Search” or equivalent

Label is persistent

No Keyboard Trap

Only activates on user action

Navigation

Skip Links

Test Method: Inspection and Manual Test

Determine the number of active elements before the start of the main content.

Go to the top of the page and press the tab key one time to place focus on the link

Use an inspection tool or activate the link to determine the destination of the skip link.

Expectations (2.4.1 Bypass Blocks)

If more than five active elements exist between the top of the page and the main content a skip link is present

The skip link is a text link (see contrast requirements)

The skip link is either always visible or becomes visible on focus

Activating the link places focus at the beginning of the main content area

Landmark Regions or Sectioning Markup

Test Method: Inspection

Use an inspection tool to determine landmark regions

Expectations (if landmark regions are used): (3.2.3 Consistent Navigation, 3.2.4 Consistent Identification)

Each region of the page has a landmark region that matches its purpose

Header/Banner (only one)

Search

Footer/ContentInfo (only one)

Nav/Navigation (If more than one each is distinctly identified)

Main/Main (only one)

Aside (If more than one each is distinctly identified)

When more than one instance of a section type is used it is identified using

Aria-labelledby pointing to a visible heading

Aria-label if the section does not begin with a heading

The number of sections has been minimized

Findings:

Navigation menus

Test Method: Inspection

Multi-level navigation menus

Test Method: Inspection/Manual

Use an inspection tool to determine role and state of menu items with submenus

Test manually with keyboard and with screen reader to determine if submenu only opens on user action

Test manually with screen reader to determine if state is conveyed correctly

Expectations:

Submenus can be skipped

The state of the submenu is conveyed using aria-expanded

Footer

Add features from the page level tests that are present in the footer.

[Page Title]

Page Title

Test method: Inspect the title element in the head of the document . Right Click and choose inspect element (IE or Chrome)

Expectation: The page title is unique for the page in the interface and accurately describes the purpose of the page. (2.4.2 Page Titled)

Findings:

Colors and Shapes

Color is not the only means of conveying meaning

Test method: Visually inspect the page

Expectations: If color is used for identification the same identification is available in text. (1.4.1 Use of Color)

Findings:

Shape, size or position are not the only means of conveying meaning

Test method: Visually inspect the page

Expectations: If controls or other elements are distinguished by shape or position then text is also used to provide the same identification. (1.3.3 Sensory Characteristics)

Findings:

Magnification Requirements

200% General Magnification

Test method: Increase browser magnification to 200%

Expectations: Using browser magnification the screen can be magnified to 200% without the loss of information or functionally. (1.4.4 Resize text)

Findings:

200% Text Magnification

Test method: Increase the text size to 200% (Firefox works best)

Expectations: Using the browsers functionality for increasing text size, the text can be magnified to 200% without the loss of information or functionality. (1.4.4 Resize text)

Findings:

Reading Order/Content

Test Method:

Disable CSS, Is the content presented in a logical fashion. (Note some content meant to be hidden may be displayed)

Screen Reader, Read from the beginning to the end of the page

Expectations:

The reading order is logical and understandable. Typically this will be left to right and top to bottom. (1.3.2 Meaningful Sequence)

All visible text is read by screen reader

Text that is meant to be hidden is hidden from the screen reader

Findings:

Text

Presentation

Test Method: Turn off images and determine if any informational text disappears

Expectations: Actual text is used unless there is no other way to present the needed styling than to use an image of text. (1.4.5 Images of Text)

Findings:

Foreground Text Contrast Ratio Against Background

Test Method: Use a contrast testing tool to determine contrast ratios.

Expectations: (1.4.3 Contrast Minimum)

The contrast ratio for all standard text on the page is equal to or greater than 4.5:1

The contrast ratio for large text (Headings and other large items) exceeds 3.0:1

The contrast ratio for images of text, other than logos and branding images, that are used to convey information exceeds 3.0:1

The contrast ratio for all text in active controls exceeds 4.5:1

Disabled controls do not have a contrast requirement.

Findings:

Headings

Test Method: Code and visual inspection

Expectations:

Headings are used to identify sections of the page. (1.3.1 Info and Relationships)

The heading text correctly identifies the content of the section or the page (2.4.6 Headings and Labels)

Heading nesting reflects the hierarchy of the content of the page (1.3.1 Info and Relationships)

Main topics are identified using <h1> (preferred)

Heading levels are not skipped (preferred)

Findings:

Lists

Test Method: Code and visual inspection

Expectations: (1.3.1 Info and Relationships)

Continuous lists are contained within a single list element (ol or ul)

List items use the li element

List nesting is correct (sublists are contained within an li)

Findings:

Images

Fail Safe

Test Method: Turn off images

Expectation: With images off (foreground or background) no loss of information or functionality occurs.

Descriptions

Test Method: Code inspection, use a tool that reveals the alt text

Expectations: (1.1.1 Non-Text Content)

If an image is used to provide context, information, or meaning then the alternative text for the image provides the same context, information or meaning. Otherwise the image is in the background or has a null alternative text.

If the image is a link or a control the alternative text provides the destination of the link or function of the control.

Images are not used to convey text-based information unless the presentation of text in an image format is essential.

Images used to convey text must meet text contrast requirements unless they are a logo.

Findings:

Tables

Test Method: Code inspection, use a tool that reveals header elements and scope

Expectations: (1.3.1 Info and Relationships), (1.3.2 Meaningful Sequence)

Tables are used for data presentation only (best practice)

If tables are used for layout they have aria-role=” presentation” (best practice)

If tables are used for layout then the reading order is correct when the table is linearized. (required)

Table headers are coded using table header elements.

If there is more than one row of column headers, then all column header cells include the scope attribute set to col scope=” col”

If there is more than one column of row headers, then all row header cells include the scope attribute set to row scope=” row”

If there are headers on the diagonal, then the headers are identified within each cell using the headers attribute. All header cells must have ids

If there is a spanning heading or caption for the entire table, it is not in a table row or coded as a header cell.

Findings:

Active Object Basics

Tab Order

Test Method: Inspection, use a tool that reveals the tab sequence and/or manually tab through the page. (2.4.3 Focus Order)

Expectations:

All active objects receive focus via when navigating using the tab key

No in-active objects receive focus (read-only form fields are considered active)

The order that objects receive focus is logical and matches the expected visual/mouse selected order.

Focus Indication

Test Method: Manually tab through active objects, check contrast levels where needed.

Expectations: (2.4.7 Focus Visible)

The visual indication of the focus location is clear

Outline or underline has contrast ratio of 4.5:1 against the background.

Color shift of the object has a contrast ratio between the two colors of 3.0:1

Behavior

Test Method: Manually tab through active objects

Expectations: (2.1.2 No Keyboard Trap, 3.2.1 On Focus)

Anything that can be entered with the tab key can be left using the tab key.

Entering or exiting and object does not cause focus location to change.

Links

Test Method: Inspection

Read the link text and the surrounding text,

Determine that links have been created using the anchor element with the href, if not,

tab to the link and press the enter key to activate links created using any other method.

Expectations: (2.4.4 Link Purpose In Context)

The link text describes the destination of the link (preferred)

The link text describes the destination of the link in context (required)

The link can be activated with the enter key

Findings:

Moving, Blinking, Flashing or Auto-Updating Information

Test Method: Inspection, Manual Testing, Testing with specialized tools

Expectations: (2.2.2 Pause Stop Hide, 2.3.1 Three Flashes or Below Threshold)

Nothing flashes more than three times per second (preferred) or

Flash area is small enough or

Threshold is tested with a tool

Harding FPA Web Site

Trace Center Photosensitive Epilepsy Tool Peat

There is a mechanism to pause or restart autoplaying, updating or moving content.

Findings:

Form Fields and Controls

Labeling and Instructions

Test Method: Inspection/Manual

Read the labels and Instructions

Place focus in the field and make an entry

Use an inspection tool to determine if the label is bound to the field

Use an inspection tool to determine if legends are used correctly and appropriately.

Use an inspection tool to determine if any aria attributes used for form labeling are used correctly

arial-labelledby includes pointers to all of the labels

aria-describedby points to additional instructional information like formatting or password requirements

aria-label is only used when a the text label would not be appropriate for a person using a screen reader (title may be preferred)

Expectations: (1.1.1 Non Text Content, 2.4.6 Headings and Labels, 1.3.1 Info and Relationships, 3.3.2 Labels or Instructions, )

The instructions and labels provide sufficient detail including any formatting requirements (this includes password rules) and whether the field is required.

All form fields and controls have a text label

Multiple form fields can share a text label

The text label clearly defines the purpose or function of the form field or control

The text label remains visible when the field is selected and when the field is completed.

All labels associated with a form field must be programmatically bound to the form field or an alternative label must be provided through the title attribute or the aria-label attribute.

Form fields that have a single unique text label must use the label element for the label with correct for and id attributes. (Warning)

When form fields have multiple labels the form fields are labeled using fieldset legends or aria-labelledby.

Formatting descriptions or other critical information to properly completing the form field are added using aria-describedby or included in the form field label.

Appropriate HTML 5 input types are used (Preferred)

Appropriate autocomplete attributes are used (Preferred, Required for 2.1)

See Input Purposes

Findings:

Error Messages

Test Method: Leave information out of required fields or enter information incorrectly and examine the error messages. Access the error messages visually and with a screen reader.

Expectations: (3.3.1 Error Identification, 3.3.3 Error Suggestion, 3.3.4 Error Prevention for Legal or Financial Data)

The error message accurately describes the error and indicates how to correct the problem.

The error message is easily discoverable for all users. Possible presentations are:

The error message is presented in a popup.

The error message is presented immediately adjacent to the error field and

Is bound to the field as part of the label, through aria-labelledby or through aria-describedby or

Is part of a live-region and announced as an alert

The error message is presented in a list of errors and keyboard focus is placed just before the beginning of the list.

If the input is part of a form that commits the user to a legal or financial obligation, then:

The submission is reversible or

The information can be checked for errors and the submitter is given the opportunity to correct any errors or

A means is available for the user to review, confirm and correct the information before final submission.

Findings:

Text Field Functionality

Test Method: Enter data in the field and exit the field. (Keyboard and Screen Reader)

Expectations:

The text entered has sufficient contrast.

If instructions or additional information appears when entering the field that information can be read with a screen reader, is visible when magnified.

Entering data or leaving the field does not cause an unexpected action.

Radio Button Functionality

Test Method: Select radio buttons using the keyboard and screen reader

Expectations

When tabbing only the selected radio button or the first radio button will be in the tab ring.

After selecting a radio button the selection can be changed using the arrow keys

Selecting a radio button or making a selection does not cause a unexpected change in focus location or in the interface.

Dropdown Field Functionality

Test Method: Make selections in the drop down using the keyboard and screen reader

Expectations:

Changing selections without opening the field does not result in a change in focus location or changes in the interface.

Selections can be made using the up and down arrow.

The control can be opened using alt+down arrow

Button Functionality

Test Method: Operate the button with the keyboard and screen reader.

Expectations:

Buttons can be activated using the space bar

Buttons can be activated using the enter key

Scripted Controls

Criteria for scripted controls must be reviewed for each project. In most cases the requirements can be derived from the design patterns and examples in WAI-ARIA Authoring Practices 1.1