All functionality of the content that is available by mouse control must be keyboard accessible. Determine the functionality of visible and hidden interactive document components (links, form fields, drop down menus, show/hide content, tree views, pop ups, etc.) available using a mouse (hover and/or click).
- -#### Test Instructions - -If any of the above checks fail, then Baseline Test 1.A-KeyboardAccess fails.
- -### 1.B Test Procedure for No Keyboard Trap - -**Baseline Test ID:** 1.B-NoKeyboardTrap - -#### Identify Content - -Components that receive keyboard focus.
- -#### Test Instructions - -If the above check fails, then Baseline Test 1.B-NoKeyboardTrap fails.
- -### Advisory: Tips for Streamlined Test Processes -- Keyboard focusable components include links, form fields, drop-down menus, show/hide content, tree views, embedded objects, and pop ups. Focusable components may also be "hidden", positioned off-screen, and/or have no visible indication of focus. -- Keyboard commands include standard and any nonstandard keyboard commands. -- This test may be combined with tests for keyboard focus. -- Tips and techniques for finding hidden content may be useful for testers. -- Based on the document format being tested, it may be useful for testers to reference the applications' guide for keyboard commands. -- Content that is found non-conformant with SC 2.1.1 may be marked for further review for a Section 508 exception if "the underlying function requires input that depends on the path of the user's movement and not just the endpoints". - -### WCAG 2.2 Techniques - -The following sufficient techniques and/or common failures were considered when developing this test procedure for this baseline requirement: -- [G21: Ensuring users are not trapped in content](https://www.w3.org/WAI/WCAG22/Techniques/general/G21) -- [G202: Ensuring keyboard control for all functionality](https://www.w3.org/WAI/WCAG22/Techniques/general/G202) -- [F10: Failure of Success Criterion 2.1.2 and Conformance Requirement 5 due to combining multiple content formats](https://www.w3.org/WAI/WCAG22/Techniques/failures/F10) in a way that traps users inside one format type + +{% include baseline-segments/wcag-techs/01-keyboard-wcag.md %} diff --git a/_baselines/document-baselines/02FocusDocs.md b/_baselines/document-baselines/02FocusDocs.md index c57c79db..49ecedc2 100644 --- a/_baselines/document-baselines/02FocusDocs.md +++ b/_baselines/document-baselines/02FocusDocs.md @@ -3,137 +3,32 @@ title: "2. Focus (Docs)" order-number: 3 toc-group: baseline-docs banner-title: "Baseline for Documents" +source: Doc --- ## 2. Focus -### Accessibility Requirements + +{% include baseline-segments/acc-reqs/02-focus-acc-reqs.md %} -- [WCAG SC 2.4.3 Focus Order](https://www.w3.org/WAI/WCAG22/Understanding/focus-order) -- If a document can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. -- [WCAG SC 2.4.7 Focus Visible](https://www.w3.org/WAI/WCAG22/Understanding/focus-visible) -- Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. -- [WCAG SC 3.2.1 On Focus](https://www.w3.org/WAI/WCAG22/Understanding/on-focus) -- When any user interface component receives focus, it does not initiate a change of context. + +{% include baseline-segments/test-method-rationales/02-focus-tmr.html %} -### Test Method Rationale + +{% include baseline-segments/lim-assmpt-except/02-focus-lae.md %} -Manually navigating or controlling document components by keyboard-only will enable a tester to identify when there is no visual differentiation between a focused item and the rest of the document or content. Using the keyboard to navigate facilitates inspection of focus order. + +{% include baseline-segments/tests/2A-focusvisible.html %} -### Limitations, Assumptions, or Exceptions + +{% include baseline-segments/tests/2B-focusorder.html %} -- Some interface components (e.g., screen text for form filling instructions), which are not normally considered interactive, may be in the tab order. Such interface components should receive a visible indication of focus when the user navigates to them using a keyboard. -- Loss of visible focus should not occur while manually shifting focus through the page (using the TAB or arrow keys). However, when a function that moves the focus is executed (such as an internal page link or hidden content is revealed), it may be necessary to manually shift focus once with the keyboard before focus becomes visible again. This is not considered a failure. -- Focus may be moved to a control either via the keyboard (e.g., tabbing to a control) or the mouse (e.g., clicking on a text field). Moving the mouse over a control does not move the focus unless scripting implements this behavior. -- While it may be a common best practice, Focus Order is not required to move left to right, top to bottom. -- Focus order includes forward and backward navigation. -- Without exception, focus must shift to modal dialog boxes and remain within the dialog box until the box is closed by the user. -- For some types of controls, clicking a control may also activate the control (e.g., button), which may, in turn, initiate a change in context. Controls that are clearly labeled and intended to initiate a change in context do not fail under this test. -- This test evaluates 3.2.1 On Focus using only the keyboard to avoid unintentional activation of controls with a mouse. -- [Changes of context](https://www.w3.org/TR/WCAG22/#dfn-change-of-context) are major changes in content that, if made without user awareness, can disorient users who are not able to view the entire page simultaneously. Changes in context include changes of: - 1. User agent - 2. Viewport - 3. Focus - 4. Content that changes the meaning of the page - - **Note:** A change of content is not always a change of context. Changes in content, such as an expanding outline, dynamic menu, or a tab control do not necessarily change the context, unless they also change one of the above (e.g., focus). - - **Examples:** Opening a new window, moving focus to a different component, going to a new document or window (including anything that would look to a user as if they had moved to a new document) or significantly re-arranging the content of a page/screen are examples of changes of context. + +{% include baseline-segments/tests/2C-onfocus.html %} -### 2.A Test Procedure for Focus Visible + +{% include baseline-segments/advisory/02-focus-adv.html %} -**Baseline Test ID:** 2.A-FocusVisible + +{% include baseline-segments/wcag-techs/02-focus-wcag.html %} -#### Identify Content - -Keyboard accessible interface components (e.g., links, form fields, drop-down menus, show/hide content, tree views, and pop ups).
- -#### Test Instructions - -If any of the above checks fail, then Baseline Test 2.A-FocusVisible fails.
- -### 2.B Test Procedure for Focus Order - -**Baseline Test ID:** 2.B-FocusOrder - -#### Identify Content - -Keyboard accessible document components (links, form fields, drop-down menus, show/hide content, tree views, and pop ups, etc.) that have a meaningful sequence of navigation.
- -#### Test Instructions - -If any of the above checks fail, then Baseline Test 2.B-FocusOrder fails.
- -### 2.C Test Procedure for On Focus - -**Baseline Test ID:** 2.C-OnFocus - -#### Identify Content - -Keyboard accessible document components (links, form fields, drop-down menus, show/hide content, tree views, and pop ups, etc.).
- -#### Test Instructions - -If any of the above checks fail, then Baseline Test 2.C-OnFocus fails.
- -### Advisory: Tips for Streamlined Test Processes - -- The clarity of visible focus is subjective, and the minimum level is the application's (or OS platform's) default display setting for indicating focus. Applications may also represent visual focus differently in specific situations. -- This test may be performed simultaneously with [Baseline 1: Keyboard Access]({{site.baseurl}}/document-baselines/01KeyboardDocs). -- No focus modifications should be enabled in the test environment during testing. Some testing tools will add a visible outline around elements that receive focus. While testing tools may help testers to track focus, any markup provided by a testing tool should not be used as an indicator of visible focus for meeting this requirement. -- Given the variability in how applications may present visual focus in specific situations, test reports should include details about testing environment, including application and version. -- Tab order that initially appears illogical may still meet this requirement due to an application-specific business logic. -- It may be useful to combine these tests with tests for keyboard navigation and visible focus. -- It may be useful to provide instructions about what "modal dialog boxes" are and how they should behave. - -### WCAG 2.2 Techniques - -The following sufficient techniques and/or common failures were considered when developing this test procedure for this baseline requirement: - -- [F55: Failure of Success Criteria 2.1.1, 2.4.7, and 3.2.1 due to using script to remove focus when focus is received](https://www.w3.org/WAI/WCAG22/Techniques/failures/F55) -- [F85: Failure of Success Criterion 2.4.3 due to using dialogs or menus that are not adjacent to their trigger control](https://www.w3.org/WAI/WCAG22/Techniques/failures/F85) in the sequential navigation order -- [G59: Placing the interactive elements in an order that follows sequences and relationships within the content](https://www.w3.org/WAI/WCAG22/Techniques/general/G59) -- [G107: Using "activate" rather than "focus" as a trigger for changes of context](https://www.w3.org/WAI/WCAG22/Techniques/general/G107) -- [G149: Using user interface components that are highlighted by the user agent when they receive focus.](https://www.w3.org/WAI/WCAG22/Techniques/general/G149) -- [G165: Using the default focus indicator for the platform so that high visibility default focus indicators will carry over](https://www.w3.org/WAI/WCAG22/Techniques/general/G165) -- [G195: Using an author-supplied, highly visible focus indicator](https://www.w3.org/WAI/WCAG22/Techniques/general/G195) -- [SCR26: Inserting dynamic content into the Document Object Model immediately following its trigger element](https://www.w3.org/WAI/WCAG22/Techniques/client-side-script/SCR26) -- [PDF3: Ensuring correct tab and reading order in PDF documents](https://www.w3.org/WAI/WCAG22/Techniques/pdf/PDF3) diff --git a/_baselines/document-baselines/03NoninterferenceDocs.md b/_baselines/document-baselines/03NoninterferenceDocs.md index fa5ec424..85c6376b 100644 --- a/_baselines/document-baselines/03NoninterferenceDocs.md +++ b/_baselines/document-baselines/03NoninterferenceDocs.md @@ -3,49 +3,25 @@ title: "3. Non-Interference (Docs)" order-number: 4 toc-group: baseline-docs banner-title: "Baseline for Documents" +source: Doc --- ## 3. Non-Interference -### Accessibility Requirements + +{% include baseline-segments/acc-reqs/03-noninterference-acc-reqs.md %} -1. [WCAG Conformance Requirement 5: Non-Interference](https://www.w3.org/WAI/WCAG22/Understanding/conformance#conf-req5) -- The following success criteria apply to all content in the document, including content that is not otherwise relied upon to meet conformance, because failure to meet them could interfere with any use of the content: - - 1.4.2 - Audio Control, - - 2.1.2 - No Keyboard Trap, - - 2.3.1 - Three Flashes or Below Threshold, and - - 2.2.2 - Pause, Stop, Hide. + +{% include baseline-segments/test-method-rationales/03-noninterference-tmr.html %} -### Test Method Rationale + +{% include baseline-segments/lim-assmpt-except/03-noninterference-lae.md %} -The test results for SC's 1.4.2 (Baseline Test 21.D-AudioControl), 2.1.2 (1.B-NoKeyboardTrap), 2.3.1 (9.A-Flashes), and 2.2.2 (21.B-MovingInfo and 21.C-AutoUpdate) determine the result of this baseline test. + +{% include baseline-segments/tests/3A-noninterference.html %} -### Limitations, Assumptions, or Exceptions + +{% include baseline-segments/advisory/03-noninterference-adv.html %} -None - -### 3.A Test Procedure for Non-Interference - -**Baseline Test ID:** 3.A-NonInterference - -#### Identify Content - -Results of Baseline Tests 21.D-AudioControl, 1.B-NoKeyboardTrap, 9.A-Flashes, 21.B-MovingInfo, and 21.C-AutoUpdate.
- -#### Test Instructions - -If any of the above checks fail, then Baseline Requirement 3.A-NonInterference fails.
- -### Advisory: Tips for Streamlined Test Processes - -- This test result is a logical AND of the identified SCs. All must pass for this test result to pass. -- A reporting tool may be utilized to generate the result for Conformance Requirement 5. - -### WCAG 2.2 Techniques - -Not Applicable. + +{% include baseline-segments/wcag-techs/03-noninterference-wcag.md %} diff --git a/_baselines/document-baselines/04RepetitiveContentDocs.md b/_baselines/document-baselines/04RepetitiveContentDocs.md index 20e5fa03..0c5ffbba 100644 --- a/_baselines/document-baselines/04RepetitiveContentDocs.md +++ b/_baselines/document-baselines/04RepetitiveContentDocs.md @@ -3,16 +3,11 @@ title: "4. Repetitive Content -- Not Applicable (Docs)" order-number: 5 toc-group: baseline-docs banner-title: "Baseline for Documents" +source: Doc --- ## 4. Repetitive Content – Not Applicable to Documents -### No Accessibility Requirements + +{% include baseline-segments/acc-reqs/no-acc-reqs.md %} -This Baseline test for repetitive content checks for WCAG SCs that Section 508 does not apply to non-web documents. It is from the ICT Testing Baseline for Web and was not removed to maintain harmonization. - -Per Section 508 E205.4 Accessibility Standard for electronic content exception, non-web documents shall not be required to conform to the following success criteria: - -- WCAG SC 2.4.1 Bypass Blocks – A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. -- WCAG SC 3.2.3 Consistent Navigation – 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. -- WCAG SC 3.2.4 Consistent Identification – Components that have the same functionality within a set of Web pages are identified consistently. diff --git a/_baselines/document-baselines/05ControlsDocs.md b/_baselines/document-baselines/05ControlsDocs.md index 9b68ddc7..13dff897 100644 --- a/_baselines/document-baselines/05ControlsDocs.md +++ b/_baselines/document-baselines/05ControlsDocs.md @@ -3,6 +3,7 @@ title: "5. User Controls (Docs)" order-number: 6 toc-group: baseline-docs banner-title: "Baseline for Documents" +source: Doc --- ## 5. User Controls diff --git a/_baselines/document-baselines/06ImagesDocs.md b/_baselines/document-baselines/06ImagesDocs.md index 99ff6232..a5916528 100644 --- a/_baselines/document-baselines/06ImagesDocs.md +++ b/_baselines/document-baselines/06ImagesDocs.md @@ -3,10 +3,40 @@ title: "6. Images (Docs)" order-number: 7 toc-group: baseline-docs banner-title: "Baseline for Documents" +source: Doc --- ## 6. Images + + +{% include baseline-segments/acc-reqs/06-images-acc-reqs.md %} + + +{% include baseline-segments/test-method-rationales/06-images-tmr.html %} + + +{% include baseline-segments/lim-assmpt-except/06-images-lae.md %} + + +{% include baseline-segments/tests/6A-meaningfulimage.html %} + + +{% include baseline-segments/tests/6B-decorativeimage.html %} + + +{% include baseline-segments/tests/6C-captcha.html %} + + +{% include baseline-segments/tests/6D-imagetext.html %} + + +{% include baseline-segments/advisory/06-images-adv.html %} + + +{% include baseline-segments/wcag-techs/06-images-wcag.md %} + + \ No newline at end of file diff --git a/_baselines/document-baselines/07SensoryDocs.md b/_baselines/document-baselines/07SensoryDocs.md index 259b2b03..831c63ab 100644 --- a/_baselines/document-baselines/07SensoryDocs.md +++ b/_baselines/document-baselines/07SensoryDocs.md @@ -3,6 +3,7 @@ title: "7. Sensory Characteristics (Docs)" order-number: 8 toc-group: baseline-docs banner-title: "Baseline for Documents" +source: Doc --- ## 7. Sensory Characteristics diff --git a/_baselines/document-baselines/08ContrastDocs.md b/_baselines/document-baselines/08ContrastDocs.md index 4f7a700a..29aa6c5a 100644 --- a/_baselines/document-baselines/08ContrastDocs.md +++ b/_baselines/document-baselines/08ContrastDocs.md @@ -3,6 +3,7 @@ title: "8. Contrast (Docs)" order-number: 9 toc-group: baseline-docs banner-title: "Baseline for Documents" +source: Doc --- ## 8. Contrast @@ -19,6 +20,18 @@ banner-title: "Baseline for Documents" This test is conducted to evaluate equal access to information for all users, including those who may experience difficulty in discerning between items with low contrast. + +{% include baseline-segments/lim-assmpt-except/08-contrast-lae.md %} + + +{% include baseline-segments/tests/08A-contrastminimum.html %} + + +{% include baseline-segments/advisory/08-contrast-adv.html %} + + +{% include baseline-segments/wcag-techs/08-contrast-wcag.md %} + ### Limitations, Assumptions, or Exceptions - Exception: The following types of text and images of text are not included in this test: diff --git a/_baselines/document-baselines/09FlashingDocs.md b/_baselines/document-baselines/09FlashingDocs.md index f08559d7..c30cd7c4 100644 --- a/_baselines/document-baselines/09FlashingDocs.md +++ b/_baselines/document-baselines/09FlashingDocs.md @@ -3,6 +3,7 @@ title: "9. Flashing (Docs)" order-number: 10 toc-group: baseline-docs banner-title: "Baseline for Documents" +source: Doc --- ## 9. Flashing @@ -32,6 +33,15 @@ This test addresses flashing caused by the content itself, including: - Note from SC 2.3.1: - Note 1: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference. + +{% include baseline-segments/tests/09A-flashes.html %} + + +{% include baseline-segments/advisory/09-flashing-adv.html %} + + +{% include baseline-segments/wcag-techs/09-flashing-wcag.md %} + ### 9.A Test Procedure for Three Flashes or Below Threshold **Baseline Test ID:** 9.A-Flashes diff --git a/_baselines/document-baselines/10FormsDocs.md b/_baselines/document-baselines/10FormsDocs.md index ccd34d78..0c9bbeb9 100644 --- a/_baselines/document-baselines/10FormsDocs.md +++ b/_baselines/document-baselines/10FormsDocs.md @@ -3,6 +3,7 @@ title: "10. Forms (Docs)" order-number: 11 toc-group: baseline-docs banner-title: "Baseline for Documents" +source: Doc --- ## 10. Forms @@ -27,6 +28,36 @@ banner-title: "Baseline for Documents" Review form instructions for completeness and programmatic association to their inputs. Enter erroneous inputs and review error notifications provided to the user. + +{% include baseline-segments/lim-assmpt-except/10-forms-lae.md %} + + +{% include baseline-segments/tests/10A-formname.html %} + + +{% include baseline-segments/tests/10B-formdescriptivelabel.html %} + + +{% include baseline-segments/tests/10C-oninput.html %} + + +{% include baseline-segments/tests/10D-erroridentification.html %} + + +{% include baseline-segments/tests/10E-formhaslabel.html %} + + +{% include baseline-segments/tests/10F-errorsuggestion.html %} + + +{% include baseline-segments/tests/10G-errorprevention.html %} + + +{% include baseline-segments/advisory/10-forms-adv.html %} + + +{% include baseline-segments/wcag-techs/10-forms-wcag.md %} --> + ### Limitations, Assumptions, or Exceptions - Read-only (e.g., pre-filled) form fields receive keyboard focus and are selectable but cannot be modified. These must be labeled and programmatically determinable, and are tested under SC 1.3.1. diff --git a/_baselines/document-baselines/11PageTitlesDocs.md b/_baselines/document-baselines/11PageTitlesDocs.md index 9848cd07..0ef9bb53 100644 --- a/_baselines/document-baselines/11PageTitlesDocs.md +++ b/_baselines/document-baselines/11PageTitlesDocs.md @@ -3,6 +3,7 @@ title: "11. Document Titles (Docs)" order-number: 12 toc-group: baseline-docs banner-title: "Baseline for Documents" +source: Doc --- ## 11. Document Titles @@ -15,6 +16,18 @@ banner-title: "Baseline for Documents" The Title property defines the title of the document and is required in all documents. This test evaluates the presence of a descriptive title for the document. + +{% include baseline-segments/lim-assmpt-except/11-pagetitles-lae.md %} + + +{% include baseline-segments/tests/11A-documenttitled.html %} + + +{% include baseline-segments/advisory/11-pagetitles-adv.html %} + + +{% include baseline-segments/wcag-techs/11-pagetitles-wcag.md %} + ### Limitations, Assumptions, Exceptions 1. Every document must have a descriptive title. This test always applies. diff --git a/_baselines/document-baselines/12DataTablesDocs.md b/_baselines/document-baselines/12DataTablesDocs.md index 5f28b118..b427687a 100644 --- a/_baselines/document-baselines/12DataTablesDocs.md +++ b/_baselines/document-baselines/12DataTablesDocs.md @@ -3,6 +3,7 @@ title: "12. Tables (Docs)" order-number: 13 toc-group: baseline-docs banner-title: "Baseline for Documents" +source: Doc --- ## 12. Tables diff --git a/_baselines/document-baselines/13StructureDocs.md b/_baselines/document-baselines/13StructureDocs.md index 904c014b..d6b27fd5 100644 --- a/_baselines/document-baselines/13StructureDocs.md +++ b/_baselines/document-baselines/13StructureDocs.md @@ -3,6 +3,7 @@ title: "13. Content Structure (Docs)" order-number: 14 toc-group: baseline-docs banner-title: "Baseline for Documents" +source: Doc --- ## 13. Content Structure diff --git a/_baselines/document-baselines/14LinksDocs.md b/_baselines/document-baselines/14LinksDocs.md index 5e634bf3..cacbe885 100644 --- a/_baselines/document-baselines/14LinksDocs.md +++ b/_baselines/document-baselines/14LinksDocs.md @@ -3,6 +3,7 @@ title: "14. Links (Docs)" order-number: 15 toc-group: baseline-docs banner-title: "Baseline for Documents" +source: Doc --- ## 14. Links diff --git a/_baselines/document-baselines/15LanguageDocs.md b/_baselines/document-baselines/15LanguageDocs.md index bc040642..a8e4a926 100644 --- a/_baselines/document-baselines/15LanguageDocs.md +++ b/_baselines/document-baselines/15LanguageDocs.md @@ -3,6 +3,7 @@ title: "15. Language (Docs)" order-number: 16 toc-group: baseline-docs banner-title: "Baseline for Documents" +source: Doc --- ## 15. Language @@ -71,4 +72,17 @@ The following sufficient techniques and/or common failures were considered when - [H57: Using language attributes on the html element](https://www.w3.org/WAI/WCAG22/Techniques/html/H57) - [H58: Using language attributes to identify changes in the human language](https://www.w3.org/WAI/WCAG22/Techniques/html/H58) - [PDF16: Setting the default language using the /Lang entry in the document catalog of a PDF document](https://www.w3.org/WAI/WCAG22/Techniques/pdf/PDF16) -- [PDF19: Specifying the language for a passage or phrase with the Lang entry in PDF documents](https://www.w3.org/WAI/WCAG22/Techniques/pdf/PDF19) \ No newline at end of file +- [PDF19: Specifying the language for a passage or phrase with the Lang entry in PDF documents](https://www.w3.org/WAI/WCAG22/Techniques/pdf/PDF19) + +{% include baseline-segments/acc-reqs/15-language-acc-reqs.md %} + +{% include baseline-segments/test-method-rationales/15-language-tmr.html %} + +{% include baseline-segments/lim-assmpt-except/15-language-lae.md %} + +{% include baseline-segments/tests/15A-languagedocument.html %} +{% include baseline-segments/tests/15B-languageparts.html %} + +{% include baseline-segments/advisory/15-language-adv.html %} + +{% include baseline-segments/wcag-techs/15-language-wcag.md %} diff --git a/_baselines/document-baselines/16AudioVideoDocs.md b/_baselines/document-baselines/16AudioVideoDocs.md index 0aaa3d28..65021e4b 100644 --- a/_baselines/document-baselines/16AudioVideoDocs.md +++ b/_baselines/document-baselines/16AudioVideoDocs.md @@ -3,6 +3,7 @@ title: "16. Audio-Only and Video-Only (Docs)" order-number: 17' toc-group: baseline-docs banner-title: "Baseline for Documents" +source: Doc --- ## 16. Audio-Only and Video-Only diff --git a/_baselines/document-baselines/17SyncMediaDocs.md b/_baselines/document-baselines/17SyncMediaDocs.md index 4125aebd..07028c54 100644 --- a/_baselines/document-baselines/17SyncMediaDocs.md +++ b/_baselines/document-baselines/17SyncMediaDocs.md @@ -3,6 +3,7 @@ title: "17. Synchronized Media (Docs)" order-number: 18 toc-group: baseline-docs banner-title: "Baseline for Documents" +source: Doc --- ## 17. Synchronized Media diff --git a/_baselines/document-baselines/18StylesheetDocs.md b/_baselines/document-baselines/18StylesheetDocs.md index fe7edcf2..979d3f0a 100644 --- a/_baselines/document-baselines/18StylesheetDocs.md +++ b/_baselines/document-baselines/18StylesheetDocs.md @@ -3,6 +3,7 @@ title: "18. Meaningful Content and Sequence (Docs)" order-number: 19 toc-group: baseline-docs banner-title: "Baseline for Documents" +source: Doc --- ## 18. Meaningful Content and Sequence diff --git a/_baselines/document-baselines/19FramesDocs.md b/_baselines/document-baselines/19FramesDocs.md index 02d36f1f..6e2735e4 100644 --- a/_baselines/document-baselines/19FramesDocs.md +++ b/_baselines/document-baselines/19FramesDocs.md @@ -3,6 +3,7 @@ title: "19. Frames and iFrames -- Not Applicable (Docs)" order-number: 20 toc-group: baseline-docs banner-title: "Baseline for Documents" +source: Doc --- # 19. Frames and iFrames-- Not Applicable to Documents diff --git a/_baselines/document-baselines/20AlternateVersionsDocs.md b/_baselines/document-baselines/20AlternateVersionsDocs.md index b70581cc..177270c5 100644 --- a/_baselines/document-baselines/20AlternateVersionsDocs.md +++ b/_baselines/document-baselines/20AlternateVersionsDocs.md @@ -3,6 +3,7 @@ title: "20. Conforming Alternate Version (Docs)" order-number: 21 toc-group: baseline-docs banner-title: "Baseline for Documents" +source: Doc --- ## 20. Conforming Alternate Version diff --git a/_baselines/document-baselines/21TimedEventsDocs.md b/_baselines/document-baselines/21TimedEventsDocs.md index 6aadad11..7ca71f76 100644 --- a/_baselines/document-baselines/21TimedEventsDocs.md +++ b/_baselines/document-baselines/21TimedEventsDocs.md @@ -3,6 +3,7 @@ title: "21. Timed Events (Docs)" order-number: 22 toc-group: baseline-docs banner-title: "Baseline for Documents" +source: Doc --- ## 21. Timed Events diff --git a/_baselines/document-baselines/22ResizeDocs.md b/_baselines/document-baselines/22ResizeDocs.md index c5a9010a..ab1f1b1a 100644 --- a/_baselines/document-baselines/22ResizeDocs.md +++ b/_baselines/document-baselines/22ResizeDocs.md @@ -3,6 +3,7 @@ title: "22. Resize Text (Docs)" order-number: 23 toc-group: baseline-docs banner-title: "Baseline for Documents" +source: Doc --- ## 22. Resize Text diff --git a/_baselines/document-baselines/23MultipleWaysDocs.md b/_baselines/document-baselines/23MultipleWaysDocs.md index b60d8397..ad40c9f8 100644 --- a/_baselines/document-baselines/23MultipleWaysDocs.md +++ b/_baselines/document-baselines/23MultipleWaysDocs.md @@ -3,14 +3,10 @@ title: "23. Multiple Ways — Not Applicable (Docs)" order-number: 24 toc-group: baseline-docs banner-title: "Baseline for Documents" +source: Doc --- ## 23. Multiple Ways — Not Applicable to Documents -### No Accessibility Requirements - -This Baseline test applies to a WCAG Success Criterion that Section 508 does not apply to non-web documents. It is from the ICT Testing Baseline for Web and was retained to maintain harmonization. - -Per Section 508 E205.4, the accessibility standard for electronic content, non-web documents are not required to conform to the following success criteria: - -- WCAG SC 2.4.5 Multiple Ways — More than one way is available to locate a Web page within a set of Web pages, except where the Web page is the result of, or a step in, a process. + +{% include baseline-segments/acc-reqs/no-acc-reqs.md %} diff --git a/_baselines/document-baselines/24ParsingDocs.md b/_baselines/document-baselines/24ParsingDocs.md index 6cbbb53d..95a6328a 100644 --- a/_baselines/document-baselines/24ParsingDocs.md +++ b/_baselines/document-baselines/24ParsingDocs.md @@ -3,6 +3,7 @@ title: "24. Parsing (Docs)" order-number: 25 toc-group: baseline-docs banner-title: "Baseline for Documents" +source: Doc --- ## 24. Parsing diff --git a/_baselines/web-baselines/01Keyboard.md b/_baselines/web-baselines/01Keyboard.md index a8d4cb0a..18af4242 100644 --- a/_baselines/web-baselines/01Keyboard.md +++ b/_baselines/web-baselines/01Keyboard.md @@ -3,87 +3,28 @@ title: "1. Keyboard Accessible (Web)" order-number: 2 toc-group: baseline-web banner-title: "Baseline for Web" +source: Web --- ## 1. Keyboard Accessible -### Accessibility Requirements -- [WCAG SC 2.1.1 Keyboard](https://www.w3.org/WAI/WCAG22/Understanding/keyboard) – All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. -- [WCAG SC 2.1.2 No Keyboard Trap](https://www.w3.org/WAI/WCAG22/Understanding/no-keyboard-trap) – If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. -- [Conformance Requirement 5: Non-Interference](https://www.w3.org/WAI/WCAG22/Understanding/conformance#conf-req5) - The following success criteria apply to all content on the page, including content that is not otherwise relied upon to meet conformance, because failure to meet them could interfere with any use of the page: 1.4.2 - Audio Control, 2.1.2 - No Keyboard Trap, 2.3.1 - Three Flashes or Below Threshold, and 2.2.2 - Pause, Stop, Hide. + +{% include baseline-segments/acc-reqs/01-keyboard-acc-reqs.md %} -### Test Method Rationale -This requirement relies on use of a keyboard to validate access and control of all functionality of the content first by checking use of standard keyboard commands (TAB, Space Bar, Enter, Escape, etc.). If an interface uses non-standard keyboard commands, the interface must clearly document the commands and make users aware that the commands exist. + +{% include baseline-segments/test-method-rationales/01-keyboard-tmr.html %} -Keyboard access and control includes the ability to navigate to **AND** away from interactive content using only a keyboard. + +{% include baseline-segments/lim-assmpt-except/01-keyboard-lae.md %} -### Limitations, Assumptions, or Exceptions + +{% include baseline-segments/tests/1A-keyboardaccess.html %} -- This test was written to be performed on a standard physical keyboard for a Windows PC. While keyboard emulators (such as on-screen keyboards, alternate keyboards, speech input, etc.) may be utilized, testing instructions may differ. Mouse Keys (a Windows and Mac OS feature that enables control of the mouse pointer by keyboard) is not a keyboard emulator. -- Notes from SC 2.1.1: - - Note 1: This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input but the underlying function (text input) does not. - - Note 2: This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation. -- Note from SC 2.1.2: - - Note 1: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference. + +{% include baseline-segments/tests/1B-nokeyboardtrap.html %} -### 1.A Test Procedure for Keyboard Access + +{% include baseline-segments/advisory/01-keyboard-adv.html %} -**Baseline Test ID:** 1.A-KeyboardAccess -#### Identify Content -All functionality of the content that is available by mouse control must be keyboard accessible. Determine the functionality of visible and hidden interactive interface components (links, form fields, drop down menus, show/hide content, tree views, pop ups/light boxes, iframes, etc.) available using a mouse (hover and/or click).
+ +{% include baseline-segments/wcag-techs/01-keyboard-wcag.md %} -#### Test Instructions -If any of the above checks fail, then Baseline Test 1.A-KeyboardAccess fails.
- -### 1.B Test Procedure for No Keyboard Trap - -**Baseline Test ID:** 1.B-NoKeyboardTrap -#### Identify Content -Components that receive keyboard focus.
- -#### Test Instructions -If the above check fails, then Baseline Test 1.B-NoKeyboardTrap fails. -
- -### Advisory: Tips for streamlined test processes - -- Keyboard focusable components include links, form fields, drop down menus, show/hide content, tree views, pop ups/light boxes, frames, and iframes. Focusable components may also be "hidden", positioned off-screen, and/or have no visible indication of focus. -- Keyboard commands include standard and any nonstandard keyboard commands. -- Keyboard access for `title` attribute is available in Internet Explorer 11 for Windows 8.1 and 10. It may be useful to notify testers to pause while tabbing through interactive content with a `title` attribute to see if `title` content is revealed during Keyboard Navigation testing. -- This test may be combined with tests for keyboard focus. -- Tips and techniques for finding hidden content may be useful for testers. -- It may be useful to provide a Windows keyboard reference guide to testers. -- Content that is found non-conformant with SC 2.1.1 may be marked for further review for a Section 508 exception if “the underlying function requires input that depends on the path of the user's movement and not just the endpoints". - -### WCAG 2.2 Techniques - -The following sufficient techniques and/or common failures were considered when developing this test procedure for this baseline requirement: -- [G21: Ensuring users are not trapped in content](https://www.w3.org/WAI/WCAG22/Techniques/general/G21) -- [G202: Ensuring keyboard control for all functionality](https://www.w3.org/WAI/WCAG22/Techniques/general/G202) - diff --git a/_baselines/web-baselines/02Focus.md b/_baselines/web-baselines/02Focus.md new file mode 100644 index 00000000..7722c0b9 --- /dev/null +++ b/_baselines/web-baselines/02Focus.md @@ -0,0 +1,33 @@ +--- +title: "2. Focus (Web)" +order-number: 3 +toc-group: baseline-web +banner-title: "Baseline for Web" +source: Web +--- +## 2. Focus + + +{% include baseline-segments/acc-reqs/02-focus-acc-reqs.md %} + + +{% include baseline-segments/test-method-rationales/02-focus-tmr.html %} + + +{% include baseline-segments/lim-assmpt-except/02-focus-lae.md %} + + +{% include baseline-segments/tests/2A-focusvisible.html %} + + +{% include baseline-segments/tests/2B-focusorder.html %} + + +{% include baseline-segments/tests/2C-onfocus.html %} + + +{% include baseline-segments/advisory/02-focus-adv.html %} + + +{% include baseline-segments/wcag-techs/02-focus-wcag.html %} + diff --git a/_baselines/web-baselines/02FocusVisible.md b/_baselines/web-baselines/02FocusVisible.md deleted file mode 100644 index 3841944b..00000000 --- a/_baselines/web-baselines/02FocusVisible.md +++ /dev/null @@ -1,125 +0,0 @@ ---- -title: "2. Focus (Web)" -order-number: 3 -toc-group: baseline-web -banner-title: "Baseline for Web" ---- -## 2. Focus - -### Accessibility Requirements - -- [WCAG SC 2.4.3 Focus Order](https://www.w3.org/WAI/WCAG22/Understanding/focus-order) -- If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. -- [WCAG SC 2.4.7 Focus Visible](https://www.w3.org/WAI/WCAG22/Understanding/focus-visible) -- Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. -- [WCAG SC 3.2.1 On Focus](https://www.w3.org/WAI/WCAG22/Understanding/on-focus) -- When any user interface component receives focus, it does not initiate a change of context. - -### Test Method Rationale - -Manually navigating or controlling the interface by keyboard-only will enable a tester to identify when there is no visual differentiation between a focused item and the rest of the interface or content. Using the keyboard to navigate facilitates inspection of focus order. - -### Limitations, Assumptions, or Exceptions - -- Some interface components (e.g., screen text for form filling instructions), which are not normally considered interactive, may be in the tab order. Such interface components should receive a visible indication of focus when the user navigates to them using a keyboard. -- Skip link visual focus is a part of this test. -- Loss of visible focus should not occur while manually shifting focus through the page (using the TAB or arrow keys). However, when a function that moves the focus is executed (such as an internal page link or hidden content is revealed), it may be necessary to manually shift focus once with the keyboard before focus becomes visible again. This is not considered a failure. -- Focus may be moved to a control either via the keyboard (e.g. tabbing to a control) or the mouse (e.g. clicking on a text field). Moving the mouse over a control does not move the focus unless scripting implements this behavior. -- While it may be a common best practice, Focus Order is not required to move left to right, top to bottom. -- Focus order includes forward and backward navigation. -- Without exception, focus must shift to modal dialog boxes and remain within the dialog box until the box is closed by the user. -- Assistive technology will process aria live regions without a focus shift. Live regions that do not contain interactive content do not require a focus shift and would not be included in this test. -- For some types of controls, clicking a control may also activate the control (e.g. button), which may, in turn, initiate a change in context. Controls that are clearly labeled and intended to initiate a change in context do not fail under this test. -- This test evaluates 3.2.1 On Focus using only the keyboard to avoid unintentional activation of controls with a mouse. -- [Changes of context](https://www.w3.org/TR/WCAG22/#dfn-change-of-context) are major changes that, if made without user awareness, can disorient users who are not able to view the entire page simultaneously. Changes in context include changes of: - 1. User agent - 2. Viewport - 3. Focus - 4. Content that changes the meaning of the page - - **Note:** A change of content is not always a change of context. Changes in content, such as an expanding outline, dynamic menu, or a tab control do not necessarily change the context, unless they also change one of the above (e.g., focus). - - **Examples:** Opening a new window, moving focus to a different component, going to a new page or window (including anything that would look to a user as if they had moved to a new page) or significantly re-arranging the content of a page/screen are examples of changes of context. - -### 2.A Test Procedure for Focus Visible - -**Baseline Test ID:** 2.A-FocusVisible - -#### Identify Content -Keyboard accessible interface components (e.g., links, form fields, drop down menus, show/hide content, tree views, pop ups/light boxes, frames, iframes).
- -#### Test Instructions -If any of the above checks fail, then Baseline Test 2.A-FocusVisible fails.
- -### 2.B Test Procedure for Focus Order - -**Baseline Test ID:** 2.B-FocusOrder -#### Identify Content -Keyboard accessible interface components (links, form fields, drop down menus, show/hide content, tree views, pop ups/light boxes, frames, iframes, etc.) that have a meaningful sequence of navigation.
- -#### Test Instructions -If any of the above checks fail, then Baseline Test 2.B-FocusOrder fails.
- -### 2.C Test Procedure for On Focus - -**Baseline Test ID:** 2.C-OnFocus -#### Identify Content -Keyboard accessible interface components (links, form fields, drop down menus, show/hide content, tree views, pop ups/light boxes, frames, iframes, etc.).
- -#### Test Instructions -If any of the above checks fail, then Baseline Test 2.C-OnFocus fails.
- -### Advisory: Tips for streamlined test processes - -- The clarity of visible focus is subjective and the minimum level is the browser’s (or OS platform) default display setting for indicating focus. Browsers may also represent visual focus differently in specific situations. -- This test may be performed simultaneously with [Baseline 1: Keyboard Access]({{site.baseurl}}/web-baselines/01Keyboard/). -- No focus modifications should be enabled in the test environment during testing. Some testing tools will add a visible outline around elements that receive focus. While testing tools may help testers to track focus, any markup provided by a testing tool should not be used as an indicator of visible focus for meeting this requirement. -- Given the variability in how browsers may present visual focus in specific situations, test reports should include details about testing environment, including browser and version. -- Tab order that initially appears illogical may still meet this requirement due to an application-specific business logic. -- It may be useful to combine these tests with tests for keyboard navigation and visible focus. -- It may be useful to provide instructions about what "modal dialog boxes" are and how they should behave. - -### WCAG 2.2 Techniques - -The following sufficient techniques and/or common failures were considered when developing this test procedure for this baseline requirement: - -- [F55: Failure of Success Criteria 2.1.1, 2.4.7, and 3.2.1 due to using script to remove focus when focus is received](https://www.w3.org/WAI/WCAG22/Techniques/failures/F55) -- [F85: Failure of Success Criterion 2.4.3 due to using dialogs or menus that are not adjacent to their trigger control](https://www.w3.org/WAI/WCAG22/Techniques/failures/F85) in the sequential navigation order -- [G59: Placing the interactive elements in an order that follows sequences and relationships within the content](https://www.w3.org/WAI/WCAG22/Techniques/general/G59) -- [G107: Using "activate" rather than "focus" as a trigger for changes of context](https://www.w3.org/WAI/WCAG22/Techniques/general/G107) -- [G149: Using user interface components that are highlighted by the user agent when they receive focus.](https://www.w3.org/WAI/WCAG22/Techniques/general/G149) -- [G165: Using the default focus indicator for the platform so that high visibility default focus indicators will carry over](https://www.w3.org/WAI/WCAG22/Techniques/general/G165) -- [G195: Using an author-supplied, highly visible focus indicator](https://www.w3.org/WAI/WCAG22/Techniques/general/G195) -- [SCR26: Inserting dynamic content into the Document Object Model immediately following its trigger element](https://www.w3.org/WAI/WCAG22/Techniques/client-side-script/SCR26) - - diff --git a/_baselines/web-baselines/03FocusOrder.md b/_baselines/web-baselines/03FocusOrder.md deleted file mode 100644 index 87c32d73..00000000 --- a/_baselines/web-baselines/03FocusOrder.md +++ /dev/null @@ -1 +0,0 @@ -# The Focus Order test has been merged into [Baseline Test 2. Focus](../02FocusVisible) diff --git a/_baselines/web-baselines/03Noninterference.md b/_baselines/web-baselines/03Noninterference.md index 0d58b651..ec0935b8 100644 --- a/_baselines/web-baselines/03Noninterference.md +++ b/_baselines/web-baselines/03Noninterference.md @@ -3,44 +3,24 @@ title: "3. Non-Interference (Web)" order-number: 4 toc-group: baseline-web banner-title: "Baseline for Web" +source: Web --- ## 3. Non-Interference -### Accessibility Requirements + +{% include baseline-segments/acc-reqs/03-noninterference-acc-reqs.md %} -- [WCAG Conformance Requirement 5: Non-Interference](https://www.w3.org/WAI/WCAG22/Understanding/conformance#conf-req5) -- The following success criteria apply to all content on the page, including content that is not otherwise relied upon to meet conformance, because failure to meet them could interfere with any use of the page: - - 1.4.2 - Audio Control, - - 2.1.2 - No Keyboard Trap, - - 2.3.1 - Three Flashes or Below Threshold, and - - 2.2.2 - Pause, Stop, Hide. + +{% include baseline-segments/test-method-rationales/03-noninterference-tmr.html %} -### Test Method Rationale + +{% include baseline-segments/lim-assmpt-except/03-noninterference-lae.md %} -The test results for SC's 1.4.2 (Baseline Test 21.D-AudioControl), 2.1.2 (1.B-NoKeyboardTrap), 2.3.1 (9.A-Flashes), and 2.2.2 (21.B-MovingInfo and 21.C-AutoUpdate) determine the result of this baseline test. + +{% include baseline-segments/tests/3A-noninterference.html %} -### Limitations, Assumptions, or Exceptions + +{% include baseline-segments/advisory/03-noninterference-adv.html %} -None. - -### 3.A Test Procedure for Non-Interference - -**Baseline Test ID:** 3.A-NonInterference -#### Identify Content -Results for Baseline Tests 21.D-AudioControl, 1.B-NoKeyboardTrap, 9.A-Flashes, 21.B-MovingInfo and 21.C-AutoUpdate.
- -#### Test Instructions -If any of the above checks fail, then Baseline Requirement 3.A-NonInterference fails.
- -### Advisory: Tips for streamlined test processes - -- This test result is a logical AND of the identified SC's. All must pass for this test result to pass. -- A reporting tool may be utilized to generate the result for Conformance Requirement 5. - -### WCAG 2.2 Techniques - -Not Applicable. + +{% include baseline-segments/wcag-techs/03-noninterference-wcag.md %} diff --git a/_baselines/web-baselines/04RepetitiveContent.md b/_baselines/web-baselines/04RepetitiveContent.md index 6cf05c32..d084676f 100644 --- a/_baselines/web-baselines/04RepetitiveContent.md +++ b/_baselines/web-baselines/04RepetitiveContent.md @@ -3,97 +3,30 @@ title: "4. Repetitive Content (Web)" order-number: 5 toc-group: baseline-web banner-title: "Baseline for Web" +source: Web --- ## 4. Repetitive Content -### Accessibility Requirements + +{% include baseline-segments/acc-reqs/04-repetitivecontent-acc-reqs.md %} -- [WCAG SC 2.4.1 Bypass Blocks](https://www.w3.org/WAI/WCAG22/Understanding/bypass-blocks) -- A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. -- [WCAG SC 3.2.3 Consistent Navigation](https://www.w3.org/WAI/WCAG22/Understanding/consistent-navigation) -- 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. -- [WCAG 3.2.4 Consistent Identification](https://www.w3.org/WAI/WCAG22/Understanding/consistent-identification) -- Components that have the same functionality within a set of Web pages are identified consistently. + +{% include baseline-segments/test-method-rationales/04-repetitivecontent-tmr.html %} -### Test Method Rationale + +{% include baseline-segments/lim-assmpt-except/04-repetitivecontent-lae.md %} -To enable equitable use by keyboard-only users, there must be a keyboard-accessible method to bypass repetitive content, with no additional tools required. A common method used to bypass repetitive content is internal (same page) links, but other methods such as a hide menu option and a navigation tree are acceptable. Repeated content is also evaluated for consistent relative order. + +{% include baseline-segments/tests/4A-bypassblocks.html %} -### Limitations, Assumptions, or Exceptions -* Small sections, such as repeated individual words, phrases, or single links are not considered blocks for the purposes of this Baseline Requirement. -* Most web browsers provide keyboard shortcuts to move the user focus to the top of the page or browser, so providing a "skip" link may be unnecessary if a set of navigation links is at the bottom of a web page. -* [Same relative order](https://www.w3.org/TR/WCAG22/#dfn-same-relative-order) is the same position relative to other items. 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. -* Consistent text alternatives for interface components that perform the same function are not always truly “identical.” This is acceptable if they follow a consistent format. For instance, in the use of a graphical arrow at the bottom of a Web page that links to the next Web page, the text alternative may be: “Go to page 4.” However, the same arrow image on the next page should then state "Go to page 5." -* "Navigational mechanisms" as referenced in SC 3.2.3 includes both interactive and non-interactive components repeated on pages. Consistent presentation and layout benefit users who interact with repeated content within a set of Web pages and need to locate specific information or functionality more than once. -* This baseline test covers bypass methods that are functional with just a keyboard. The following WCAG Sufficient Techniques, which require additional assistive tools to function as bypass methods, were not included: - - [ARIA11: Using ARIA landmarks to identify regions of a page](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA11) - - [H69: Providing heading elements at the beginning of each section of content](https://www.w3.org/WAI/WCAG22/Techniques/html/H69) + +{% include baseline-segments/tests/4B-consistentnavigation.html %} -### 4.A Test Procedure for Bypass Blocks + +{% include baseline-segments/tests/4C-consistentidentification.html %} -**Baseline Test ID:** 4.A-BypassBlocks -#### Identify Content -Blocks of content that are repeated on multiple pages, including navigation links, page headers, and banners.
+ +{% include baseline-segments/advisory/04-repetitivecontent-adv.html %} -#### Test Instructions -If any of the above checks fail, then Baseline Test 4.A-BypassBlocks fails.
- -### 4.B Test Procedure for Consistent Navigation - -**Baseline Test ID:** 4.B-ConsistentNavigation -#### Identify Content -Navigational mechanisms that are repeated on multiple pages (which may or may not be contained within a block of content).
- -#### Test Instructions -If any of the above checks fail, then Baseline Test 4.B-ConsistentNavigation fails.
- -### 4.C Test Procedure for Consistent Identification - -**Baseline Test ID:** 4.C-ConsistentIdentification -#### Identify Content -Components that have the same functionality within a set of Web pages.
- -#### Test Instructions -If any of the above checks fail, then Baseline Test 4.C-ConsistentIdentification fails.
- -### Advisory: Tips for streamlined test processes - -- Some bypass methods may require a specific keyboard shortcut (i.e., the F6 key is the browser default for navigating between frames). -- If bypass method is provided but cannot be activated by keyboard, this is also a failure of Baseline Test 1.A Keyboard Access. -- If bypass method is in the focus order but is not visible when it has keyboard focus, this is a failure of Baseline 2.1 Focus Visible. -- If there is a need for multiple bypass methods on a page, each method must describe its purpose to comply with Baseline 14.A Links. For example, a page with repetitive links should have a descriptive bypass method. If there is also a block of repetitive content, this should have a separate descriptive bypass method. - -### WCAG 2.2 Techniques - -The following sufficient techniques and/or common failures were considered when developing this test procedure for this baseline requirement: - -- [F31: Failure of Success Criterion 3.2.4 due to using two different labels for the same function on different Web pages within a set of Web pages](https://www.w3.org/WAI/WCAG22/Techniques/failures/F31) -- [G1: Adding a link at the top of each page that goes directly to the main content area](https://www.w3.org/WAI/WCAG22/Techniques/general/G1) -- [G61: Presenting repeated components in the same relative order each time they appear](https://www.w3.org/WAI/WCAG22/Techniques/general/G61) -- [G123: Adding a link at the beginning of a block of repeated content to go to the end of the block](https://www.w3.org/WAI/WCAG22/Techniques/general/G123) -- [G124: Adding links at the top of the page to each area of the content](https://www.w3.org/WAI/WCAG22/Techniques/general/G124) -- [G197: Using labels, names, and text alternatives consistently for content that has the same functionality](https://www.w3.org/WAI/WCAG22/Techniques/general/G197) -- [G202: Ensuring keyboard control for all functionality](https://www.w3.org/WAI/WCAG22/Techniques/general/G202) -- [H70: Using frame elements to group blocks of repeated material](https://www.w3.org/WAI/WCAG22/Techniques/html/H70) **AND** [H64: Using the title attribute of the frame and iframe elements](https://www.w3.org/WAI/WCAG22/Techniques/html/H64) -- [SCR28: Using an expandable and collapsible menu to bypass block of content](https://www.w3.org/TR/WCAG20-TECHS/SCR28.html) + +{% include baseline-segments/wcag-techs/04-repetitivecontent-wcag.md %} diff --git a/_baselines/web-baselines/05Controls.md b/_baselines/web-baselines/05Controls.md index e13ed8c4..aec58704 100644 --- a/_baselines/web-baselines/05Controls.md +++ b/_baselines/web-baselines/05Controls.md @@ -3,131 +3,33 @@ title: "5. User Controls (Web)" order-number: 6 toc-group: baseline-web banner-title: "Baseline for Web" +source: Web --- ## 5. User Controls -### Accessibility Requirements + +{% include baseline-segments/acc-reqs/05-controls-acc-reqs.md %} -- [WCAG2 SC 4.1.2 Name, Role, Value](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value): For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. + +{% include baseline-segments/test-method-rationales/05-controls-tmr.html %} -### Test Method Rationale + +{% include baseline-segments/lim-assmpt-except/05-controls-lae.md %} -The purpose of this Baseline test is to check the following accessibility properties of user controls: -- Name -- Role -- State -- Value + +{% include baseline-segments/tests/5A-controlname.html %} -### Limitations, Assumptions, or Exceptions + +{% include baseline-segments/tests/5B-controlrole.html %} -- [User interface component](https://www.w3.org/TR/WCAG22/#dfn-user-interface-components) is a part of the content that is perceived by users as a single control for a distinct function. User interface components include form elements and links as well as components generated by scripts. This test uses the term "user controls" for brevity. -- The accessibility properties of the user control must be correct if the user control changes. -- Per [WCAG 2.2 Understanding SC 1.4.1 Use of Color](https://www.w3.org/WAI/WCAG22/Understanding/use-of-color) authors cannot set the visited state of links. The anchor element does not include a "visited" attribute; therefore the author has no ability to alter the state through an attribute setting. Exclude visited/unvisited state of links from this Baseline test. -- [Widget Roles of Accessible Rich Internet Applications (WAI-ARIA)](https://www.w3.org/TR/wai-aria/#widget_roles) lists roles that may be used for user controls. A "widget" is a "discrete user interface object with which the user can interact. Widgets range from simple objects that have one value or operation (e.g., check boxes and menu items), to complex objects that contain many managed sub-objects (e.g., trees and grids)." -- [Widget Attributes of Accessible Rich Internet Applications (WAI-ARIA)](https://www.w3.org/TR/wai-aria/#attrs_widgets) lists state and property attributes for user interface elements found on GUI systems or in rich internet applications which receive user input and process user actions. These attributes are used to support the widget roles. The WAI ARIA specification explains "the values of properties (such as aria-labelledby) are often less likely to change throughout the application life-cycle than the values of states (such as aria-checked) which may change frequently due to user interaction." -- In the Baseline Test instructions, where an ARIA role is identified, it is the first valid ARIA role attribute value. + +{% include baseline-segments/tests/5C-controlstate.html %} -### 5.A Test Procedure for Control Name + +{% include baseline-segments/tests/5D-controlvalue.html %} -**Baseline Test ID:** 5.A-ControlName + +{% include baseline-segments/advisory/05-controls-adv.html %} -#### Identify Content - -- -Identify user controls for a distinct function. Exclude forms and links as these are covered by Baseline 10. Forms and Baseline 14. Links, respectively.
- -#### Test Instructions -inputinput controlsbutton elementinput type="image"If any of the above checks fail, then Baseline Test 5.A-ControlName fails.
- -### 5.B Test Procedure for Control Role - -**Baseline Test ID:** 5.B-ControlRole - -#### Identify Content -Identify user controls for a distinct function that have an explicit role attribute (role="[value]"). Examples include forms, links, and toggle controls.
If any of the above checks fail, then Baseline Test 5.B-ControlRole fails.
- -### 5.C Test Procedure for Control State - -**Baseline Test ID:** 5.C-ControlState - -#### Identify Content -Identify user controls for a distinct function that can be set by the user. Examples of such user controls include those that can be checked, expanded, hidden, and pressed. Exclude the visited/unvisited state of links.
- -#### Test Instructions -hidden, disabled, and the use of WAI-ARIA state attributes must be used correctly. [SC 4.1.2]If any of the above checks fail, then Baseline Test 5.C-ControlState fails.
- -### 5.D Test Procedure for Control Value - -**Baseline Test ID:** 5.D-ControlValue - -#### Identify Content -Identify controls that have a value that can be changed by a user. Examples include form fields and sliders.
- -#### Test Instructions -If any of the above checks fail, then Baseline Test 5.D-ControlValue fails.
- -### Advisory: Tips for streamlined test processes - -- Changes to controls may also include changes in color to convey information. If so, this test should check that the information is programmatically determinable. If color is used as the only visual means of conveying information (or changes in information), then the content would fail to meet SC 1.4.1 Use of Color (addressed in [Baseline 7. Sensory Characteristics]({{site.baseurl}}/web-baselines/07Sensory/)). -- The accessible name and accessible description of some user controls are tested in other Baseline tests, such as [Baseline 10. Forms]({{site.baseurl}}/web-baselines/10Forms/), [Baseline 14. Links]({{site.baseurl}}/web-baselines/14Links/). For user controls that have dedicated Baseline Tests, please map to those tests for accessible name instead of 5.A-ControlName. -- This test may require interaction with controls to assess changes in name, role, state, value. Interaction instructions such as a test plan may be helpful. - -### WCAG 2.2 Techniques -The following sufficient techniques and/or common failures were considered when developing this test procedure for this baseline requirement: -- [F20: Failure of Success Criterion 1.1.1 and 4.1.2 due to not updating text alternatives when changes to non-text content occur](https://www.w3.org/WAI/WCAG22/Techniques/failures/F20) + +{% include baseline-segments/wcag-techs/05-controls-wcag.md %} diff --git a/_baselines/web-baselines/06Images.md b/_baselines/web-baselines/06Images.md index 6d3d4659..cd97aa92 100644 --- a/_baselines/web-baselines/06Images.md +++ b/_baselines/web-baselines/06Images.md @@ -3,9 +3,39 @@ title: "6. Images (Web)" order-number: 7 toc-group: baseline-web banner-title: "Baseline for Web" +source: Web --- ## 6. Images + +{% include baseline-segments/acc-reqs/06-images-acc-reqs.md %} + + +{% include baseline-segments/test-method-rationales/06-images-tmr.html %} + + +{% include baseline-segments/lim-assmpt-except/06-images-lae.md %} + + +{% include baseline-segments/tests/6A-meaningfulimage.html %} + + +{% include baseline-segments/tests/6B-decorativeimage.html %} + + +{% include baseline-segments/tests/6C-captcha.html %} + + +{% include baseline-segments/tests/6D-imagetext.html %} + + +{% include baseline-segments/advisory/06-images-adv.html %} + + +{% include baseline-segments/wcag-techs/06-images-wcag.md %} + + diff --git a/_baselines/web-baselines/07Sensory.md b/_baselines/web-baselines/07Sensory.md index e5d4e6be..4fc58435 100644 --- a/_baselines/web-baselines/07Sensory.md +++ b/_baselines/web-baselines/07Sensory.md @@ -3,6 +3,7 @@ title: "7. Sensory Characteristics (Web)" order-number: 8 toc-group: baseline-web banner-title: "Baseline for Web" +source: Web --- ## 7. Sensory Characteristics @@ -109,6 +110,27 @@ The following sufficient techniques and/or common failures were considered when - [G182: Ensuring that additional visual cues are available when text color differences are used to convey information](https://www.w3.org/WAI/WCAG22/Techniques/general/G182) - [G205: Including a text cue for colored form control labels](https://www.w3.org/WAI/WCAG22/Techniques/general/G205) + +{% include baseline-segments/test-method-rationales/07-sensory-tmr.html %} + + +{% include baseline-segments/lim-assmpt-except/07-sensory-lae.md %} + + +{% include baseline-segments/tests/7A-color.html %} + + +{% include baseline-segments/tests/7B-sensorycharacteristics.html %} + + +{% include baseline-segments/tests/7C-audiblecues.html %} + + +{% include baseline-segments/advisory/07-sensory-adv.html %} + + +{% include baseline-segments/wcag-techs/07-sensory-wcag.md %} + diff --git a/_baselines/web-baselines/08Contrast.md b/_baselines/web-baselines/08Contrast.md index 4edfa1d5..d1dd0bef 100644 --- a/_baselines/web-baselines/08Contrast.md +++ b/_baselines/web-baselines/08Contrast.md @@ -3,6 +3,7 @@ title: "8. Contrast (Web)" order-number: 9 toc-group: baseline-web banner-title: "Baseline for Web" +source: Web --- ## 8. Contrast diff --git a/_baselines/web-baselines/09Flashing.md b/_baselines/web-baselines/09Flashing.md index d12cb9dd..802aff48 100644 --- a/_baselines/web-baselines/09Flashing.md +++ b/_baselines/web-baselines/09Flashing.md @@ -3,6 +3,7 @@ title: "9. Flashing (Web)" order-number: 10 toc-group: baseline-web banner-title: "Baseline for Web" +source: Web --- ## 9. Flashing diff --git a/_baselines/web-baselines/10Forms.md b/_baselines/web-baselines/10Forms.md index aa629223..f5991876 100644 --- a/_baselines/web-baselines/10Forms.md +++ b/_baselines/web-baselines/10Forms.md @@ -3,8 +3,9 @@ title: "10. Forms (Web)" order-number: 11 toc-group: baseline-web banner-title: "Baseline for Web" ---- -## 10. Forms +source: Web + --- + ## 10. Forms ### Accessibility Requirements diff --git a/_baselines/web-baselines/11PageTitles.md b/_baselines/web-baselines/11PageTitles.md index f289cc28..374dc631 100644 --- a/_baselines/web-baselines/11PageTitles.md +++ b/_baselines/web-baselines/11PageTitles.md @@ -3,6 +3,7 @@ title: "11. Page Titles (Web)" order-number: 12 toc-group: baseline-web banner-title: "Baseline for Web" +source: Web --- ## 11. Page Titles diff --git a/_baselines/web-baselines/12DataTables.md b/_baselines/web-baselines/12DataTables.md index a9bafb1c..f15042d2 100644 --- a/_baselines/web-baselines/12DataTables.md +++ b/_baselines/web-baselines/12DataTables.md @@ -3,6 +3,7 @@ title: "12. Tables (Web)" order-number: 13 toc-group: baseline-web banner-title: "Baseline for Web" +source: Web --- ## 12. Tables @@ -136,3 +137,16 @@ The following sufficient techniques were considered when developing this test pr - [H63: Using the scope attribute to associate header cells and data cells in data tables](https://www.w3.org/WAI/WCAG22/Techniques/html/H63) +{% include baseline-segments/advisory/12-datatables-adv.html %} + +{% include baseline-segments/test-method-rationales/12-datatables-tmr.html %} + +{% include baseline-segments/lim-assmpt-except/12-datatables-lae.md %} + +{% include baseline-segments/tests/12A-datatables-role.html %} +{% include baseline-segments/tests/12B-datatables-headerassoc.html %} +{% include baseline-segments/tests/12C-layouttable.html %} + +{% include baseline-segments/wcag-techs/12-datatables-wcag.md %} + + diff --git a/_baselines/web-baselines/13Structure.md b/_baselines/web-baselines/13Structure.md index 3a656e43..223f326a 100644 --- a/_baselines/web-baselines/13Structure.md +++ b/_baselines/web-baselines/13Structure.md @@ -3,6 +3,7 @@ title: "13. Content Structure (Web)" order-number: 14 toc-group: baseline-web banner-title: "Baseline for Web" +source: Web --- ## 13. Content Structure @@ -115,3 +116,19 @@ The following sufficient techniques and/or common failures were considered when - [G130: Providing descriptive headings](https://www.w3.org/WAI/WCAG22/Techniques/general/G130) - [H42: Using <h1> to <h6> to identify headings](https://www.w3.org/WAI/WCAG22/Techniques/html/H42) - [H48: Using ol, ul and dl for lists or groups of links](https://www.w3.org/WAI/WCAG22/Techniques/html/H48) + +{% include baseline-segments/acc-reqs/13-structure-acc-reqs.md %} + +{% include baseline-segments/test-method-rationales/13-structure-tmr.html %} + +{% include baseline-segments/lim-assmpt-except/13-structure-lae.md %} + +{% include baseline-segments/tests/13A-headingdescriptive.html %} +{% include baseline-segments/tests/13B-visheadingprog.html %} +{% include baseline-segments/tests/13C-progheadingvisual.html %} +{% include baseline-segments/tests/13D-list.html %} + +{% include baseline-segments/advisory/13-structure-adv.html %} + +{% include baseline-segments/wcag-techs/13-structure-wcag.md %} + diff --git a/_baselines/web-baselines/14Links.md b/_baselines/web-baselines/14Links.md index 8ab6b59d..34ed8f68 100644 --- a/_baselines/web-baselines/14Links.md +++ b/_baselines/web-baselines/14Links.md @@ -3,6 +3,7 @@ title: "14. Links (Web)" order-number: 15 toc-group: baseline-web banner-title: "Baseline for Web" +source: Web --- ## 14. Links @@ -11,6 +12,13 @@ banner-title: "Baseline for Web" - [WCAG SC 2.4.4 Link Purpose (In Context)](https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-in-context) -- The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. - [WCAG2 SC 4.1.2 Name, Role, Value](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value): For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. +{% include baseline-segments/acc-reqs/14-links-acc-reqs.md %} +{% include baseline-segments/test-method-rationales/14-links-tmr.html %} +{% include baseline-segments/lim-assmpt-except/14-links-lae.md %} +{% include baseline-segments/tests/14A-linkpurpose.html %} +{% include baseline-segments/advisory/14-links-adv.html %} +{% include baseline-segments/wcag-techs/14-links-wcag.md %} + ### Test Method Rationale Links and buttons, including scripted elements, must have meaningful text (either directly associated or available in context) that describes their purpose or function. In order for associated text to be available to assistive technologies, the information must be determinable programmatically. diff --git a/_baselines/web-baselines/15Language.md b/_baselines/web-baselines/15Language.md index 327ea3c5..77c6ea18 100644 --- a/_baselines/web-baselines/15Language.md +++ b/_baselines/web-baselines/15Language.md @@ -3,6 +3,7 @@ title: "15. Language (Web)" order-number: 16 toc-group: baseline-web banner-title: "Baseline for Web" +source: Web --- ## 15. Language diff --git a/_baselines/web-baselines/16AudioVideo.md b/_baselines/web-baselines/16AudioVideo.md index 9d7da5da..dab55ad2 100644 --- a/_baselines/web-baselines/16AudioVideo.md +++ b/_baselines/web-baselines/16AudioVideo.md @@ -3,6 +3,7 @@ title: "16. Audio-Only and Video-Only (Web)" order-number: 17 toc-group: baseline-web banner-title: "Baseline for Web" +source: Web --- ## 16. Audio-Only and Video-Only @@ -119,3 +120,18 @@ The following sufficient techniques and/or common failures were considered when - [G158: Providing an alternative for time-based media for audio-only content](https://www.w3.org/WAI/WCAG22/Techniques/general/G158) - [G159: Providing an alternative for time-based media for video-only content](https://www.w3.org/WAI/WCAG22/Techniques/general/G159) + +{% include baseline-segments/acc-reqs/16-audiovideo-acc-reqs.md %} + +{% include baseline-segments/test-method-rationales/16-audiovideo-tmr.html %} + +{% include baseline-segments/lim-assmpt-except/16-audiovideo-lae.md %} + +{% include baseline-segments/tests/16A-audioonlytranscript.html %} +{% include baseline-segments/tests/16B-videoonlyalt.html %} +{% include baseline-segments/tests/16C-audiomediaalt.html %} +{% include baseline-segments/tests/16D-videomediaalt.html %} + +{% include baseline-segments/advisory/16-audiovideo-adv.html %} + +{% include baseline-segments/wcag-techs/16-audiovideo-wcag.md %} diff --git a/_baselines/web-baselines/17SyncMedia.md b/_baselines/web-baselines/17SyncMedia.md index 1290e5d4..f6164c1f 100644 --- a/_baselines/web-baselines/17SyncMedia.md +++ b/_baselines/web-baselines/17SyncMedia.md @@ -3,6 +3,7 @@ title: "17. Synchronized Media (Web)" order-number: 18 toc-group: baseline-web banner-title: "Baseline for Web" +source: Web --- ## 17. Synchronized Media @@ -169,3 +170,21 @@ The following sufficient techniques and/or common failures were considered when - [G78: providing a second, user-selectable, audio track that includes audio descriptions](https://www.w3.org/WAI/WCAG22/Techniques/general/G78) - [G87: Providing closed captions](https://www.w3.org/WAI/WCAG22/Techniques/general/G87) - [G93: Providing open (always visible) captions](https://www.w3.org/WAI/WCAG22/Techniques/general/G93) + +{% include baseline-segments/acc-reqs/17-syncmedia-acc-reqs.md %} + +{% include baseline-segments/test-method-rationales/17-syncmedia-tmr.html %} + +{% include baseline-segments/lim-assmpt-except/17-syncmedia-lae.md %} + +{% include baseline-segments/tests/17A-mediaplayerccadcontrols.html %} +{% include baseline-segments/tests/17B-mediaplayercclevel.html %} +{% include baseline-segments/tests/17C-mediaplayeradlevel.html %} +{% include baseline-segments/tests/17D-captionsprerecorded.html %} +{% include baseline-segments/tests/17E-adprerecorded.html %} +{% include baseline-segments/tests/17F-captionslive.html %} +{% include baseline-segments/tests/17G-syncmediaalternative.html %} + +{% include baseline-segments/advisory/17-syncmedia-adv.html %} + +{% include baseline-segments/wcag-techs/17-syncmedia-wcag.md %} diff --git a/_baselines/web-baselines/18Stylesheet.md b/_baselines/web-baselines/18Stylesheet.md index 5e6f87b2..e077cb4d 100644 --- a/_baselines/web-baselines/18Stylesheet.md +++ b/_baselines/web-baselines/18Stylesheet.md @@ -3,47 +3,28 @@ title: "18. CSS Positioning (Web)" order-number: 19 toc-group: baseline-web banner-title: "Baseline for Web" +source: Web --- ## 18. CSS Positioning -### Accessibility Requirements + +{% include baseline-segments/acc-reqs/18-meaningfulcontent-acc-reqs.md %} -- [WCAG SC 1.3.2 Meaningful Sequence](https://www.w3.org/WAI/WCAG22/Understanding/meaningful-sequence) -- When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. + +{% include baseline-segments/test-method-rationales/18-csspositioning-tmr.html %} -### Test Method Rationale + +{% include baseline-segments/lim-assmpt-except/18-csspositioning-lae.md %} -Meaningful information provided solely through CSS content may not be in the Document Object Model (DOM). Equivalent information must be available without CSS. + +{% include baseline-segments/tests/18A-meaningful-background-image.html %} -### Limitations, Assumptions, or Exceptions + +{% include baseline-segments/tests/18B-csspositionedcontent.html %} -- Only the CSS techniques identified as Failures in WCAG 2.0 Level A and Level AA are included in this test. There may be other CSS techniques that affect conformance. -- Inline styling is included in this test. + +{% include baseline-segments/advisory/18-csspositioning-adv.html %} -### 18.A for Test Procedure for Meaningful Background Image -CSS background image is now covered under [Baseline 6.B Test Procedure for Images with empty text alternatives]({{site.baseurl}}/web-baselines/06Images/#6b-test-procedure-for-images-with-an-empty-text-alternative). - -### 18.B Test Procedure for CSS Positioned Content - -**Baseline Test ID:** 18.B-CSSPositionedContent -#### Identify Content -Meaningful content positioned with CSS
- -#### Test Instructions -If any of the above checks fail, then Baseline Test 18.B-CSSPositionedContent fails.
- -### Advisory: Tips for streamlined test processes -- These tests are not to be performed by disabling all CSS. Content is not required to be perceivable and operable with all CSS disabled. - -### WCAG 2.2 Techniques - -The following sufficient techniques and/or common failures were considered when developing this test procedure for this baseline requirement: - -- [F1: Changing the meaning of content by positioning information with CSS](https://www.w3.org/WAI/WCAG22/Techniques/failures/F1) -- [G57: Ordering the content in a meaningful sequence](https://www.w3.org/WAI/WCAG22/Techniques/general/G57) + +{% include baseline-segments/wcag-techs/18-csspositioning-wcag.md %} diff --git a/_baselines/web-baselines/19Frames.md b/_baselines/web-baselines/19Frames.md index d9770286..cfcf3a08 100644 --- a/_baselines/web-baselines/19Frames.md +++ b/_baselines/web-baselines/19Frames.md @@ -3,63 +3,27 @@ title: "19. Frames and iFrames (Web)" order-number: 20 toc-group: baseline-web banner-title: "Baseline for Web" +source: Web --- ## 19. Frames and iFrames -### Accessibility Requirements + +{% include baseline-segments/acc-reqs/19-frames-acc-reqs.md %} -- [WCAG SC 4.1.2 Name, Role, Value](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value) -- For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. + +{% include baseline-segments/test-method-rationales/19-frames-tmr.html %} -### Test Method Rationale -While users with vision can recognize the structure presented by frames and iframes, users without vision rely on programmatic elements to determine their content. This test method determines the adequacy of the code to describe the contents of any `` or `