2.4.6 Headings and Labels (AA)

Headings and labels describe topic or purpose.

this doesn't mandate the use of headings and labels … only that if a page uses headings and labels, they must be descriptive.

it also doesn't mandate that headings and labels be correctly marked-up - that's the job of 1.3.1 Info and Relationships and (where it affects "accessible name" of controls) 4.1.2 Name, Role, Value.

lastly, if labels aren't there, it's a 3.3.2 Labels or Instructions problem.

3.3.2 Labels or Instructions (A)

Labels or instructions are provided when content requires user input.

again, this doesn't mandate that labels be marked-up as <label> and properly associated with form controls - that's covered by 1.3.1 Info and Relationships and (where it affects "accessible name" of controls) 4.1.2 Name, Role, Value.

2.1.1 Keyboard (A)

All functionality of the content is operable through a keyboard interface […]

doesn't say anything about which keys are needed to operate controls/functionality

1.3.3 Sensory Characteristics (A)

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.

this only relates specifically to instructions … and not whether or not sensory characteristics are used for content - this is covered by other SCs, like 1.4.1 Use of Color or even 1.1.1 Non-Text Content.

Fixes for Understanding 1.3.3 Sensory Characteristics #767

1.4.1 Use of Color (A)

Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

both lines contain a link. but only in the first line is colour used.

the first cases fails 1.4.1 Use of Color, but the second passes

auditors pondering failing the previous example for not using colour …

1.3.1 Info and Relationships (A)

Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

auditors pondering failing the previous example for not conveying things through presentation …

3.1.1 Language of Page (A)

The default human language of each Web page can be programmatically determined.

3.1.2 Language of Parts (AA)

The human language of each passage or phrase in the content can be programmatically determined […]

if you can't determine the language of the page, then you also can't determine the language of each passage or phrase.

fail one, and you automatically fail the other …

2.4.4 Link Purpose (In Context) (AA)

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 […]

what counts as "programmatically determined link context"? do preceding headings count?

2.4.7 Focus Visible (AA)

Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.

but what does visible mean? it's not normatively defined…

1.4.11 Non-text Contrast (AA)

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 […]
• Graphical Objects: […]

2.4.11 Focus Not Obscured (Minimum) (AA)

When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.

classic example: sticky header …

this passes 2.4.11 Focus Not Obscured (Minimum) (AA)

but how far can we take the "not entirely hidden" aspect?

arguably … not entirely hidden
(but is the focus indicator part of the component? wcag/issues/3529)

1.4.1 Use of Color (A)

Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

if your focus indication just changes colour, 1.4.1 likely applies

If content is conveyed through the use of colors that differ not only in their hue, but that also have a significant difference in lightness, then this counts as an additional visual distinction, as long as the difference in relative luminance between the colors leads to a contrast ratio of 3:1 or greater.

used to be buried in technique F73, now in understanding for 1.4.1 (#1500)

beware: if you look hard enough, everything is a use of color.

is it essential for conveying information or just eye candy?

1.4.10 Reflow (AA)

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

[…]

to help low vision users. should ideally have been "use responsive design"

instead, it was watered down to 400% zoom on a 1280×1024 display … and now only normatively applies at those exact values

1.4.12 Text Spacing (AA)

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 […]:

• 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

[…]

only those exact values and over

do you test the "at least" part here, and up to which values?

what if user changes just a few (e.g. just letter spacing)

this bookmarklet didn't work to change text styles … can I fail this?

no you can't … the SC doesn't care if a user can or can't change the metrics, or if a particular bookmarklet or method doesn't work.

only that if the metrics are indeed changed, then content doesn't become unreadable or unusable.

Understanding 1.4.12: clarify the intent and author responsibility #1687

3.3.8 Accessible Authentication (Minimum) (AA)

A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process […]

2.5.8 Target Size (Minimum) (AA)

The size of the target for pointer inputs is at least 24 by 24 CSS pixels […]

at first glance, the SC defines a minimum target size (it says so in the title)

2.5.8 Target Size (Minimum) (AA)

The size of the target for pointer inputs is at least 24 by 24 CSS pixels except where:

• Spacing: Undersized targets (those less than 24 by 24 CSS pixels) are positioned so that if a 24 CSS pixel diameter circle is centered on the bounding box of each, the circles do not intersect another target or the circle for another undersized target

…

the first exception turns this into Target Spacing (Minimum)

3.2.6 Consistent Help (A)

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 order relative to other page content, unless a change is initiated by the user […]:

the understanding document goes in depth listing and explaining help mechanisms, but the SC doesn't actually require any help mechanisms to be present at all …

relative order here means just means a consistent "focus/reading order"

"If the help item is visually in a different location, but in the same serial order, that is not helpful from a user's point of view, but it would not fail this criterion."