Button with the autofocus property

This demo is currently a work in progress.

Before getting into the technical details of the autofocus attribute, it is important to discuss how using the attribute can causes usability issues for all users. Whenever we do something automatically for users, it takes away their choice in the matter. This can be good in many instances! Reducing cognitive load is very important in accessibility. This process can look like:

Simplifying text content to be more readable and understandable
Reducing the number of actionable elements in a page or area of a page
Enabling users to personalize their experience

What it looks like less often is automating functionality. It is not possible to fully automate accessibility because every person is different and every disability or condition a person might have is typically on a spectrum and affects the person uniquely. There are some things that can and should be automated, but it is absolutely necessary to figure out if an automation makes something unusable for anyone before implementing it.

Some examples of good automation:

Designing forms to prevent mistakes: automatically fixing errors, allowing autocomplete, suggesting corrections on invalid inputs, etc.
Providing a login that does not rely on memory or other cognitive skills: automatic authentication on trusted devices, biometrics (fingerprints, retina scans, facial recognition), third-party auth, etc.
Providing reminders (only upon user request): allowing users to add reminders to their calendar and choose their reminder method and frequency.

Click this button to open an alert