Issues

• Target Size: Inline link adjacent to control

  2.5.8 Target Size (Minimum)
  w3c/wcag#5384 · Filter by author aardrian opened on Sep 29, 2026
  4

• Conforming Alternate Version (CAV) and the mechanism to reach/achieve it

  2.4.6 Headings and Labels3.3.2 Labels or instructionsConformance WCAG 2.xResponse-Only
  w3c/wcag#5373 · Filter by author patrickhlauke opened on Sep 23, 2026
  1

  

• "Are programming languages human languages?" and repercussions for text contrast requirements

  1.4.3 Contrast (Minimum)1.4.6 Contrast (Enhanced)
  w3c/wcag#5369 · Filter by author patrickhlauke opened on Sep 21, 2026
  1

• Distinguish theoretical backward compatibility from practical backward compatibility

  Response-OnlyWCAG 2.3
  w3c/wcag#5344 · Filter by author murata2makoto opened on Sep 2, 2026
  4

• ISO does not require abbreviation/initialism expansion

  w3c/wcag#5324 · Filter by author daniel-montalvo opened on Aug 25, 2026
  

• Update Understanding Success Criteria 1.4.8 Visual Presentation to clarify the purpose of the phrase "(aligned to both the left and the right margins)"

  1.4.8 Visual Presentationi18n
  w3c/wcag#5323 · Filter by author daniel-montalvo opened on Aug 25, 2026
  4

  

• Does the use of Summary and Details for an accordion pass 1.3.1?

  1.3.1 Info and RelationshipsResponse-Only
  w3c/wcag#5321 · Filter by author mbgower opened on Aug 24, 2026
  14

  

• What is considered 'functionality' in 1.4.10 Reflow

  w3c/wcag#5320 · Filter by author jake-abma opened on Aug 24, 2026

• 1.4.5 Move the note embedded in a paragraph to the standard styling

  w3c/wcag#5318 · Filter by author ljkoakley opened on Aug 20, 2026
  

• Clarification on WCAG 1.4.11 Non-Text Contrast – Updated Understanding Document Statement on Boundaries

  w3c/wcag#5304 · Filter by author Ashritha-98 opened on Aug 12, 2026

• Consider generalizing listing of autocomplete attributes for 1.3.5

  w3c/wcag#5288 · Filter by author scottaohara opened on Aug 7, 2026

• The procedure in F19 could be made more accurate

  Techniques
  w3c/wcag#5286 · Filter by author giacomo-petri opened on Aug 6, 2026

• F111 could be clarified and simplified

  Techniques
  w3c/wcag#5285 · Filter by author giacomo-petri opened on Aug 6, 2026

• The procedure in F108 does not account for the normative exceptions

  Techniques
  w3c/wcag#5284 · Filter by author giacomo-petri opened on Aug 6, 2026

• Step 2 of the procedure in F107 is ambiguous

  Techniques
  w3c/wcag#5283 · Filter by author giacomo-petri opened on Aug 6, 2026

• Editorial: step 3 of the procedure in F103 appears unnecessary

  EditorialTechniques
  w3c/wcag#5282 · Filter by author giacomo-petri opened on Aug 6, 2026

• F102 procedure should better align with the scope of 1.4.10

  Techniques
  w3c/wcag#5281 · Filter by author giacomo-petri opened on Aug 6, 2026

• F99 should use "user interface component" instead of "input"

  Techniques
  w3c/wcag#5280 · Filter by author giacomo-petri opened on Aug 5, 2026

• The wording "programmatically linked label" in F96 is ambiguous

  Techniques
  w3c/wcag#5279 · Filter by author giacomo-petri opened on Aug 5, 2026

• The procedure in F92 appears to be incomplete and internally inconsistent

  Techniques
  w3c/wcag#5278 · Filter by author giacomo-petri opened on Aug 5, 2026

• The procedure in F88 should acknowledge the availability of a mechanism to achieve the goal

  Techniques
  w3c/wcag#5277 · Filter by author giacomo-petri opened on Aug 5, 2026

• F75 could be simplified and clarified

  Techniques
  w3c/wcag#5274 · Filter by author giacomo-petri opened on Aug 5, 2026

• Editorial: the first step of the procedure in F72 could be removed

  EditorialTechniques
  w3c/wcag#5273 · Filter by author giacomo-petri opened on Aug 5, 2026

• The procedure in F65 is too implementation-specific

  Techniques
  w3c/wcag#5272 · Filter by author giacomo-petri opened on Aug 5, 2026

• The first step of the procedure in F63 is too restrictive

  Techniques
  w3c/wcag#5271 · Filter by author giacomo-petri opened on Aug 5, 2026