How toManually test a web page

Helpful Guides


Complete each of the following tests for every web page

Manual testing

  • Keyboard navigation

    Keyboard access and control must be available for all interactive interface components and frames that can be accessed or controlled with a mouse. Where non-standard keyboard commands are employed, notify users of the existence and use of Alternate keyboard commands through the interface, application help, and/or documentation.

    Back to top

  • Focus (visible)

    There must be a visible indication of the currently focused interactive component.

    Back to top

  • Focus (order)

    When the sequence of interface components has meaning or requires an order of operation, the focus/TAB order must logically flow with the application/content.

    Back to top

  • Focus (Revealing hidden content)

    Components that reveal hidden content (dialog boxes, light boxes, popups, content accordions, drop-down menus etc.) must either (i) shift focus to the content they reveal, or (ii) the component must describe that a change to the content will occur if selected.

    Back to top

  • Skip links

    A method must be provided to skip blocks of repeated content or links on pages, allowing a user to move directly to page-specific content.

    Back to top

  • Multi-state components

    Components that can change their state must reveal their current state and function to Assistive Technology.

    Back to top

  • Images

    All images must have associated text describing the content of the image. Some decorative images do not require a description.

    Back to top

  • Color (meaning)

    Color must not be the only means of conveying information, indicating an action, prompting a response, or indicating status. Information conveyed through color must also be provided in text displayed on the screen or by visual differentiation.

    Back to top

  • Color (contrast)

    There must be contrasting colors/shades at a ratio of 4.5:1 for discerning between background and foreground content.

    Back to top

  • Flashing (reserved)

    Sections(s) of the screen should not flash at or above 3Hz.

    Back to top

  • Forms (associated instructions)

    Labels, instructions, directions and cues necessary to complete a form must be programmatically associated with their respective input control.

    Back to top

  • Page Titles

    Every page must have one page title

    Back to top

  • Data Tables (headers)

    Column and row header cells of data tables must be programmatically identified.

    Tables should not have merged cells

    Back to top

  • Data Tables (cell-header association)

    Data cells on complex tables must include markup to associate the data cell with the correct header.

    Back to top

  • Headings

    1. There should only be one h1 per page
    2. Headings should not skip a level

    Back to top

  • Links


    1. Use unique, meaningful link names
    2. Link names should only be used once per page
    3. Link names should be only a few words long
    4. Links shouldn't only be indicated by color
    5. There should separate hover and visited link formats


    1. Don't use Click Here, Read More for link text
    2. Don't use the same link text for two different links
    3. Use button code on a link

    Back to top

  • Language

    A default language must be programmatically identified for each page, and for passages that use a language other than the default. Exceptions: proper names or technical terms.

    Back to top

  • Audio transcripts

    Audio-only content must be accompanied by transcripts.

    Back to top

  • Video (descriptions)

    Video-only content must be accompanied by descriptions.

    Back to top

  • Synchronized media (captions)

    Synchronized media must have captions that are time-synchronized with the dialog and relevant sounds.

    Back to top

  • Synchronized media (descriptions)

    Synchronized media must have audio descriptions that are time-synchronized with the video.

    Back to top

  • Style-sheet non-dependence

    Web pages must be structured so that their reading order is consistent whether they are viewed with or without an associated style sheet. Layout and appearance of the page may change visually, as long as the logical reading order is maintained.

    Back to top

  • Frames

    Frames and iframes must have a meaningful title

    Back to top

  • Alternate pages

    When the primary page/site cannot be made accessible, an alternative page or site must contain equivalent and up-to-date content.

    Back to top

  • Time outs

    Users of assistive technology must be alerted about a pending time out, and users must be able to request more time to complete their task.

    Back to top

  • Image maps

    Server-side image maps may not be used. Client-side image-maps must be used instead.

    Avoid image maps when possible

    Back to top

  • Plug-in links

    When pages use content delivered via plugins or contain downloadable content that must be opened with a separate application, a link to obtain the plug-in and/or application must be provided.

    Back to top

  • Built-in accessibility features

    Operating System (OS) user-configurable accessibility appearance settings and functions must not be disrupted or disabled by the software application.

    Back to top

  • Screen reader keyboard shortcuts and gestures

    Back to top

Related Topics