fixed broken links

This commit is contained in:
2025-12-23 21:04:52 -05:00
parent 2bd947dfe5
commit deed72cfba
91 changed files with 261 additions and 261 deletions
+34 -34
View File
@@ -8,57 +8,57 @@ User interface components and navigation must be operable.
Make all functionality available from a keyboard.
- [2.1.1 Keyboard](2.1.1-keyboard.md) — 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. (Level A)
- [2.1.2 No Keyboard Trap](2.1.2-no-keyboard-trap.md) — 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. (Level A)
- [2.1.3 Keyboard (No Exception)](2.1.3-keyboard-no-exception.md) — All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. (Level AAA)
- [2.1.4 Character Key Shortcuts](2.1.4-character-key-shortcuts.md) — If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true: (Level A)
- [2.1.1 Keyboard](2.1.1-keyboard.html) — 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. (Level A)
- [2.1.2 No Keyboard Trap](2.1.2-no-keyboard-trap.html) — 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. (Level A)
- [2.1.3 Keyboard (No Exception)](2.1.3-keyboard-no-exception.html) — All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. (Level AAA)
- [2.1.4 Character Key Shortcuts](2.1.4-character-key-shortcuts.html) — If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true: (Level A)
### 2.2 Enough Time
Provide users enough time to read and use content.
- [2.2.1 Timing Adjustable](2.2.1-timing-adjustable.md) — For each time limit that is set by the content, at least one of the following is true: (Level A)
- [2.2.2 Pause, Stop, Hide](2.2.2-pause-stop-hide.md) — For moving, blinking, scrolling, or auto-updating information, all of the following are true: (Level A)
- [2.2.3 No Timing](2.2.3-no-timing.md) — Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events. (Level AAA)
- [2.2.4 Interruptions](2.2.4-interruptions.md) — Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency. (Level AAA)
- [2.2.5 Re-authenticating](2.2.5-re-authenticating.md) — When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating. (Level AAA)
- [2.2.6 Timeouts](2.2.6-timeouts.md) — Users are warned of the duration of any user inactivity that could cause data loss, unless the data is preserved for more than 20 hours when the user does not take any actions. (Level AAA)
- [2.2.1 Timing Adjustable](2.2.1-timing-adjustable.html) — For each time limit that is set by the content, at least one of the following is true: (Level A)
- [2.2.2 Pause, Stop, Hide](2.2.2-pause-stop-hide.html) — For moving, blinking, scrolling, or auto-updating information, all of the following are true: (Level A)
- [2.2.3 No Timing](2.2.3-no-timing.html) — Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events. (Level AAA)
- [2.2.4 Interruptions](2.2.4-interruptions.html) — Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency. (Level AAA)
- [2.2.5 Re-authenticating](2.2.5-re-authenticating.html) — When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating. (Level AAA)
- [2.2.6 Timeouts](2.2.6-timeouts.html) — Users are warned of the duration of any user inactivity that could cause data loss, unless the data is preserved for more than 20 hours when the user does not take any actions. (Level AAA)
### 2.3 Seizures and Physical Reactions
Do not design content in a way that is known to cause seizures or physical reactions.
- [2.3.1 Three Flashes or Below Threshold](2.3.1-three-flashes-or-below-threshold.md) — Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds. (Level A)
- [2.3.2 Three Flashes](2.3.2-three-flashes.md) — Web pages do not contain anything that flashes more than three times in any one second period. (Level AAA)
- [2.3.3 Animation from Interactions](2.3.3-animation-from-interactions.md) — Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or the information being conveyed. (Level AAA)
- [2.3.1 Three Flashes or Below Threshold](2.3.1-three-flashes-or-below-threshold.html) — Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds. (Level A)
- [2.3.2 Three Flashes](2.3.2-three-flashes.html) — Web pages do not contain anything that flashes more than three times in any one second period. (Level AAA)
- [2.3.3 Animation from Interactions](2.3.3-animation-from-interactions.html) — Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or the information being conveyed. (Level AAA)
### 2.4 Navigable
Provide ways to help users navigate, find content, and determine where they are.
- [2.4.1 Bypass Blocks](2.4.1-bypass-blocks.md) — A mechanism is available to bypass blocks of content that are repeated on multiple web pages. (Level A)
- [2.4.2 Page Titled](2.4.2-page-titled.md) — Web pages have titles that describe topic or purpose. (Level A)
- [2.4.3 Focus Order](2.4.3-focus-order.md) — 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. (Level A)
- [2.4.4 Link Purpose (In Context)](2.4.4-link-purpose-in-context.md) — 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. (Level A)
- [2.4.5 Multiple Ways](2.4.5-multiple-ways.md) — 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. (Level AA)
- [2.4.6 Headings and Labels](2.4.6-headings-and-labels.md) — Headings and labels describe topic or purpose. (Level AA)
- [2.4.7 Focus Visible](2.4.7-focus-visible.md) — Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA)
- [2.4.8 Location](2.4.8-location.md) — Information about the user's location within a set of web pages is available. (Level AAA)
- [2.4.9 Link Purpose (Link Only)](2.4.9-link-purpose-link-only.md) — A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general. (Level AAA)
- [2.4.10 Section Headings](2.4.10-section-headings.md) — Section headings are used to organize the content. (Level AAA)
- [2.4.11 Focus Not Obscured (Minimum)](2.4.11-focus-not-obscured-minimum.md) — When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content. (Level AA)
- [2.4.12 Focus Not Obscured (Enhanced)](2.4.12-focus-not-obscured-enhanced.md) — When a user interface component receives keyboard focus, no part of the component is hidden by author-created content. (Level AAA)
- [2.4.13 Focus Appearance](2.4.13-focus-appearance.md) — When the keyboard focus indicator is visible, an area of the focus indicator meets all the following: (Level AAA)
- [2.4.1 Bypass Blocks](2.4.1-bypass-blocks.html) — A mechanism is available to bypass blocks of content that are repeated on multiple web pages. (Level A)
- [2.4.2 Page Titled](2.4.2-page-titled.html) — Web pages have titles that describe topic or purpose. (Level A)
- [2.4.3 Focus Order](2.4.3-focus-order.html) — 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. (Level A)
- [2.4.4 Link Purpose (In Context)](2.4.4-link-purpose-in-context.html) — 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. (Level A)
- [2.4.5 Multiple Ways](2.4.5-multiple-ways.html) — 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. (Level AA)
- [2.4.6 Headings and Labels](2.4.6-headings-and-labels.html) — Headings and labels describe topic or purpose. (Level AA)
- [2.4.7 Focus Visible](2.4.7-focus-visible.html) — Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA)
- [2.4.8 Location](2.4.8-location.html) — Information about the user's location within a set of web pages is available. (Level AAA)
- [2.4.9 Link Purpose (Link Only)](2.4.9-link-purpose-link-only.html) — A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general. (Level AAA)
- [2.4.10 Section Headings](2.4.10-section-headings.html) — Section headings are used to organize the content. (Level AAA)
- [2.4.11 Focus Not Obscured (Minimum)](2.4.11-focus-not-obscured-minimum.html) — When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content. (Level AA)
- [2.4.12 Focus Not Obscured (Enhanced)](2.4.12-focus-not-obscured-enhanced.html) — When a user interface component receives keyboard focus, no part of the component is hidden by author-created content. (Level AAA)
- [2.4.13 Focus Appearance](2.4.13-focus-appearance.html) — When the keyboard focus indicator is visible, an area of the focus indicator meets all the following: (Level AAA)
### 2.5 Input Modalities
Make it easier for users to operate functionality through various inputs beyond keyboard.
- [2.5.1 Pointer Gestures](2.5.1-pointer-gestures.md) — All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential. (Level A)
- [2.5.2 Pointer Cancellation](2.5.2-pointer-cancellation.md) — For functionality that can be operated using a single pointer, at least one of the following is true: (Level A)
- [2.5.3 Label in Name](2.5.3-label-in-name.md) — For user interface components with labels that include text or images of text, the name contains the text that is presented visually. (Level A)
- [2.5.4 Motion Actuation](2.5.4-motion-actuation.md) — Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when: (Level A)
- [2.5.5 Target Size (Enhanced)](2.5.5-target-size-enhanced.md) — The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when: (Level AAA)
- [2.5.6 Concurrent Input Mechanisms](2.5.6-concurrent-input-mechanisms.md) — Web content does not restrict use of input modalities available on a platform except where the restriction is essential, required to ensure the security of the content, or required to respect user settings. (Level AAA)
- [2.5.7 Dragging Movements](2.5.7-dragging-movements.md) — All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author. (Level AA)
- [2.5.8 Target Size (Minimum)](2.5.8-target-size-minimum.md) — The size of the target for pointer inputs is at least 24 by 24 CSS pixels, except when: (Level AA)
- [2.5.1 Pointer Gestures](2.5.1-pointer-gestures.html) — All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential. (Level A)
- [2.5.2 Pointer Cancellation](2.5.2-pointer-cancellation.html) — For functionality that can be operated using a single pointer, at least one of the following is true: (Level A)
- [2.5.3 Label in Name](2.5.3-label-in-name.html) — For user interface components with labels that include text or images of text, the name contains the text that is presented visually. (Level A)
- [2.5.4 Motion Actuation](2.5.4-motion-actuation.html) — Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when: (Level A)
- [2.5.5 Target Size (Enhanced)](2.5.5-target-size-enhanced.html) — The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when: (Level AAA)
- [2.5.6 Concurrent Input Mechanisms](2.5.6-concurrent-input-mechanisms.html) — Web content does not restrict use of input modalities available on a platform except where the restriction is essential, required to ensure the security of the content, or required to respect user settings. (Level AAA)
- [2.5.7 Dragging Movements](2.5.7-dragging-movements.html) — All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author. (Level AA)
- [2.5.8 Target Size (Minimum)](2.5.8-target-size-minimum.html) — The size of the target for pointer inputs is at least 24 by 24 CSS pixels, except when: (Level AA)