- From: WCAG 2.0 Techniques Submission Form <nobody@w3.org>
- Date: Mon, 25 Aug 2008 14:49:45 +0000 (GMT)
- To: public-wcag2-techs@w3.org
Submitter's Name: Treasury Board of Canada Secretariat (Common Look and Feel Office) Submitter's Email: clf-nsi@tbs-sct.gc.ca Technique ID: UNKNOWN Short Name: Opening new windows and tabs only when best from an accessibility perspective Technique Category: General Techniques Guideline Reference: consistent-behavior-receive-focus Success Criterion Reference: UNKNOWN Applicability: Applies to all technologies. Description: The objective of this technique is to identify from an accessibility perspective when it is acceptable to automatically open a new window or tab when a change of context is initiated by a user request. In general, new windows and tabs should not be opened automatically since they can be disorienting for people who have difficulty perceiving visual content. Although automatically opening a new window or tab can cause disorientation, it is best from an accessibility perspective to open a new window or tab in the following situations: 1. Opening a page containing context-sensitive information (such as help instructions) or an alternate means of completing a form (such as a calendar-based date picker) will significantly disrupt a multi-step workflow (such as filling in and submitting a form) if the page is opened in the same window or tab. 2. Opening a page outside of a secure session will prematurely break or destroy the secure session if the page is opened in the same window or tab. Example 1 Head: Example 1 Example 1 Description: An online form provides extensive context-sensitive help for each form field on a separate page because there is too much text to include within the form. The links to the context-sensitive help open in new windows or tabs to prevent the loss of any form data that has already been entered. Example 2 Head: Example 2 Example 2 Description: A page on a secure Web site includes a link to an external page that is outside of the secure session. The link opens in a new window or tab since opening the link in the same window will break or destroy the secure session. Resource 1 Title: Beware of opening links in a new window (Webcredible) Resource 1 URI: http://www.webcredible.co.uk/user-friendly-resources/web-usability/new-browser-windows.shtml Resource 2 Title: Day 16: Not opening new windows (Dive Into Accessibility) Resource 2 URI: http://diveintoaccessibility.org/day_16_not_opening_new_windows.html Related Techniques: H83 SCR24 Test Procedure: For each page that opens automatically in a new window or tab when a change of context is initiated by a user request: 1. Check that the new page contains context-sensitive information (such as help instructions) or an alternate means of completing a form (such as a calendar-based date picker) and that opening the page in the same window or tab will significantly disrupt a multi-step workflow (such as filling in and submitting a form). 2. Check that a secure session exists and that opening the new page in the same window or tab will prematurely break or destroy the secure session. Expected Result: One of the above checks is true. Additional Notes: Applies to both Success Criterion 3.2.1 and Success Criterion 3.2.5. Additional examples: 1) Example 3: An online form includes a date field that allows the user to manually type in the date or select a date from a calendar-based date picker on a separate page. The link to the calendar-based date picker opens in a new window or tab to prevent the loss of any form data that has already been entered. 2) Failure Example 1: A non-secure page includes links to pages that are external to the Web site where those links open in new windows or tabs even though opening the pages in the same window or tab would not significantly disrupt a multi-step workflow and would not break or destroy a secure session. 3) Failure Example 2: A search results page includes links which open in new windows or tabs to prevent the results from being lost even though users can manually open a new window or tab, or can otherwise use the browser back button. In addition, opening the links in the same window or tab would not significantly disrupt a multi-step workflow and would not break or destroy a secure session. 4) Failure Example 3: A page includes links which open in new windows or tabs to prevent users from leaving the current Web page even though users can manually open a new window or tab should they want to keep the current page open. In addition, opening the links in the same window or tab would not significantly disrupt a multi-step workflow and would not break or destroy a secure session. 5) Failure Example 4: A page includes links to non-Web (non-W3C) documents, full-size versions of thumbnail images or oversized graphics, or printable versions of pages that open in new windows even though opening the links in the same window or tab would not significantly disrupt a multi-step workflow and would not break or destroy a secure session. 6) Failure Example 5: A page includes a form button that opens a new window or tab when activated even though opening the new page in the same window or tab would not significantly disrupt a multi-step workflow and would not break or destroy a secure session. Additional Resource: 1) Top-10 New Mistakes of Web Design (Jakob Nielsen’s Alertbox): http://www.useit.com/alertbox/990530.html Additional Related Technique: 1) GXXX: Giving users advanced warning when opening a new window (once it has been written) No UA issues were submitted! No test file 1 was submitted! No test file 1 pass/fail was submitted! No test file 2 was submitted! No test file 2 pass/fail was submitted! ------------------------------------------------ <technique id="UNKNOWN"> <short-name>Opening new windows and tabs only when best from an accessibility perspective</short-name> <applies-to> <guideline idref="consistent-behavior-receive-focus" /> <success-criterion idref="UNKNOWN" /> </applies-to> <applicability> Applies to all technologies. </applicability> <ua_issues> </ua_issues> <description> The objective of this technique is to identify from an accessibility perspective when it is acceptable to automatically open a new window or tab when a change of context is initiated by a user request. In general, new windows and tabs should not be opened automatically since they can be disorienting for people who have difficulty perceiving visual content. Although automatically opening a new window or tab can cause disorientation, it is best from an accessibility perspective to open a new window or tab in the following situations: 1. Opening a page containing context-sensitive information (such as help instructions) or an alternate means of completing a form (such as a calendar-based date picker) will significantly disrupt a multi-step workflow (such as filling in and submitting a form) if the page is opened in the same window or tab. 2. Opening a page outside of a secure session will prematurely break or destroy the secure session if the page is opened in the same window or tab. </description> <examples> <ex_head_1> Example 1 </ex_head_1> <ex_desc_1> An online form provides extensive context-sensitive help for each form field on a separate page because there is too much text to include within the form. The links to the context-sensitive help open in new windows or tabs to prevent the loss of any form data that has already been entered. </ex_desc_1> <ex_head_2> Example 2 </ex_head_2> <ex_desc_2> A page on a secure Web site includes a link to an external page that is outside of the secure session. The link opens in a new window or tab since opening the link in the same window will break or destroy the secure session. </ex_desc_2> </examples> <resources> <resources_title1> Beware of opening links in a new window (Webcredible) </resources_title1> <resource_uri1> http://www.webcredible.co.uk/user-friendly-resources/web-usability/new-browser-windows.shtml </resource_uri1> <resources_title2> Day 16: Not opening new windows (Dive Into Accessibility) </resources_title2> <resource_uri2> http://diveintoaccessibility.org/day_16_not_opening_new_windows.html </resource_uri2> </resources> <related_techniques> <related_technique> H83 </related_technique> <related_technique> SCR24 </related_technique> </related_techniques> <tests> <procedure> For each page that opens automatically in a new window or tab when a change of context is initiated by a user request: 1. Check that the new page contains context-sensitive information (such as help instructions) or an alternate means of completing a form (such as a calendar-based date picker) and that opening the page in the same window or tab will significantly disrupt a multi-step workflow (such as filling in and submitting a form). 2. Check that a secure session exists and that opening the new page in the same window or tab will prematurely break or destroy the secure session. </procedure> <expected_result> One of the above checks is true. </expected_result> <test_file_1> </test_file_1> <pass_fail_1> </pass_fail_1> <test_file_2> </test_file_2> <pass_fail_2> </pass_fail_2> </tests> </technique> Additional Notes: Applies to both Success Criterion 3.2.1 and Success Criterion 3.2.5. Additional examples: 1) Example 3: An online form includes a date field that allows the user to manually type in the date or select a date from a calendar-based date picker on a separate page. The link to the calendar-based date picker opens in a new window or tab to prevent the loss of any form data that has already been entered. 2) Failure Example 1: A non-secure page includes links to pages that are external to the Web site where those links open in new windows or tabs even though opening the pages in the same window or tab would not significantly disrupt a multi-step workflow and would not break or destroy a secure session. 3) Failure Example 2: A search results page includes links which open in new windows or tabs to prevent the results from being lost even though users can manually open a new window or tab, or can otherwise use the browser back button. In addition, opening the links in the same window or tab would not significantly disrupt a multi-step workflow and would not break or destroy a secure session. 4) Failure Example 3: A page includes links which open in new windows or tabs to prevent users from leaving the current Web page even though users can manually open a new window or tab should they want to keep the current page open. In addition, opening the links in the same window or tab would not significantly disrupt a multi-step workflow and would not break or destroy a secure session. 5) Failure Example 4: A page includes links to non-Web (non-W3C) documents, full-size versions of thumbnail images or oversized graphics, or printable versions of pages that open in new windows even though opening the links in the same window or tab would not significantly disrupt a multi-step workflow and would not break or destroy a secure session. 6) Failure Example 5: A page includes a form button that opens a new window or tab when activated even though opening the new page in the same window or tab would not significantly disrupt a multi-step workflow and would not break or destroy a secure session. Additional Resource: 1) Top-10 New Mistakes of Web Design (Jakob Nielsen’s Alertbox): http://www.useit.com/alertbox/990530.html Additional Related Technique: 1) GXXX: Giving users advanced warning when opening a new window (once it has been written)
Received on Monday, 25 August 2008 14:50:21 UTC