{"id":1345,"date":"2018-04-27T14:29:09","date_gmt":"2018-04-27T14:29:09","guid":{"rendered":"http:\/\/pressbooks.library.ryerson.ca\/pwaa\/?post_type=chapter&p=1345"},"modified":"2022-12-16T16:16:47","modified_gmt":"2022-12-16T16:16:47","slug":"tab-key-navigation-test","status":"publish","type":"chapter","link":"https:\/\/pressbooks.library.torontomu.ca\/pwaa\/chapter\/tab-key-navigation-test\/","title":{"raw":"Tab Key Navigation Test","rendered":"Tab Key Navigation Test"},"content":{"raw":"The Tab Key Navigation test is often used with the \u201cSelect All\u201d test (discussed on the next page) to confirm whether items that were not selected are keyboard operable, but this test can also be used on its own. Place the cursor at the very start of the HTML content (sometimes tricky), or in the browser\u2019s location field or address bar, then press the Tab key repeatedly and watch as the cursor moves through the content of the page. Make the following observations:\r\n
    \r\n \t
  1. Are you able to see the cursor\u2019s area of focus as you move through elements of the page? If not, this will violate Guideline 2.4.7 Focus Visible (Level AA). When reporting on the issue, recommend adding a focus indicator so it is possible to visually follow the cursor as it moves through the page.<\/li>\r\n \t
  2. As you navigate with the Tab key through elements on the page, do all functional elements such as links, buttons or forms receive focus? If not, those elements that do not receive focus are going to be inaccessible to some people, violating Guideline 2.1.1 Keyboard (Level A).<\/li>\r\n<\/ol>\r\n
    \r\n\r\nTechnical:\u00a0<\/strong>These elements are often custom features built with non-standard HTML and JavaScript. In such cases you can recommend the use of standard HTML where possible or suggest the developer add keyboard focus for the element by adding tabindex=\"0\"<\/code> to the HTML, and add keyboard events, in addition to the existing mouse events, to the programming that controls the functionality of the feature.\r\n\r\n<\/div>\r\n
      \r\n \t
    1. When navigating with the Tab key through elements of the page, is the path followed through these elements the standard left to right, top to bottom sequence? If the cursor\u2019s focus jumps around, moving to places on the page outside where you might logically expect the cursor to go by viewing the layout of elements on the page, it may violate Guideline 2.4.3 Focus Order (Level A). By default the focus order will be standard, so in cases where the order is irregular, it is because the developer has purposely changed the order. You may recommend removing the irregular tab sequence or adjusting it to follow a more meaningful path.<\/li>\r\n \t
    2. While navigating with the Tab key through menus, and other features that one can operate with a mouse, do these features also operate with a keyboard? If they do not, they will be inaccessible to those who use only a keyboard to move through web content. In the figure below, the submenus that drop down when one of the main navigation elements is clicked cannot be opened with a keypress. These types of menus may use the arrow keys to open and navigate through submenus, or they may operate using the Tab key. Arrow keys are preferred, though Tab key navigation will satisfy the success criteria associated with keyboard operability.<\/li>\r\n<\/ol>\r\nFor drop down menus like those described in #4 above, also watch for Tab key navigation moving through the items in the submenus, but the submenus not visibly opening. This will be confusing for low vision keyboard users who are following the focus indicator to keep track of where they are within the page.\r\n\r\n \r\n\r\n\"pointing\r\n\r\nFigure: Scenario in which the menus only function with a mouse click (see Lulu's Lollipops<\/a>)<\/strong>","rendered":"

      The Tab Key Navigation test is often used with the \u201cSelect All\u201d test (discussed on the next page) to confirm whether items that were not selected are keyboard operable, but this test can also be used on its own. Place the cursor at the very start of the HTML content (sometimes tricky), or in the browser\u2019s location field or address bar, then press the Tab key repeatedly and watch as the cursor moves through the content of the page. Make the following observations:<\/p>\n

        \n
      1. Are you able to see the cursor\u2019s area of focus as you move through elements of the page? If not, this will violate Guideline 2.4.7 Focus Visible (Level AA). When reporting on the issue, recommend adding a focus indicator so it is possible to visually follow the cursor as it moves through the page.<\/li>\n
      2. As you navigate with the Tab key through elements on the page, do all functional elements such as links, buttons or forms receive focus? If not, those elements that do not receive focus are going to be inaccessible to some people, violating Guideline 2.1.1 Keyboard (Level A).<\/li>\n<\/ol>\n
        \n

        Technical:\u00a0<\/strong>These elements are often custom features built with non-standard HTML and JavaScript. In such cases you can recommend the use of standard HTML where possible or suggest the developer add keyboard focus for the element by adding tabindex=\"0\"<\/code> to the HTML, and add keyboard events, in addition to the existing mouse events, to the programming that controls the functionality of the feature.<\/p>\n<\/div>\n

          \n
        1. When navigating with the Tab key through elements of the page, is the path followed through these elements the standard left to right, top to bottom sequence? If the cursor\u2019s focus jumps around, moving to places on the page outside where you might logically expect the cursor to go by viewing the layout of elements on the page, it may violate Guideline 2.4.3 Focus Order (Level A). By default the focus order will be standard, so in cases where the order is irregular, it is because the developer has purposely changed the order. You may recommend removing the irregular tab sequence or adjusting it to follow a more meaningful path.<\/li>\n
        2. While navigating with the Tab key through menus, and other features that one can operate with a mouse, do these features also operate with a keyboard? If they do not, they will be inaccessible to those who use only a keyboard to move through web content. In the figure below, the submenus that drop down when one of the main navigation elements is clicked cannot be opened with a keypress. These types of menus may use the arrow keys to open and navigate through submenus, or they may operate using the Tab key. Arrow keys are preferred, though Tab key navigation will satisfy the success criteria associated with keyboard operability.<\/li>\n<\/ol>\n

          For drop down menus like those described in #4 above, also watch for Tab key navigation moving through the items in the submenus, but the submenus not visibly opening. This will be confusing for low vision keyboard users who are following the focus indicator to keep track of where they are within the page.<\/p>\n

           <\/p>\n

          \"pointing<\/p>\n

          Figure: Scenario in which the menus only function with a mouse click (see Lulu’s Lollipops<\/a>)<\/strong><\/p>\n","protected":false},"author":56,"menu_order":3,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-1345","chapter","type-chapter","status-publish","hentry"],"part":1337,"_links":{"self":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/pwaa\/wp-json\/pressbooks\/v2\/chapters\/1345","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/pwaa\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/pwaa\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/pwaa\/wp-json\/wp\/v2\/users\/56"}],"version-history":[{"count":9,"href":"https:\/\/pressbooks.library.torontomu.ca\/pwaa\/wp-json\/pressbooks\/v2\/chapters\/1345\/revisions"}],"predecessor-version":[{"id":2568,"href":"https:\/\/pressbooks.library.torontomu.ca\/pwaa\/wp-json\/pressbooks\/v2\/chapters\/1345\/revisions\/2568"}],"part":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/pwaa\/wp-json\/pressbooks\/v2\/parts\/1337"}],"metadata":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/pwaa\/wp-json\/pressbooks\/v2\/chapters\/1345\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/pressbooks.library.torontomu.ca\/pwaa\/wp-json\/wp\/v2\/media?parent=1345"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/pwaa\/wp-json\/pressbooks\/v2\/chapter-type?post=1345"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/pwaa\/wp-json\/wp\/v2\/contributor?post=1345"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/pressbooks.library.torontomu.ca\/pwaa\/wp-json\/wp\/v2\/license?post=1345"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}