Upstream Tracking
APG Specification Updates
Tracking changes to the W3C ARIA Authoring Practices Guide and their reflection on this site.
1.4.11: Clarify the exemption "carries over" to UI components
The Understanding document for SC 1.4.11 Non-text Contrast was substantially reorganized, and now states normatively that when a graphic covered by the "essential" exception -- such as a logo -- also acts as a user interface component (e.g. a link or button), the exemption carries over to that component. It also notes, as a recommended practice, that authors should still provide another way to identify the component, and that other aspects of the criterion, such as a sufficiently contrasting focus indicator, remain required. No changes were needed to this site’s data.
3.2.4: Revise Understanding, clarify context-appropriate label differences are allowed
The Understanding document for SC 3.2.4 Consistent Identification was substantially rewritten. It clarifies that components with the same functionality don't need identical labels or icons -- contextual variation such as "Page 4" becoming "Previous page" (when viewed from page 5) is acceptable -- while using different icons for the same functionality is now listed as a new failure example, and buttons with different functions (such as separate "print receipt" / "print invoice" buttons) are explicitly out of scope. The PR states this does not change the criterion's normative meaning. No changes were needed to this site’s data.
1.3.5: Clarify whether the browser actually autofills is irrelevant
The Understanding document for SC 1.3.5 Identify Input Purpose now clarifies that whether a browser actually autofills a field is irrelevant to conformance -- what matters is whether the input’s purpose is programmatically determinable. It also notes that browsers autofilling via heuristics (rather than a programmatically exposed purpose) does not satisfy the criterion, and that autofill can be turned off in the browser while still exposing the purpose via the autocomplete attribute. No changes were needed to this site’s data.
1.4.3/1.4.6: Port the logo "author choice" exception to text contrast, add cross-reference to 1.4.11
The Understanding documents for SC 1.4.3 Contrast (Minimum) and 1.4.6 Contrast (Enhanced) now port over the "author choice" concept already introduced for Non-text Contrast (1.4.11): a logo presented with low contrast by the author's own choice, rather than because of brand guidelines, is not exempt. They also clarify that corporate identity or brand guidelines beyond the logo/logotype itself are not covered by the exception, and add a cross-reference noting that heavily stylized text or text used as symbols falls under 1.4.11's non-text content requirements instead. No changes were needed to this site’s data.
Summer 2026 editorial errata for WCAG 2.2 / 2.1 (1.4.13 exception wording, etc.)
The WCAG 2.2 and 2.1 errata now list the summer 2026 editorial corrections. The exception in SC 1.4.13 Content on Hover or Focus was reworded from content "controlled by" the user agent to content whose visual presentation is "determined by" the user agent. Other items replace an example in the definition of "process", unify "touch screen" as "touchscreen", and expand references to success criteria to their full short names. None of them change normative meaning. On this site, the wording of the exception in the 1.4.13 summary was aligned with the new phrasing.
PR #5176(opens in a new tab)Affected:tooltipF68: Rewrite the test procedure to rely on computed accessible names
The test procedure of failure technique F68 for SC 4.1.2 Name, Role, Value was rewritten. Instead of enumerating possible name sources such as label elements or aria-label, the procedure now checks in the browser’s accessibility tree that the computed accessible name is not empty. Its scope also broadened from input, textarea, and select elements to any user interface component exposed in the accessibility tree. The intent and title of F68 are unchanged, and no changes were needed to this site’s data.
G183: Rework to be purely about contrast ratio
Sufficient technique G183 for SC 1.4.1 Use of Color was reworked to be purely about maintaining a contrast ratio of at least 3:1 with surrounding text. The former wording about additional visual cues on hover was removed and the title was changed. The new title is reflected in this site’s techniques data.
2.5.1 / 2.5.7: Clarify one cannot be the alternative for the other
Notes were added to the Understanding documents for SC 2.5.1 Pointer Gestures and SC 2.5.7 Dragging Movements clarifying that a dragging movement cannot serve as the alternative for a path-based gesture, and vice versa. No changes were needed to this site’s data.
Reinstate G200 as advisory for 3.2.5
Technique G200 (opening new windows and tabs from a link only when necessary), once deleted, was reinstated as an advisory technique for SC 3.2.5 Change on Request with its inaccurate wording removed. G200 is included again in this site’s techniques data (also associated with SC 3.2.1 as advisory, matching the current primary sources).
1.4.4: Clarify UA-controlled text is not covered
A note was added to the Understanding document for SC 1.4.4 Resize Text: content whose text size is determined by the user agent or platform -- such as title-attribute tooltips or the platform file picker -- is not covered by this criterion. No changes were needed to this site’s data.
3.1.2: Clarify single words can be covered
A note was added to the Understanding document for SC 3.1.2 Language of Parts: phrases and passages consist of one or more words, so even an individual word can be covered unless it falls under an exception. This site’s summary already covers the exceptions, so no change was needed.
1.4.13: Rewrite the "Dismissible" explanation and clarify the two exemptions
The Understanding document for SC 1.4.13 Content on Hover or Focus rewrote the intent of the "Dismissible" condition from the perspective of screen-magnification users, and clarified the two exemptions: input error messages, and additional content that does not obscure meaningful content. No changes were needed to this site’s data.
PR #5175(opens in a new tab)Affected:tooltip2.4.7: Note that focus indicators are subject to 1.4.11
The Understanding document for SC 2.4.7 Focus Visible now explains that focus indicators are generally non-text content (e.g. borders or outlines) and are therefore also subject to SC 1.4.11 Non-text Contrast, with a cross-reference to the related section in Understanding 1.4.11. No changes were needed to this site’s data.
1.4.11: Add C40 as sufficient technique, reorganize by situation
C40 (two-color focus indicator) was added as a sufficient technique for SC 1.4.11 Non-text Contrast, and the technique list was reorganized by situation. Our association data will be regenerated once the change reaches the quickref.
3.1.2: Add explanation of "proper name" to Understanding
A non-normative explanation of what counts as a "proper name" -- an exemption in SC 3.1.2 Language of Parts -- was added to the Understanding document. This site’s summary already mentions the exemption, so no change was needed.
Tooltip: role="tooltip" to become name-prohibited
Due to ARIA spec changes, role="tooltip" is expected to become name-prohibited (cannot have an accessible name). This has not yet been reflected in the APG, but attention is needed for future impact.
1.4.11: Rewrite the boundaries explanation
The Understanding document for SC 1.4.11 Non-text Contrast rewrote its explanation of when visual boundaries are required, and added a failure example of an input with only a low-contrast border and placeholder text. No changes were needed to this site’s data.
3.2.2: Clarify button types in scope in Understanding
The Understanding document for SC 3.2.2 On Input now clarifies which button types are in or out of scope. No changes were needed to this site’s data.
2.5.4: Clarify camera pointing (e.g. QR codes) is out of scope
The Understanding document for SC 2.5.4 Motion Actuation now clarifies that pointing a device camera at an object such as a QR code does not count as motion actuation. No changes were needed to this site’s data.
4.1.3: Mention ariaNotify and add new technique ARIA27
The Understanding document for SC 4.1.3 Status Messages now mentions ariaNotify (notifications via accessibility APIs), and a new technique ARIA27 was added. ARIA27 is already included in this site’s techniques data.
PR #5079(opens in a new tab)Affected:alertAccordion: Remove arrow key and Home/End navigation from spec
Arrow key (Up/Down) and Home/End navigation between accordion headers has been removed from the APG pattern spec. Tab is now the only standard navigation method.
AlertDialog: Clarify aria-modal guidance
Guidance was added to explicitly set aria-modal="true" on alert dialogs. This site already follows this practice.
Keyboard Interface Practice: Clarify guidance on focusability of disabled controls
The "Developing a Keyboard Interface" practice revised its guidance on disabled controls: when discoverability matters, use aria-disabled="true" instead of the HTML disabled attribute to keep controls focusable while conveying the disabled state. Toolbar buttons and grids were added as examples.
PR #3387(opens in a new tab)Affected:grid, listbox, menu-menubar, tabs, toolbar, tree-viewDialog Modal: Change sample heading level from H2 to H1
The title element in dialog sample code was changed from <h2> to <h1>. This reflects the principle that dialogs are independent contexts where heading levels can be reset.
Grid: Fix arrow key behavior description
The description of left/right arrow key behavior when cells contain focusable elements was corrected to match the actual specification.
PR #3356(opens in a new tab)Affected:gridKeyboard Interface Practice: Add note on focus management for pointer activation
A note was added to the "Developing a Keyboard Interface" practice: when focus moves via pointer interactions such as click or tap, roving tabindex and aria-activedescendant must be updated just as with keyboard interactions. This guidance applies to all composite widgets using these techniques.