From 31169a68a773df1a614cf4bcfb875c6c498853dc Mon Sep 17 00:00:00 2001 From: Chris Loiselle <3275560+ChrisLoiselle@users.noreply.github.com> Date: Mon, 17 Apr 2023 09:10:02 -0400 Subject: [PATCH 01/13] consistent-navigation-ACT-Rule-proposal Consistent Navigation manual test rule proposal --- _rules/consistent_nav_ACT_Rule | 215 +++++++++++++++++++++++++++++++++ 1 file changed, 215 insertions(+) create mode 100644 _rules/consistent_nav_ACT_Rule diff --git a/_rules/consistent_nav_ACT_Rule b/_rules/consistent_nav_ACT_Rule new file mode 100644 index 0000000000..320e1336ff --- /dev/null +++ b/_rules/consistent_nav_ACT_Rule @@ -0,0 +1,215 @@ +--- +id: +name: +rule_type: atomic +description: | + This rule checks whether Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. + +accessibility_requirements: # Remove whatever is not applicable + wcag2.1: # Success Criterion 3.2.3 Consistent Navigatoin (AA) + forConformance: true | false + failed: not satisfied + passed: satisfied | further testing needed + inapplicable: satisfied | further testing needed + aria12:anchor-name: # + title: Title to display + forConformance: true | false + failed: not satisfied + passed: satisfied | further testing needed + inapplicable: satisfied | further testing needed + wcag-technique:Xxx: # + forConformance: false + failed: not satisfied + passed: satisfied | further testing needed + inapplicable: satisfied | further testing needed + using-aria:anchor-name: # + title: Title to display + forConformance: false + failed: not satisfied + passed: satisfied | further testing needed + inapplicable: satisfied | further testing needed +input_aspects: + - # (e.g. HTTP Messages, DOM Tree, CSS Styling, Accessibility Tree, Language, etc.,) +acknowledgments: + authors: + - # Chris Loiselle + +--- + +## Applicability + +This rule applies to any navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. + +Applies to all technologies. This technique relates to 3.2.3: Consistent Navigation (Failure). + + +## Expectation + +Navigational mechansisms that are repeated on multiple pages within a set of Web pages occur in the same relaative order each time they are repeated. + +## Assumptions + +"Same relative order" means that secondary navigation items may be in between the link items on some pages. They can be present without affecting the outcome of this test. + +## Accessibility Support + +There are no accessibility support issues known. + +## Background + +- (e.g. WCAG Techniques or links with background information mentioned in Applicability, Expectations or Assumptions) + +## Test Cases + +Procedure +Check to see if a navigation mechanism is being used on more than one Web page. +Check the default presentation of the navigation mechanism on each page to see if the list of links are in the same relative order on each Web page. +"Same relative order" means that secondary navigation items may be in between the link items on some pages. They can be present without affecting the outcome of this test. + +Expected Results +If #1 is true and #2 is false, then this failure condition applies and content fails the Success Criterion. + +### Passed + + +A search field is the last item on every Web page in a site. Users can quickly locate the search function. + +An expanding navigation menu + +A navigation menu includes a list of seven items with links to the main sections of a site. When a user selects one of these items, a list of sub-navigation items is inserted into the top-level navigation menu. + +Consistently positioned skip navigation controls + +A "skip navigation" (or "skip to main content") link is included as the first link on every page in a Web site. The link allows users to quickly bypass heading information and navigational content and begin interacting with the main content of a page. + +Skip to navigation link + +Navigational content is consistently located at the end of each page in a set of Web pages. A "skip to navigation" link is consistently located at the beginning of each page so that keyboard users can easily locate it when needed. + +#### Passed Example 1 + +A consistently located control. Presenting repeated components in the same relative order each time they appear. + + +Examples of a navigation mechanism that presents links in same order. + +Page 1 Menu + + +Page 2 Menu + + + +#### Passed Example 2 + +... + +### Failed + +#### Failed Example 1 + +##### Description + +This describes a failure condition for all techniques involving navigation mechanisms that are repeated on multiple Web pages within a set of Web pages (Success Criterion 3.2.3). If the mechanism presents the order of links in a different order on two or more pages, then the failure is triggered. + +Example 1: An XHTML menu presenting a series of links that are in a different relative order on two different pages +Examples of a navigation mechanism that presents links in a different order. + +Page 1 Menu + + +Page 2 Menu + + + +```html + +``` + +### Inapplicable + +#### Inapplicable Example 1 + +Description... + +```html + +``` + +### Glossary + +assistive technology +hardware and/or software that acts as a user agent, or along with a mainstream user agent, to provide functionality to meet the requirements of users with disabilities that go beyond those offered by mainstream user agents + +Note +functionality provided by assistive technology includes alternative presentations (e.g., as synthesized speech or magnified content), alternative input methods (e.g., voice), additional navigation or orientation mechanisms, and content transformations (e.g., to make tables more accessible). + +Note +Assistive technologies often communicate data and messages with mainstream user agents by using and monitoring APIs. + +Note +The distinction between mainstream user agents and assistive technologies is not absolute. Many mainstream user agents provide some features to assist individuals with disabilities. The basic difference is that mainstream user agents target broad and diverse audiences that usually include people with and without disabilities. Assistive technologies target narrowly defined populations of users with specific disabilities. The assistance provided by an assistive technology is more specific and appropriate to the needs of its target users. The mainstream user agent may provide important functionality to assistive technologies like retrieving Web content from program objects or parsing markup into identifiable bundles. + +Assistive technologies that are important in the context of this document include the following: + +screen magnifiers, and other visual reading assistants, which are used by people with visual, perceptual and physical print disabilities to change text font, size, spacing, color, synchronization with speech, etc. in order to improve the visual readability of rendered text and images; +screen readers, which are used by people who are blind to read textual information through synthesized speech or braille; +text-to-speech software, which is used by some people with cognitive, language, and learning disabilities to convert text into synthetic speech; +speech recognition software, which may be used by people who have some physical disabilities; +alternative keyboards, which are used by people with certain physical disabilities to simulate the keyboard (including alternate keyboards that use head pointers, single switches, sip/puff and other special input devices.); +alternative pointing devices, which are used by people with certain physical disabilities to simulate mouse pointing and button activations. +same relative order +same position relative to other items + +Note +Items are considered to be in the same relative order even if other items are inserted or removed from the original order. For example, expanding navigation menus may insert an additional level of detail or a secondary navigation section may be inserted into the reading order. + +set of web pages +collection of web pages that share a common purpose and that are created by the same author, group or organization + +Examples include a publication which is split across multiple Web pages, where each page contains one chapter or other significant section of the work. The publication is logically a single contiguous unit, and contains navigation features that enable access to the full set of pages. + +Note +Different language versions would be considered different sets of Web pages. + +user agent +any software that retrieves and presents Web content for users + +Web browsers, media players, plug-ins, and other programs — including assistive technologies — that help in retrieving, rendering, and interacting with Web content. + +web page +a non-embedded resource obtained from a single URI using HTTP plus any other resources that are used in the rendering or intended to be rendered together with it by a user agent + +Note +Although any "other resources" would be rendered together with the primary resource, they would not necessarily be rendered simultaneously with each other. + +Note +For the purposes of conformance with these guidelines, a resource must be "non-embedded" within the scope of conformance to be considered a Web page. + +A Web resource including all embedded images and media. + +A Web mail program built using Asynchronous JavaScript and XML (AJAX). The program lives entirely at http://example.com/mail, but includes an inbox, a contacts area and a calendar. Links or buttons are provided that cause the inbox, contacts, or calendar to display, but do not change the URI of the page as a whole. + +A customizable portal site, where users can choose content to display from a set of different content modules. + +When you enter "http://shopping.example.com/" in your browser, you enter a movie-like interactive shopping environment where you visually move around in a store dragging products off of the shelves around you and into a visual shopping cart in front of you. Clicking on a product causes it to be demonstrated with a specification sheet floating alongside. This might be a single-page Web site or just one page within a Web site. \ No newline at end of file From 31dd8865c32fdf34f87fc37356e31091f8352817 Mon Sep 17 00:00:00 2001 From: Jean-Yves Moyen Date: Thu, 27 Apr 2023 10:42:21 +0200 Subject: [PATCH 02/13] Rename file and add id --- ...T_Rule => consistent-navigation-oe3rrh.md} | 428 +++++++++--------- 1 file changed, 214 insertions(+), 214 deletions(-) rename _rules/{consistent_nav_ACT_Rule => consistent-navigation-oe3rrh.md} (97%) diff --git a/_rules/consistent_nav_ACT_Rule b/_rules/consistent-navigation-oe3rrh.md similarity index 97% rename from _rules/consistent_nav_ACT_Rule rename to _rules/consistent-navigation-oe3rrh.md index 320e1336ff..2a001f098b 100644 --- a/_rules/consistent_nav_ACT_Rule +++ b/_rules/consistent-navigation-oe3rrh.md @@ -1,215 +1,215 @@ ---- -id: -name: -rule_type: atomic -description: | - This rule checks whether Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. - -accessibility_requirements: # Remove whatever is not applicable - wcag2.1: # Success Criterion 3.2.3 Consistent Navigatoin (AA) - forConformance: true | false - failed: not satisfied - passed: satisfied | further testing needed - inapplicable: satisfied | further testing needed - aria12:anchor-name: # - title: Title to display - forConformance: true | false - failed: not satisfied - passed: satisfied | further testing needed - inapplicable: satisfied | further testing needed - wcag-technique:Xxx: # - forConformance: false - failed: not satisfied - passed: satisfied | further testing needed - inapplicable: satisfied | further testing needed - using-aria:anchor-name: # - title: Title to display - forConformance: false - failed: not satisfied - passed: satisfied | further testing needed - inapplicable: satisfied | further testing needed -input_aspects: - - # (e.g. HTTP Messages, DOM Tree, CSS Styling, Accessibility Tree, Language, etc.,) -acknowledgments: - authors: - - # Chris Loiselle - ---- - -## Applicability - -This rule applies to any navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. - -Applies to all technologies. This technique relates to 3.2.3: Consistent Navigation (Failure). - - -## Expectation - -Navigational mechansisms that are repeated on multiple pages within a set of Web pages occur in the same relaative order each time they are repeated. - -## Assumptions - -"Same relative order" means that secondary navigation items may be in between the link items on some pages. They can be present without affecting the outcome of this test. - -## Accessibility Support - -There are no accessibility support issues known. - -## Background - -- (e.g. WCAG Techniques or links with background information mentioned in Applicability, Expectations or Assumptions) - -## Test Cases - -Procedure -Check to see if a navigation mechanism is being used on more than one Web page. -Check the default presentation of the navigation mechanism on each page to see if the list of links are in the same relative order on each Web page. -"Same relative order" means that secondary navigation items may be in between the link items on some pages. They can be present without affecting the outcome of this test. - -Expected Results -If #1 is true and #2 is false, then this failure condition applies and content fails the Success Criterion. - -### Passed - - -A search field is the last item on every Web page in a site. Users can quickly locate the search function. - -An expanding navigation menu - -A navigation menu includes a list of seven items with links to the main sections of a site. When a user selects one of these items, a list of sub-navigation items is inserted into the top-level navigation menu. - -Consistently positioned skip navigation controls - -A "skip navigation" (or "skip to main content") link is included as the first link on every page in a Web site. The link allows users to quickly bypass heading information and navigational content and begin interacting with the main content of a page. - -Skip to navigation link - -Navigational content is consistently located at the end of each page in a set of Web pages. A "skip to navigation" link is consistently located at the beginning of each page so that keyboard users can easily locate it when needed. - -#### Passed Example 1 - -A consistently located control. Presenting repeated components in the same relative order each time they appear. - - -Examples of a navigation mechanism that presents links in same order. - -Page 1 Menu - - -Page 2 Menu - - - -#### Passed Example 2 - -... - -### Failed - -#### Failed Example 1 - -##### Description - -This describes a failure condition for all techniques involving navigation mechanisms that are repeated on multiple Web pages within a set of Web pages (Success Criterion 3.2.3). If the mechanism presents the order of links in a different order on two or more pages, then the failure is triggered. - -Example 1: An XHTML menu presenting a series of links that are in a different relative order on two different pages -Examples of a navigation mechanism that presents links in a different order. - -Page 1 Menu - - -Page 2 Menu - - - -```html - -``` - -### Inapplicable - -#### Inapplicable Example 1 - -Description... - -```html - -``` - -### Glossary - -assistive technology -hardware and/or software that acts as a user agent, or along with a mainstream user agent, to provide functionality to meet the requirements of users with disabilities that go beyond those offered by mainstream user agents - -Note -functionality provided by assistive technology includes alternative presentations (e.g., as synthesized speech or magnified content), alternative input methods (e.g., voice), additional navigation or orientation mechanisms, and content transformations (e.g., to make tables more accessible). - -Note -Assistive technologies often communicate data and messages with mainstream user agents by using and monitoring APIs. - -Note -The distinction between mainstream user agents and assistive technologies is not absolute. Many mainstream user agents provide some features to assist individuals with disabilities. The basic difference is that mainstream user agents target broad and diverse audiences that usually include people with and without disabilities. Assistive technologies target narrowly defined populations of users with specific disabilities. The assistance provided by an assistive technology is more specific and appropriate to the needs of its target users. The mainstream user agent may provide important functionality to assistive technologies like retrieving Web content from program objects or parsing markup into identifiable bundles. - -Assistive technologies that are important in the context of this document include the following: - -screen magnifiers, and other visual reading assistants, which are used by people with visual, perceptual and physical print disabilities to change text font, size, spacing, color, synchronization with speech, etc. in order to improve the visual readability of rendered text and images; -screen readers, which are used by people who are blind to read textual information through synthesized speech or braille; -text-to-speech software, which is used by some people with cognitive, language, and learning disabilities to convert text into synthetic speech; -speech recognition software, which may be used by people who have some physical disabilities; -alternative keyboards, which are used by people with certain physical disabilities to simulate the keyboard (including alternate keyboards that use head pointers, single switches, sip/puff and other special input devices.); -alternative pointing devices, which are used by people with certain physical disabilities to simulate mouse pointing and button activations. -same relative order -same position relative to other items - -Note -Items are considered to be in the same relative order even if other items are inserted or removed from the original order. For example, expanding navigation menus may insert an additional level of detail or a secondary navigation section may be inserted into the reading order. - -set of web pages -collection of web pages that share a common purpose and that are created by the same author, group or organization - -Examples include a publication which is split across multiple Web pages, where each page contains one chapter or other significant section of the work. The publication is logically a single contiguous unit, and contains navigation features that enable access to the full set of pages. - -Note -Different language versions would be considered different sets of Web pages. - -user agent -any software that retrieves and presents Web content for users - -Web browsers, media players, plug-ins, and other programs — including assistive technologies — that help in retrieving, rendering, and interacting with Web content. - -web page -a non-embedded resource obtained from a single URI using HTTP plus any other resources that are used in the rendering or intended to be rendered together with it by a user agent - -Note -Although any "other resources" would be rendered together with the primary resource, they would not necessarily be rendered simultaneously with each other. - -Note -For the purposes of conformance with these guidelines, a resource must be "non-embedded" within the scope of conformance to be considered a Web page. - -A Web resource including all embedded images and media. - -A Web mail program built using Asynchronous JavaScript and XML (AJAX). The program lives entirely at http://example.com/mail, but includes an inbox, a contacts area and a calendar. Links or buttons are provided that cause the inbox, contacts, or calendar to display, but do not change the URI of the page as a whole. - -A customizable portal site, where users can choose content to display from a set of different content modules. - +--- +id: oe3rrh +name: Consistent navigation +rule_type: atomic +description: | + This rule checks whether Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. + +accessibility_requirements: # Remove whatever is not applicable + wcag2.1: # Success Criterion 3.2.3 Consistent Navigatoin (AA) + forConformance: true | false + failed: not satisfied + passed: satisfied | further testing needed + inapplicable: satisfied | further testing needed + aria12:anchor-name: # + title: Title to display + forConformance: true | false + failed: not satisfied + passed: satisfied | further testing needed + inapplicable: satisfied | further testing needed + wcag-technique:Xxx: # + forConformance: false + failed: not satisfied + passed: satisfied | further testing needed + inapplicable: satisfied | further testing needed + using-aria:anchor-name: # + title: Title to display + forConformance: false + failed: not satisfied + passed: satisfied | further testing needed + inapplicable: satisfied | further testing needed +input_aspects: + - # (e.g. HTTP Messages, DOM Tree, CSS Styling, Accessibility Tree, Language, etc.,) +acknowledgments: + authors: + - # Chris Loiselle + +--- + +## Applicability + +This rule applies to any navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. + +Applies to all technologies. This technique relates to 3.2.3: Consistent Navigation (Failure). + + +## Expectation + +Navigational mechansisms that are repeated on multiple pages within a set of Web pages occur in the same relaative order each time they are repeated. + +## Assumptions + +"Same relative order" means that secondary navigation items may be in between the link items on some pages. They can be present without affecting the outcome of this test. + +## Accessibility Support + +There are no accessibility support issues known. + +## Background + +- (e.g. WCAG Techniques or links with background information mentioned in Applicability, Expectations or Assumptions) + +## Test Cases + +Procedure +Check to see if a navigation mechanism is being used on more than one Web page. +Check the default presentation of the navigation mechanism on each page to see if the list of links are in the same relative order on each Web page. +"Same relative order" means that secondary navigation items may be in between the link items on some pages. They can be present without affecting the outcome of this test. + +Expected Results +If #1 is true and #2 is false, then this failure condition applies and content fails the Success Criterion. + +### Passed + + +A search field is the last item on every Web page in a site. Users can quickly locate the search function. + +An expanding navigation menu + +A navigation menu includes a list of seven items with links to the main sections of a site. When a user selects one of these items, a list of sub-navigation items is inserted into the top-level navigation menu. + +Consistently positioned skip navigation controls + +A "skip navigation" (or "skip to main content") link is included as the first link on every page in a Web site. The link allows users to quickly bypass heading information and navigational content and begin interacting with the main content of a page. + +Skip to navigation link + +Navigational content is consistently located at the end of each page in a set of Web pages. A "skip to navigation" link is consistently located at the beginning of each page so that keyboard users can easily locate it when needed. + +#### Passed Example 1 + +A consistently located control. Presenting repeated components in the same relative order each time they appear. + + +Examples of a navigation mechanism that presents links in same order. + +Page 1 Menu + + +Page 2 Menu + + + +#### Passed Example 2 + +... + +### Failed + +#### Failed Example 1 + +##### Description + +This describes a failure condition for all techniques involving navigation mechanisms that are repeated on multiple Web pages within a set of Web pages (Success Criterion 3.2.3). If the mechanism presents the order of links in a different order on two or more pages, then the failure is triggered. + +Example 1: An XHTML menu presenting a series of links that are in a different relative order on two different pages +Examples of a navigation mechanism that presents links in a different order. + +Page 1 Menu + + +Page 2 Menu + + + +```html + +``` + +### Inapplicable + +#### Inapplicable Example 1 + +Description... + +```html + +``` + +### Glossary + +assistive technology +hardware and/or software that acts as a user agent, or along with a mainstream user agent, to provide functionality to meet the requirements of users with disabilities that go beyond those offered by mainstream user agents + +Note +functionality provided by assistive technology includes alternative presentations (e.g., as synthesized speech or magnified content), alternative input methods (e.g., voice), additional navigation or orientation mechanisms, and content transformations (e.g., to make tables more accessible). + +Note +Assistive technologies often communicate data and messages with mainstream user agents by using and monitoring APIs. + +Note +The distinction between mainstream user agents and assistive technologies is not absolute. Many mainstream user agents provide some features to assist individuals with disabilities. The basic difference is that mainstream user agents target broad and diverse audiences that usually include people with and without disabilities. Assistive technologies target narrowly defined populations of users with specific disabilities. The assistance provided by an assistive technology is more specific and appropriate to the needs of its target users. The mainstream user agent may provide important functionality to assistive technologies like retrieving Web content from program objects or parsing markup into identifiable bundles. + +Assistive technologies that are important in the context of this document include the following: + +screen magnifiers, and other visual reading assistants, which are used by people with visual, perceptual and physical print disabilities to change text font, size, spacing, color, synchronization with speech, etc. in order to improve the visual readability of rendered text and images; +screen readers, which are used by people who are blind to read textual information through synthesized speech or braille; +text-to-speech software, which is used by some people with cognitive, language, and learning disabilities to convert text into synthetic speech; +speech recognition software, which may be used by people who have some physical disabilities; +alternative keyboards, which are used by people with certain physical disabilities to simulate the keyboard (including alternate keyboards that use head pointers, single switches, sip/puff and other special input devices.); +alternative pointing devices, which are used by people with certain physical disabilities to simulate mouse pointing and button activations. +same relative order +same position relative to other items + +Note +Items are considered to be in the same relative order even if other items are inserted or removed from the original order. For example, expanding navigation menus may insert an additional level of detail or a secondary navigation section may be inserted into the reading order. + +set of web pages +collection of web pages that share a common purpose and that are created by the same author, group or organization + +Examples include a publication which is split across multiple Web pages, where each page contains one chapter or other significant section of the work. The publication is logically a single contiguous unit, and contains navigation features that enable access to the full set of pages. + +Note +Different language versions would be considered different sets of Web pages. + +user agent +any software that retrieves and presents Web content for users + +Web browsers, media players, plug-ins, and other programs — including assistive technologies — that help in retrieving, rendering, and interacting with Web content. + +web page +a non-embedded resource obtained from a single URI using HTTP plus any other resources that are used in the rendering or intended to be rendered together with it by a user agent + +Note +Although any "other resources" would be rendered together with the primary resource, they would not necessarily be rendered simultaneously with each other. + +Note +For the purposes of conformance with these guidelines, a resource must be "non-embedded" within the scope of conformance to be considered a Web page. + +A Web resource including all embedded images and media. + +A Web mail program built using Asynchronous JavaScript and XML (AJAX). The program lives entirely at http://example.com/mail, but includes an inbox, a contacts area and a calendar. Links or buttons are provided that cause the inbox, contacts, or calendar to display, but do not change the URI of the page as a whole. + +A customizable portal site, where users can choose content to display from a set of different content modules. + When you enter "http://shopping.example.com/" in your browser, you enter a movie-like interactive shopping environment where you visually move around in a store dragging products off of the shelves around you and into a visual shopping cart in front of you. Clicking on a product causes it to be demonstrated with a specification sheet floating alongside. This might be a single-page Web site or just one page within a Web site. \ No newline at end of file From b34b84b18e8c21f8280f60d859786df52b84e1b6 Mon Sep 17 00:00:00 2001 From: Jean-Yves Moyen Date: Thu, 27 Apr 2023 10:45:37 +0200 Subject: [PATCH 03/13] Udpate requirement mappings --- _rules/consistent-navigation-oe3rrh.md | 25 ++++--------------------- 1 file changed, 4 insertions(+), 21 deletions(-) diff --git a/_rules/consistent-navigation-oe3rrh.md b/_rules/consistent-navigation-oe3rrh.md index 2a001f098b..d7037221e2 100644 --- a/_rules/consistent-navigation-oe3rrh.md +++ b/_rules/consistent-navigation-oe3rrh.md @@ -6,28 +6,11 @@ description: | This rule checks whether Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. accessibility_requirements: # Remove whatever is not applicable - wcag2.1: # Success Criterion 3.2.3 Consistent Navigatoin (AA) - forConformance: true | false + wcag2.1:3.2.3: # Consistent Navigation (AA) + forConformance: true failed: not satisfied - passed: satisfied | further testing needed - inapplicable: satisfied | further testing needed - aria12:anchor-name: # - title: Title to display - forConformance: true | false - failed: not satisfied - passed: satisfied | further testing needed - inapplicable: satisfied | further testing needed - wcag-technique:Xxx: # - forConformance: false - failed: not satisfied - passed: satisfied | further testing needed - inapplicable: satisfied | further testing needed - using-aria:anchor-name: # - title: Title to display - forConformance: false - failed: not satisfied - passed: satisfied | further testing needed - inapplicable: satisfied | further testing needed + passed: further testing needed + inapplicable: further testing needed input_aspects: - # (e.g. HTTP Messages, DOM Tree, CSS Styling, Accessibility Tree, Language, etc.,) acknowledgments: From cd7dbe73f50bd7a89f4cf0161e34dd2180dbe027 Mon Sep 17 00:00:00 2001 From: Jean-Yves Moyen Date: Thu, 27 Apr 2023 10:47:19 +0200 Subject: [PATCH 04/13] Update frontmatter --- _rules/consistent-navigation-oe3rrh.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/_rules/consistent-navigation-oe3rrh.md b/_rules/consistent-navigation-oe3rrh.md index d7037221e2..da79816354 100644 --- a/_rules/consistent-navigation-oe3rrh.md +++ b/_rules/consistent-navigation-oe3rrh.md @@ -12,11 +12,11 @@ accessibility_requirements: # Remove whatever is not applicable passed: further testing needed inapplicable: further testing needed input_aspects: - - # (e.g. HTTP Messages, DOM Tree, CSS Styling, Accessibility Tree, Language, etc.,) + - CSS Styling + - DOM tree acknowledgments: authors: - - # Chris Loiselle - + - Chris Loiselle --- ## Applicability From 6f3b9b3560c8e205bbb58300eb0923cca2e89c1c Mon Sep 17 00:00:00 2001 From: HelenBurge <41951878+HelenBurge@users.noreply.github.com> Date: Fri, 7 Feb 2025 12:15:32 +0000 Subject: [PATCH 05/13] Update _rules/consistent-navigation-oe3rrh.md Co-authored-by: Jean-Yves Moyen --- _rules/consistent-navigation-oe3rrh.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_rules/consistent-navigation-oe3rrh.md b/_rules/consistent-navigation-oe3rrh.md index da79816354..cc89fc0a79 100644 --- a/_rules/consistent-navigation-oe3rrh.md +++ b/_rules/consistent-navigation-oe3rrh.md @@ -21,9 +21,9 @@ acknowledgments: ## Applicability -This rule applies to any navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. +This rule applies to any two pages within a given set of pages. -Applies to all technologies. This technique relates to 3.2.3: Consistent Navigation (Failure). +**Note:** the set of pages is the test subject for the rule. ## Expectation From 8ad6c2b5e452d95a3ddf63789b7f32c0ef1f4d9e Mon Sep 17 00:00:00 2001 From: HelenBurge <41951878+HelenBurge@users.noreply.github.com> Date: Fri, 7 Feb 2025 12:15:44 +0000 Subject: [PATCH 06/13] Update _rules/consistent-navigation-oe3rrh.md Co-authored-by: Jean-Yves Moyen --- _rules/consistent-navigation-oe3rrh.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/consistent-navigation-oe3rrh.md b/_rules/consistent-navigation-oe3rrh.md index cc89fc0a79..9db634609a 100644 --- a/_rules/consistent-navigation-oe3rrh.md +++ b/_rules/consistent-navigation-oe3rrh.md @@ -28,7 +28,7 @@ This rule applies to any two pages within a given set of pages. ## Expectation -Navigational mechansisms that are repeated on multiple pages within a set of Web pages occur in the same relaative order each time they are repeated. +For each target, navigational mechanisms that are present on both pages appear in the same relative order. ## Assumptions From 67157ac90cdc34b7cbd3b574f7ae08b1a4be9127 Mon Sep 17 00:00:00 2001 From: HelenBurge <41951878+HelenBurge@users.noreply.github.com> Date: Fri, 7 Feb 2025 13:14:35 +0000 Subject: [PATCH 07/13] Update spelling-ignore.yml --- __tests__/spelling-ignore.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/__tests__/spelling-ignore.yml b/__tests__/spelling-ignore.yml index f3078a8b64..36aa1235bc 100644 --- a/__tests__/spelling-ignore.yml +++ b/__tests__/spelling-ignore.yml @@ -14,6 +14,7 @@ # Tag(s) - svg # `aria-query` dom tags does not list `svg` - xhtml +- XHTML - DOCTYPE - iFrame # used to demonstrate bad spelling - Iframe From 20f7f2e15382da3f8796f98152cd5f701e2f245c Mon Sep 17 00:00:00 2001 From: HelenBurge <41951878+HelenBurge@users.noreply.github.com> Date: Fri, 7 Feb 2025 13:18:24 +0000 Subject: [PATCH 08/13] Update consistent-navigation-oe3rrh.md --- _rules/consistent-navigation-oe3rrh.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_rules/consistent-navigation-oe3rrh.md b/_rules/consistent-navigation-oe3rrh.md index 9db634609a..3921ca1c59 100644 --- a/_rules/consistent-navigation-oe3rrh.md +++ b/_rules/consistent-navigation-oe3rrh.md @@ -160,7 +160,7 @@ screen readers, which are used by people who are blind to read textual informati text-to-speech software, which is used by some people with cognitive, language, and learning disabilities to convert text into synthetic speech; speech recognition software, which may be used by people who have some physical disabilities; alternative keyboards, which are used by people with certain physical disabilities to simulate the keyboard (including alternate keyboards that use head pointers, single switches, sip/puff and other special input devices.); -alternative pointing devices, which are used by people with certain physical disabilities to simulate mouse pointing and button activations. +alternative pointing devices, which are used by people with certain physical disabilities to simulate mouse pointing and button activation. same relative order same position relative to other items @@ -195,4 +195,4 @@ A Web mail program built using Asynchronous JavaScript and XML (AJAX). The progr A customizable portal site, where users can choose content to display from a set of different content modules. -When you enter "http://shopping.example.com/" in your browser, you enter a movie-like interactive shopping environment where you visually move around in a store dragging products off of the shelves around you and into a visual shopping cart in front of you. Clicking on a product causes it to be demonstrated with a specification sheet floating alongside. This might be a single-page Web site or just one page within a Web site. \ No newline at end of file +When you enter "http://shopping.example.com/" in your browser, you enter a movie-like interactive shopping environment where you visually move around in a store dragging products off of the shelves around you and into a visual shopping cart in front of you. Clicking on a product causes it to be demonstrated with a specification sheet floating alongside. This might be a single-page Web site or just one page within a Web site. From ea2e19921578f08a7867ee56696a11f70c4d7cf6 Mon Sep 17 00:00:00 2001 From: HelenBurge <41951878+HelenBurge@users.noreply.github.com> Date: Fri, 7 Feb 2025 13:22:54 +0000 Subject: [PATCH 09/13] Update package.json --- package.json | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/package.json b/package.json index e4f6daa691..8239e20fce 100644 --- a/package.json +++ b/package.json @@ -123,6 +123,10 @@ { "name": "Wilco Fiers", "url": "https://github.com/wilcofiers" + }, + { + "name": "Chris Loiselle", + "url": "https://github.com/ChrisLoiselle" } ], "devDependencies": { From 1707268c6584e434d44596997d5474aabd4d454a Mon Sep 17 00:00:00 2001 From: HelenBurge <41951878+HelenBurge@users.noreply.github.com> Date: Fri, 7 Feb 2025 13:28:40 +0000 Subject: [PATCH 10/13] Update consistent-navigation-oe3rrh.md --- _rules/consistent-navigation-oe3rrh.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/_rules/consistent-navigation-oe3rrh.md b/_rules/consistent-navigation-oe3rrh.md index 3921ca1c59..531808295d 100644 --- a/_rules/consistent-navigation-oe3rrh.md +++ b/_rules/consistent-navigation-oe3rrh.md @@ -30,17 +30,17 @@ This rule applies to any two pages within a given set of pages. For each target, navigational mechanisms that are present on both pages appear in the same relative order. -## Assumptions +## Background -"Same relative order" means that secondary navigation items may be in between the link items on some pages. They can be present without affecting the outcome of this test. +- (e.g. WCAG Techniques or links with background information mentioned in Applicability, Expectations or Assumptions) -## Accessibility Support +### Assumptions -There are no accessibility support issues known. +"Same relative order" means that secondary navigation items may be in between the link items on some pages. They can be present without affecting the outcome of this test. -## Background +### Accessibility Support -- (e.g. WCAG Techniques or links with background information mentioned in Applicability, Expectations or Assumptions) +There are no accessibility support issues known. ## Test Cases From 5505fb3a7ee688dfc0caf48c03705c0ce072e41c Mon Sep 17 00:00:00 2001 From: HelenBurge <41951878+HelenBurge@users.noreply.github.com> Date: Fri, 7 Feb 2025 15:08:39 +0000 Subject: [PATCH 11/13] Create set-of-pages.md --- pages/glossary/set-of-pages.md | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 pages/glossary/set-of-pages.md diff --git a/pages/glossary/set-of-pages.md b/pages/glossary/set-of-pages.md new file mode 100644 index 0000000000..c090bb2cf9 --- /dev/null +++ b/pages/glossary/set-of-pages.md @@ -0,0 +1,10 @@ +--- +title: Set of pages +key: set-of-pages +unambiguous: true +objective: false +--- + +A _set of pages_ is a set of [web pages][] that are in a defined group or brand (also known as [top-level browsing context](https://html.spec.whatwg.org/#top-level-browsing-context)) to require consistent [elements in the DOM](https://html.spec.whatwg.org/#elements-in-the-dom). + +[web pages]: #web-page-html 'Definition of web page' From 8fe66c4065fa43a5a08b8bf38804b9c1e39705d3 Mon Sep 17 00:00:00 2001 From: HelenBurge <41951878+HelenBurge@users.noreply.github.com> Date: Fri, 7 Feb 2025 16:08:11 +0000 Subject: [PATCH 12/13] Create navigational-mechanisms.md --- pages/glossary/navigational-mechanisms.md | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 pages/glossary/navigational-mechanisms.md diff --git a/pages/glossary/navigational-mechanisms.md b/pages/glossary/navigational-mechanisms.md new file mode 100644 index 0000000000..22a7c977d1 --- /dev/null +++ b/pages/glossary/navigational-mechanisms.md @@ -0,0 +1,8 @@ +--- +title: Navigational Mechanisms +key: navigational-mechanisms +unambiguous: true +objective: true +--- + +A method for how a user can move through a series of documents, or [navigation across documments](https://html.spec.whatwg.org/#navigating-across-documents). From fb9e0e506dfa59fdfa31053606d7081d197eaf13 Mon Sep 17 00:00:00 2001 From: HelenBurge <41951878+HelenBurge@users.noreply.github.com> Date: Fri, 7 Feb 2025 16:16:03 +0000 Subject: [PATCH 13/13] Update consistent-navigation-oe3rrh.md Updating the rule to use the glossary in the shared location --- _rules/consistent-navigation-oe3rrh.md | 77 ++++---------------------- 1 file changed, 11 insertions(+), 66 deletions(-) diff --git a/_rules/consistent-navigation-oe3rrh.md b/_rules/consistent-navigation-oe3rrh.md index 531808295d..9b20ab1a48 100644 --- a/_rules/consistent-navigation-oe3rrh.md +++ b/_rules/consistent-navigation-oe3rrh.md @@ -5,7 +5,7 @@ rule_type: atomic description: | This rule checks whether Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. -accessibility_requirements: # Remove whatever is not applicable +accessibility_requirements: wcag2.1:3.2.3: # Consistent Navigation (AA) forConformance: true failed: not satisfied @@ -17,31 +17,31 @@ input_aspects: acknowledgments: authors: - Chris Loiselle + - Helen Burge --- ## Applicability -This rule applies to any two pages within a given set of pages. - -**Note:** the set of pages is the test subject for the rule. - +This rule applies to any two pages within a given [set of pages][]. ## Expectation -For each target, navigational mechanisms that are present on both pages appear in the same relative order. +For each target, [navigational mechanisms][] that are present on both pages appear in the same relative order. ## Background -- (e.g. WCAG Techniques or links with background information mentioned in Applicability, Expectations or Assumptions) - ### Assumptions -"Same relative order" means that secondary navigation items may be in between the link items on some pages. They can be present without affecting the outcome of this test. +"Same relative order" means that secondary navigation items may change the original location of the elements. They can be present without affecting the outcome of this test. ### Accessibility Support There are no accessibility support issues known. +### Bibliography + +- [Understanding Success Criterion 3.2.3: Consistent Navigation](https://www.w3.org/WAI/WCAG22/Understanding/consistent-navigation.html) + ## Test Cases Procedure @@ -139,60 +139,5 @@ Description... ``` -### Glossary - -assistive technology -hardware and/or software that acts as a user agent, or along with a mainstream user agent, to provide functionality to meet the requirements of users with disabilities that go beyond those offered by mainstream user agents - -Note -functionality provided by assistive technology includes alternative presentations (e.g., as synthesized speech or magnified content), alternative input methods (e.g., voice), additional navigation or orientation mechanisms, and content transformations (e.g., to make tables more accessible). - -Note -Assistive technologies often communicate data and messages with mainstream user agents by using and monitoring APIs. - -Note -The distinction between mainstream user agents and assistive technologies is not absolute. Many mainstream user agents provide some features to assist individuals with disabilities. The basic difference is that mainstream user agents target broad and diverse audiences that usually include people with and without disabilities. Assistive technologies target narrowly defined populations of users with specific disabilities. The assistance provided by an assistive technology is more specific and appropriate to the needs of its target users. The mainstream user agent may provide important functionality to assistive technologies like retrieving Web content from program objects or parsing markup into identifiable bundles. - -Assistive technologies that are important in the context of this document include the following: - -screen magnifiers, and other visual reading assistants, which are used by people with visual, perceptual and physical print disabilities to change text font, size, spacing, color, synchronization with speech, etc. in order to improve the visual readability of rendered text and images; -screen readers, which are used by people who are blind to read textual information through synthesized speech or braille; -text-to-speech software, which is used by some people with cognitive, language, and learning disabilities to convert text into synthetic speech; -speech recognition software, which may be used by people who have some physical disabilities; -alternative keyboards, which are used by people with certain physical disabilities to simulate the keyboard (including alternate keyboards that use head pointers, single switches, sip/puff and other special input devices.); -alternative pointing devices, which are used by people with certain physical disabilities to simulate mouse pointing and button activation. -same relative order -same position relative to other items - -Note -Items are considered to be in the same relative order even if other items are inserted or removed from the original order. For example, expanding navigation menus may insert an additional level of detail or a secondary navigation section may be inserted into the reading order. - -set of web pages -collection of web pages that share a common purpose and that are created by the same author, group or organization - -Examples include a publication which is split across multiple Web pages, where each page contains one chapter or other significant section of the work. The publication is logically a single contiguous unit, and contains navigation features that enable access to the full set of pages. - -Note -Different language versions would be considered different sets of Web pages. - -user agent -any software that retrieves and presents Web content for users - -Web browsers, media players, plug-ins, and other programs — including assistive technologies — that help in retrieving, rendering, and interacting with Web content. - -web page -a non-embedded resource obtained from a single URI using HTTP plus any other resources that are used in the rendering or intended to be rendered together with it by a user agent - -Note -Although any "other resources" would be rendered together with the primary resource, they would not necessarily be rendered simultaneously with each other. - -Note -For the purposes of conformance with these guidelines, a resource must be "non-embedded" within the scope of conformance to be considered a Web page. - -A Web resource including all embedded images and media. - -A Web mail program built using Asynchronous JavaScript and XML (AJAX). The program lives entirely at http://example.com/mail, but includes an inbox, a contacts area and a calendar. Links or buttons are provided that cause the inbox, contacts, or calendar to display, but do not change the URI of the page as a whole. - -A customizable portal site, where users can choose content to display from a set of different content modules. - -When you enter "http://shopping.example.com/" in your browser, you enter a movie-like interactive shopping environment where you visually move around in a store dragging products off of the shelves around you and into a visual shopping cart in front of you. Clicking on a product causes it to be demonstrated with a specification sheet floating alongside. This might be a single-page Web site or just one page within a Web site. +[set of pages]: #set-of-pages 'Definition of set of pages' +[navigational mechanisms]: #navigational-mechanisms 'Definition of a navigational mechanism'