Get the latest tech news
How Chrome Accessibility Works
This document explains the technical details behind Chrome accessibility code by starting at a high level and progressively adding more levels of detail. Please read the accessibility overview first.
Examples of standard toolkits would be Win32 UI controls or .NET components on Windows, or Cocoa NSViews on macOS, or Android Views via Java or Kotlin. So if you add a button, checkbox, scroll container, or text field to your application, you don’t need to do any work to make it accessible - the built-in UI toolkit has provided all of that already. In addition to setting properties such as the name and role (like ComboBox on Windows, or Choice on Android), we'd want to override any methods that are used to walk the tree, in order to give this object accessible children - one for each option the user can pick.
Or read this on Hacker News