| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | AA | AB | AC | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Date | Who | SC # | SC Name | SC Normative Text | Clear language | Level | Applicable to mobile Web | Applicable to mobile Native | How | Remark | Discussions | Something else needed? | What? | |||||||||||||||
2 | appt.li/wcag | ||||||||||||||||||||||||||||
3 | 1.1 | Text Alternatives | Yes | Yes | |||||||||||||||||||||||||
4 | 1.2 | Time-based Media | ? | ? | |||||||||||||||||||||||||
5 | 1.3 | Adaptable | Yes | Yes | |||||||||||||||||||||||||
6 | 1.4 | Distinguishable | Yes | Yes | |||||||||||||||||||||||||
7 | 2.1 | Keyboard Accessible | |||||||||||||||||||||||||||
8 | 2.2 | Enough Time | |||||||||||||||||||||||||||
9 | 2.3 | Seizures and Physical Reactions | came across this tool. PEAT (Photosensitive Epilepsy Analyzer Tool) | ||||||||||||||||||||||||||
10 | 2.4 | Navigable | |||||||||||||||||||||||||||
11 | 2.5 | Input Modalities | |||||||||||||||||||||||||||
12 | 3 | Understandable | |||||||||||||||||||||||||||
13 | 3.1 | Readable | |||||||||||||||||||||||||||
14 | 3.2 | Predictable | |||||||||||||||||||||||||||
15 | 3.3 | Input Assistance | |||||||||||||||||||||||||||
16 | 4.1 | Compatible | |||||||||||||||||||||||||||
17 | 5.1 | Interpreting Normative Requirements | |||||||||||||||||||||||||||
18 | 5.2 | Conformance Requirements | |||||||||||||||||||||||||||
19 | 5.3 | Conformance Claims (Optional) | |||||||||||||||||||||||||||
20 | 5.4 | Statement of Partial Conformance - Third Party Content | |||||||||||||||||||||||||||
21 | 5.5 | Statement of Partial Conformance - Language | |||||||||||||||||||||||||||
22 | 2022-9-26 | MK/PS | 1.1.1 | Non-text Content | Provide text alternatives for non-text content that serves the same purpose. | A | Yes | Yes | iOS: accessibilityLabel Android: contentDescription | N/A | N/A | ||||||||||||||||||
23 | 2022-9-26 | MK/PS | 1.2.1 | Audio-only and Video-only (Prerecorded) | Provide a text alternative to video-only and audio-only content. | A | Yes | Yes | iOS: UITextView Android: ScrollView / TextView | N/A | N/A | ||||||||||||||||||
24 | PS | 1.2.2 | Captions (Prerecorded) | Provide captions for prerecorded videos with audio. | A | Yes | Yes, plus support the 'prefers captions' setting to automatically enable captions | Question: How it works on Web application? | |||||||||||||||||||||
25 | 2022-9-26 | MK | 1.2.3 | Audio Description or Media Alternative (Prerecorded) | Provide audio description or text transcript for videos with sound. | A | Yes | Yes | Transcript iOS: UITextView Android: ScrollView / TextView Audio Description iOS: via AVPlayer Android: via MediaPlayer | N/A | N/A | ||||||||||||||||||
26 | 2022-9-26 | MK | 1.2.4 | Captions (Live) | Provide captions for live videos with audio. | AA | Yes | Yes | iOS: via AVPlayer Android: Native iOS: Live Captions (beta) setting Question: How it works on Web application? | N/A | N/A | ||||||||||||||||||
27 | PS | 1.2.5 | Audio Description (Prerecorded) | Provide audio description for videos with sound. | AA | Yes | Yes, plus support the 'prefers audio description' setting to automatically enable audio description | ||||||||||||||||||||||
28 | PS | 1.2.6 | Sign Language (Prerecorded) | Sign language interpretation is provided for all prerecorded audio content in synchronized media. | AAA | Yes | Yes | No accessibility setting available as of today on iOS and Android | |||||||||||||||||||||
29 | PS | 1.2.7 | Extended Audio Description (Prerecorded) | Where pauses in foreground audio are insufficient to allow audio descriptions to convey the sense of the video, extended audio description is provided for all prerecorded video content in synchronized media. | AAA | Yes | Yes | ||||||||||||||||||||||
30 | PS | 1.2.8 | Media Alternative (Prerecorded) | An alternative for time-based media is provided for all prerecorded synchronized media and for all prerecorded video-only media. | AAA | Yes | Yes | ||||||||||||||||||||||
31 | PS | 1.2.9 | Audio-only (Live) | An alternative for time-based media that presents equivalent information for live audio-only content is provided. | AAA | Yes | Yes | ||||||||||||||||||||||
32 | 2022-9-26 | MK/PS | 1.3.1 | Info and Relationships | Content, structure and relationships can be programmatically determined. | A | Yes | Yes, but certain variations | MK: A lot of the specific call outs around tables, semantic coding, or tags for formatting/layout are not applicable to native. | ||||||||||||||||||||
33 | PS | 1.3.2 | Meaningful Sequence | When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. | A | Yes | Yes | ||||||||||||||||||||||
34 | PS | 1.3.3 | Sensory Characteristics | Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound. | A | Yes | Yes | Content related | |||||||||||||||||||||
35 | PS | 1.3.4 | Orientation | Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential. | AA | Yes | Yes | Mobile specific | MK: Most apps are built for one orientation. | ||||||||||||||||||||
36 | 2022-9-26 | MK/PS | 1.3.5 | Identify Input Purpose | Check that data entry fields collecting information about users include the definition of purpose using HTML5.2 autofill/autocomplete and appropriate values | AA | Yes | Yes, but certain variants | User ID & Passwords are supported in most cases with Face ID | MK: There's not reliable capabilities to replicate the HTML autocomplete attribute for form fields | JJ: Require setting the right keyboard type for apps? E.g. show numberic keyboard when inputting numbers, show e-mail keyboard when inputting e-mail address, etc. Joe: Checking out where the input attributes are stored on Android/iOS. Quintin: Taking security into account / maybe in future Android/iOS versions it will act differently | ||||||||||||||||||
37 | PS | 1.3.6 | Identify Purpose | In content implemented using markup languages, the purpose of user interface components, icons, and regions can be programmatically determined. | AAA | Yes | Yes | ||||||||||||||||||||||
38 | PS | 1.4.1 | Use of Color | Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. | A | Yes | Yes | ||||||||||||||||||||||
39 | PS | 1.4.2 | Audio Control | If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. | A | Yes | Yes | ||||||||||||||||||||||
40 | PS | 1.4.3 | Contrast (Minimum) | The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: Large Text Large-scale text and images of large-scale text have a contrast ratio of at least 3:1; Incidental Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement. Logotypes Text that is part of a logo or brand name has no contrast requirement. | AA | Yes | Yes, plus support the 'high contrast' setting to increase contrast | Reading Legibility | JJ: Support high contrast mode? | ||||||||||||||||||||
41 | 2022-09-19 | JJ | 1.4.4 | Resize Text | Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. | AA | Yes | Yes, but scaling works different compared to websites. | iOS: Dynamic Font Size -> https://developer.apple.com/design/human-interface-guidelines/foundations/typography#specifications Android: Scale-indepenent Pixels (sp) -> https://m3.material.io/styles/typography/type-scale-tokens | https://github.com/w3c/wcag2ict/issues/4#issuecomment-1148810084 | JJ: Like WCAG2ICT recommendation include 200% of body text instead of requiring headings to be rendered super large? | AK: Could we introduce the minimum sizes to be used during the design phase itself? | |||||||||||||||||
42 | 2022-10-10 | KP/SB/PS | 1.4.5 | Images of Text | If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: Customizable The image of text can be visually customized to the user's requirements; Essential A particular presentation of text is essential to the information being conveyed. | AA | Yes | Yes | Content related | ||||||||||||||||||||
43 | 2022-10-10 | KP/SB/PS | 1.4.6 | Contrast (Enhanced) | The visual presentation of text and images of text has a contrast ratio of at least 7:1, except for the following: Large Text Large-scale text and images of large-scale text have a contrast ratio of at least 4.5:1; Incidental Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement. Logotypes Text that is part of a logo or brand name has no contrast requirement. | AAA | Yes | Yes, plus support the 'high contrast' setting to increase contrast | Content related iOS: https://developer.apple.com/documentation/uikit/uiaccessibilitycontrast Android: https://stackoverflow.com/questions/34411712/detect-if-high-contrast-is-enabled-in-android-accessibility-settings | Web developers need to support mobile abilities. Documented on iOS not documented on android. | |||||||||||||||||||
44 | 2022-10-10 | KP/SB/PS | 1.4.7 | Low or No Background Audio | For prerecorded audio-only content that (1) contains primarily speech in the foreground, (2) is not an audio CAPTCHA or audio logo, and (3) is not vocalization intended to be primarily musical expression such as singing or rapping, at least one of the following is true: No Background The audio does not contain background sounds. Turn Off The background sounds can be turned off. 20 dB The background sounds are at least 20 decibels lower than the foreground speech content, with the exception of occasional sounds that last for only one or two seconds. | AAA | Yes | Yes | |||||||||||||||||||||
45 | 2022-10-10 | KP/SB/PS | 1.4.8 | Visual Presentation | For the visual presentation of blocks of text, a mechanism is available to achieve the following: Foreground and background colors can be selected by the user. Width is no more than 80 characters or glyphs (40 if CJK). Text is not justified (aligned to both the left and the right margins). Line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the line spacing. Text can be resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window. | AAA | Yes but certain variants | Yes | Mobile Web: Only the below criteria can be achieved- - Text size resize for upto 200% - Line Spacing (CSS/styling attributes) | Does small screens change this any? | |||||||||||||||||||
46 | 2022-10-10 | KP/SB/PS | 1.4.9 | Images of Text (No Exception) | Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed. | AAA | Yes | Yes | Content related | ||||||||||||||||||||
47 | PS | 1.4.10 | Reflow | Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for: Vertical scrolling content at a width equivalent to 320 CSS pixels; Horizontal scrolling content at a height equivalent to 256 CSS pixels. Except for parts of the content which require two-dimensional layout for usage or meaning. | AA | Yes but certain variants | Yes but certain variants | Mobile Web: It is not possible to comply all of this guideline as the web browser supports - pinch & zoom (text size enlarging) - Text size resizing option to 300% reflow (where this guideline targets up to 400%) Question: Will responsible applications satisfy this criteria? Mobile Native: The native A11y settings like 'Large Text size' works in the native applications, but not sure if the pixel specifications can be met accurate there | MK: I'm not so sure this is supported on native. AK: We are running an experiment to ensure reflow of the Grid to List when the font is scaled to 200%. CC: I don't think this applies to native AV: EN 301 549 considers it applicable to native. Not sure how to test it, except for the very specific case of apps offering a zoom feature. BITV in Germany offers a test for it https://bitvtest-de.translate.goog/pruefschritt/bitv-20-app/bitv-20-app-11-1-4-10-automatischer-umbruch-reflow?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=en&_x_tr_pto=wapp but mentions also a discussion about this in WCAG2ICT https://github.com/w3c/wcag2ict/issues/98 | ||||||||||||||||||||
48 | PS | 1.4.11 | Non-text Contrast | The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s): User Interface Components Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author; Graphical Objects Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed. | AA | Yes | Yes, but how do we interpret hover and focus on mobile? Yes, plus support the 'high contrast' setting to increase contrast | Mobile Native: The user can use keyboard along with mobile devices. But not sure how it interpret with Native application | |||||||||||||||||||||
49 | 2022-09-19 | JJ/PS | 1.4.12 | Text Spacing | In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property: Line height (line spacing) to at least 1.5 times the font size; Spacing following paragraphs to at least 2 times the font size; Letter spacing (tracking) to at least 0.12 times the font size; Word spacing to at least 0.16 times the font size. | AA | No | No, the mentioned properties are not user adjustable on mobile. | Text-style properties --> Support bold text, because it is a text-style property? JJ: Bold text is not mentioned in WCAG, it's just about spacing properties. AK: Link to the typrface properties | CC: I don't think this applies to mobile. AV: there is no user setting for this on native. | |||||||||||||||||||
50 | 2022-9-26 | MK KP/SB/PS | 1.4.13 | Content on Hover or Focus | Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true: Dismissible A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content; Hoverable If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing; Persistent The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid. Exception: The visual presentation of the additional content is controlled by the user agent and is not modified by the author. | AA | No | No | Don't use hover if keyboard is used. | The primary navigation on mobile is touch. Yet to see a specific trigger on keyboard focus and mobile isn't used (apart from iPad's now i believe) Keyboard on mobile should not implement however as part of a focus. Difficult on screen readers, people who are using external keywords and braille displays Issues are touch and screen real estate AV: even if it does not seem common, it can be tested. We test it with an external (bluetooth) keyboard and a mouse. | |||||||||||||||||||
51 | 2022-09-26 | JJ / PS | 2.1.1 | 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. | A | Yes | Yes | Support (at least) full keyboard access, screen reader, voice access, switch control | There are use cases of using wired or wireless keyboard plugged into the mobile device | |||||||||||||||||||
52 | PS | 2.1.2 | 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. | A | Yes | Yes | Question: How far the keyboard support for mobile devices (both web & native) | Question: How far the keyboard support for mobile devices (both web & native) | ||||||||||||||||||||
53 | 2.1.3 | Keyboard (No Exception) | All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. | AAA | |||||||||||||||||||||||||
54 | 2022-09-26 | MK | 2.1.4 | Character Key Shortcuts | 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: Turn off A mechanism is available to turn the shortcut off; Remap A mechanism is available to remap the shortcut to include one or more non-printable keyboard keys (e.g., Ctrl, Alt); Active only on focus The keyboard shortcut for a user interface component is only active when that component has focus. | Confirm keyboard shortcuts if used are active on focus only, can be disabled or remapped. | A | Yes | No JJ: I would say Yes for iOS | iOS: Use UIKeyCommand Android: no built-in support, can use key events | No technique for native apps to support keyboard shortcuts in the same way as desktop browsers JJ: iOS has UIKeyCommand which is native shortcut support | ||||||||||||||||||
55 | 2.2.1 | Timing Adjustable | For each time limit that is set by the content, at least one of the following is true: Turn off The user is allowed to turn off the time limit before encountering it; or Adjust The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or Extend The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or Real-time Exception The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or Essential Exception The time limit is essential and extending it would invalidate the activity; or 20 Hour Exception The time limit is longer than 20 hours. | A | Yes | Yes | |||||||||||||||||||||||
56 | 2022-10-10 | PS | 2.2.2 | Pause, Stop, Hide | For moving, blinking, scrolling, or auto-updating information, all of the following are true: Moving, blinking, scrolling For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and Auto-updating For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential. | A | Yes | Yes | For both Native & Browser Apps, the animation content will work the same way as desktop | ||||||||||||||||||||
57 | 2022-10-10 | PS | 2.2.3 | No Timing | 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. | AAA | Yes | Yes | For both Native & Browser Apps, the Timing functionalities will work the same way as desktop | ||||||||||||||||||||
58 | JJ | 2.2.4 | Interruptions | Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency. | AAA | Yes | Yes | Yes, take foreground/background state into account | |||||||||||||||||||||
59 | JJ | 2.2.5 | Re-authenticating | When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating. | AAA | Yes | Yes | Store auth tokens somewhere like UserDefaults / Preferences | |||||||||||||||||||||
60 | JJ | 2.2.6 | Timeouts | 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. | AAA | Yes | Yes | Local push notifications? Native/web logic? Think mobile can achieve this kind of behavior. | |||||||||||||||||||||
61 | JJ | 2.3.1 | Three Flashes or Below Threshold | 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. | A | Yes | Yes | ||||||||||||||||||||||
62 | 2.3.2 | Three Flashes | Web pages do not contain anything that flashes more than three times in any one second period. | AAA | |||||||||||||||||||||||||
63 | JJ | 2.3.3 | Animation from Interactions | Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or the information being conveyed. | AAA | Yes | Yes | Add a button, or use system preferences: iOS: Prefers reduced motion + UIView.setAnimationsEnabled(false) Android: windowAnimationStyle="@null" | Web developers need to support mobile settings. | ||||||||||||||||||||
64 | 2022-09-26 | JJ | 2.4.1 | Bypass Blocks | The mechanism available to skip repeated elements or blocks of text | A | Yes | Yes, assistive technologies should be able to bypass blocks, but it's different to Web | E.g. screen readers can navigate by heading, links, containers, etc. | AV: it is considered as non-applicable to native in EN 301 549 and Section 508 | The Section 508 standards for software list as an exception. However can still be done and could be merit in doing so. CC: We usually have tab bar navigations with 4-5 tabs for native and hamburger menus on mobile web. I don't think a bypass block is needed in those cases. | ||||||||||||||||||
65 | 2022-09-26 | MK | 2.4.2 | Page Titled | Web pages have titles that describe topic or purpose. | A | Yes | No: Specific to 'Web pages' but this would be useful for native apps as well. | Use a NavigationBar or Toolbar to display a Title | This SC is very specific to the HTML <title> element. | Not all screens need a visual title, so this should be optional but recommended. Or maybe this applies more to the name of the app? Because the intention of this SC is to recognize the Webpage inside your browser? Then, for native mobile, this applies more to the App name to recognize it in the App browser. iOS also has synonyms: https://developer.apple.com/documentation/sirikit/registering_custom_vocabulary_with_sirikit/specifying_synonyms_for_your_app_name | ||||||||||||||||||
66 | 2022-12-12 | MK | 2.4.3 | 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. | A | Yes | Yes | |||||||||||||||||||||
67 | 2022-10-10 | PS / MK | 2.4.4 | 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. | A | Yes | Yes | Links / buttons text used both in Native & Browser apps, it is required to write the links text in a way to understand its purpose visually and also with screen readers | ||||||||||||||||||||
68 | 2022-12-12 | MK | 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. | AA | Yes | The Section 508 standards (and EN 301 549) for software list as an exception. However can still be done and could be merit in doing so. | There are multiple ways to navigate in native apps, such as Search Navigation Menu (typically the hamburger menu),Tab panel navigation, Bottom tabbed navigation and Back buttons. There are likely exceptions where apps are small (e.g. just a dashboard view) and don't require multiple methods. | ||||||||||||||||||||
69 | 2022-10-10 | PS / MK | 2.4.6 | Headings and Labels | Headings and labels describe topic or purpose. | AA | Yes | Yes | |||||||||||||||||||||
70 | 2022-09-26 | JJ / MK | 2.4.7 | Focus Visible | Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. | A | Yes | No, keyboard focus indicator is not adjustable by apps. But colors are adjustable in focused state. | |||||||||||||||||||||
71 | 2022-12-12 | MK | 2.4.8 | Location | Information about the user's location within a set of Web pages is available. | AAA | Yes | Yes | Indicating current location within navigation bars | ||||||||||||||||||||
72 | 2022-12-12 | MK | 2.4.9 | Link Purpose (Link Only) | 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. | AAA | Yes | Yes | |||||||||||||||||||||
73 | 2023-01-23 | JJ | 2.4.10 | Section Headings | Section headings are used to organize the content. | AAA | Yes | Yes | |||||||||||||||||||||
74 | 2022-09-26 | JJ / MK | 2.4.11 | Focus Appearance | When the keyboard focus indicator is visible, one or both of the following are true: The entire focus indicator meets all the following: encloses the user interface component or sub-component that is focused, and has a contrast ratio of at least 3:1 between the same pixels in the focused and unfocused states, and has a contrast ratio of at least 3:1 against adjacent non-focus-indicator colors. An area of the focus indicator meets all the following: is at least as large as the area of a 1 CSS pixel thick perimeter of the unfocused component or sub-component, or is at least as large as a 4 CSS pixel thick line along the shortest side of the minimum bounding box of the unfocused component or sub-component, and has a contrast ratio of at least 3:1 between the same pixels in the focused and unfocused states, and has a contrast ratio of at least 3:1 against adjacent non-focus-indicator colors, or is no thinner than 2 CSS pixels. Exceptions: The focus indicator is determined by the user agent and cannot be adjusted by the author, or The focus indicator and the indicator's background color are not modified by the author. | AA | Yes | No, keyboard focus indicator is not adjustable by apps. But colors are adjustable in focused state. | MK: Can we determine if a focus indicator is adjustable in either Android or iOS? JJ: It is not adjustable by app developers. Users can adjust the color through system settings. | ||||||||||||||||||||
75 | 2022-09-26 | JJ / MK | 2.4.12 | Focus Not Obscured (Minimum) | When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content. | AAA | Yes | MK: Unsure if developement can control the keyboard focus indicators. | |||||||||||||||||||||
76 | 2022-12-12 | MK | 2.4.13 | Focus Not Obscured (Enhanced) | When a user interface component receives keyboard focus, no part of the focus indicator is hidden by author-created content. | AAA | Yes | MK: Unsure if developement can control the keyboard focus indicators. | |||||||||||||||||||||
77 | MK | 2.5.1 | Pointer Gestures | 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. | A | Yes | Yes | ||||||||||||||||||||||
78 | MK | 2.5.2 | Pointer Cancellation | For functionality that can be operated using a single pointer, at least one of the following is true: No Down-Event The down-event of the pointer is not used to execute any part of the function; Abort or Undo Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion; Up Reversal The up-event reverses any outcome of the preceding down-event; Essential Completing the function on the down-event is essential. | A | Yes | Yes | ||||||||||||||||||||||
79 | 2022-12-12 | MK | 2.5.3 | Label in Name | For user interface components with labels that include text or images of text, the name contains the text that is presented visually. | A | Yes | Yes | |||||||||||||||||||||
80 | MK | 2.5.4 | Motion Actuation | 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: Supported Interface The motion is used to operate functionality through an accessibility supported interface; Essential The motion is essential for the function and doing so would invalidate the activity. | A | Yes | Yes | ||||||||||||||||||||||
81 | 2022-09-26 | JJ / MK | 2.5.5 | Target Size (Enhanced) | The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when: Equivalent The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels; Inline The target is in a sentence or block of text; User Agent Control The size of the target is determined by the user agent and is not modified by the author; Essential A particular presentation of the target is essential to the information being conveyed. | AAA | Yes | Yes, but how do we convert 44 CSS pixels to mobile units? | |||||||||||||||||||||
82 | MK | 2.5.6 | Concurrent Input Mechanisms | 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. | AAA | Yes | Unsure if it would come up with native code, as in could developers limit interactions to touch only. Never came across it. | ||||||||||||||||||||||
83 | 2022-09-26 | JJ /MK | 2.5.7 | Dragging Movements | 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. | AA | Yes | Yes, but what if you use a native component and it does not have an alternative for dragging? | |||||||||||||||||||||
84 | 2022-09-26 | JJ / MK | 2.5.8 | Target Size (Minimum) | The size of the target for pointer inputs is at least 24 by 24 CSS pixels, except where: Spacing: The target offset is at least 24 CSS pixels to every adjacent target; Equivalent: The function can be achieved through a different control on the same page that meets this criterion. Inline: The target is in a sentence or block of text; User agent control: The size of the target is determined by the user agent and is not modified by the author; Essential: A particular presentation of the target is essential or is legally required for the information being conveyed; | AA | Yes | Yes, but how do we convert 24 CSS pixels to mobile units? | Use dp (Density-independent Pixels) on Android, pt on iOS, this also aligns with WCAG2ICT Physical size is different to include in guidance, but can be helpful to add Reference guidance from Apple / Google: 44x44 / 48x48 OR point to the 2.5.5 AAA requirement | ||||||||||||||||||||
85 | 2022-09-26 | MK | 3.1.1 | Language of Page | The default human language of each Web page can be programmatically determined | A | Yes | No | There is no method to test that a language is programmatically defined | ||||||||||||||||||||
86 | 2022-09-26 | MK | 3.1.2 | Language of Parts | The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. | AA | Yes | No | https://appt.org/en/guidelines/wcag/success-criterion-3-1-2 | There is no method to test that a language is programmatically defined | You can change the language of parts, but it's difficult to verifiy as a tester. Screen reader audio can be captured to determine. | ||||||||||||||||||
87 | 2022-12-12 | MK | 3.1.3 | Unusual Words | A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon. | AAA | Yes | Yes | |||||||||||||||||||||
88 | 2022-12-12 | MK | 3.1.4 | Abbreviations | A mechanism for identifying the expanded form or meaning of abbreviations is available. | AAA | Yes | Yes | |||||||||||||||||||||
89 | 2022-12-12 | MK | 3.1.5 | Reading Level | When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available. | AAA | Yes | Yes | Instructions, documentation | ||||||||||||||||||||
90 | 2022-12-12 | MK | 3.1.6 | Pronunciation | A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation. | AAA | Yes | Yes | |||||||||||||||||||||
91 | 2022-12-12 | MK | 3.2.1 | On Focus | When any user interface component receives focus, it does not initiate a change of context. | A | Yes | Yes - however very unlikely a change of content would happen | |||||||||||||||||||||
92 | 2022-12-12 | MK | 3.2.2 | On Input | Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. | A | Yes | Yes | |||||||||||||||||||||
93 | 2022-12-12 | MK | 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. | AA | Yes | The Section 508 standards for software list as an exception. However can still be done and could be merit in doing so. | Should discuss more | ||||||||||||||||||||
94 | 2022-12-12 | MK | 3.2.4 | Consistent Identification | Components that have the same functionality within a set of Web pages are identified consistently. | AA | Yes | The Section 508 standards for software list as an exception. However can still be done and could be merit in doing so. | Should discuss more | ||||||||||||||||||||
95 | 2023-01-23 | JJ | 3.2.5 | Change on Request | Changes of context are initiated only by user request or a mechanism is available to turn off such changes. | AAA | Yes | Yes | Program the logic somehow. | ||||||||||||||||||||
96 | 2022-09-26 | JJ | 3.2.6 | Consistent Help | If a web page contains any of the following help mechanisms, and those mechanisms are repeated on multiple web pages within a set of web pages, they occur in the same relative order to other page content, unless a change is initiated by the user: Human contact details; Human contact mechanism; Self-help option; A fully automated contact mechanism. | A | Yes | Yes | Place icon/button in a consistent place, e.g. in the navigation bar or sticky button at bottom of screen | ||||||||||||||||||||
97 | 2022-12-12 | KP | 3.3.1 | Error Identification | If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. | A | Yes | Yes | |||||||||||||||||||||
98 | 2022-12-12 | KP | 3.3.2 | Labels or Instructions | Labels or instructions are provided when content requires user input. | A | Yes | Yes | |||||||||||||||||||||
99 | 2022-12-12 | KP | 3.3.3 | Error Suggestion | If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. | AA | Yes | Yes | |||||||||||||||||||||
100 | 2022-12-12 | KP | 3.3.4 | Error Prevention (Legal, Financial, Data) | For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: Reversible Submissions are reversible. Checked Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. Confirmed A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission. | AA | Yes | Yes |