A useful overview of the new success criteria coming in WCAG 2.2 (though the author is quick to note that changes are still at least a little likely).
[I wouldn't normally copy such a large block of text, but as this is a Medium article I don't trust it to stay online.]
Goal: Keep the focused item visible
What to do: Ensure the item receiving keyboard focus is at least partially visible in the viewportGoal: Keep the focused item entirely visible
What to do: Ensure no content obstructs the item receiving keyboard focusGoal: Make it easier to spot the keyboard focus
What to do: Use a focus indicator of sufficient size and contrastGoal: Don’t rely on dragging for user actions
What to do: Provide a simple pointer alternative to any action that involves draggingGoal: Make controls easier to activate
What to do: Ensure targets meet a minimum size or have sufficient spacing around themGoal: Make it easier to find help and support
What to do: Consistently locate any user help that appears on multiple pagesGoal: Make it easier for users to complete multi-step processes
What to do: Don’t ask for the same information twice in the same sessionAccessible Authentication (Minimum)
Goal: Make logins possible with less mental effort
What to do: Don’t make people memorize or transcribe something in order to log inAccessible Authentication (Enhanced)
Goal: Make logins possible with less mental effort
What to do: Don’t make people recognize objects or personal information to log in