Over the years, Drupal has taken some great steps forward to achieve web accessibility through several of its major releases and is one of the leading implementations of the web accessibility standards. With web accessibility being one of the major factors contributing to the user interface and the ability of a business to reach the maximum audience, several strategic initiatives for Drupal core is sure to shape the future of how people interact with a website. Some of the noteworthy ones include: Application-like interfaces and various UI interactions that are presented without full-page refreshes: sliding panels, autofocus, live result filters, drag-and-drop, pop-up success messages, live previews,wizard-like progress steps, and role impersonation. Drupal bot Automated accessibility testing using headless browser drivers. Supporting more interaction modes, such as MS Windows’ high-contrast mode, and speech-driven control. End-user testing for accessibility The theme component library initiative which involves much refactoring of how Drupal produces output.
Source: Why We Love Web Accessibility With Drupal 8 : Why You Should Care Too | Specbee – Enterprise E-Commerce & Customized Drupal Solutions
What It Means to be Drupal Adjacent One of the major objectives of Drupal 8 is the desire to “get off the island.†Drupal opened its doors to using and contributing to a broader ecosystem of projects instead of replicating functionality in Drupal. We now see tools like Twig and various Symfony components in Core. Contributed modules are also able to integrate projects and Software Development Kits (SDKs). For example, Password Strength, Digital Ocean, and Hubspot API integrate through Drupal’s native use of Composer. This philosophy helps those of us that more closely identify as “Drupal Adjacent.â€
