Although mobile usage by for example visually impaired might not speak to imagination, they might benefit the most from using a mobile device. Obviously, we all want to be able to independently go out and about, regardless of any impairment or disability.
As no-one is the same, such guidelines are needed (and often obligatory towards governmental organizations) as part of equal access and thus equal rights, regardless of the technology and thus device that is being used. The World Wide Web Consortium (you may know them as W3C) is describing Web Content Accessibility Guidelines 2.1 as following:
[it] defines how to make Web content more accessible to people with disabilities. Accessibility involves a wide range of disabilities, including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities.W3.org about WCAg 2.1
WCAG 2.1 guidelines
The difference with WCAG 2.0? WCAG 2.1 isn't new, it's an update compared to WCAG 2.0, which is also addressing the accessibility on mobile devices and thus the responsive version of your website. Rather have the guidelines in Dutch? My former employer Accessibility Foundation recently leaded the translation of the accessibility guidelines.
We are proud to present the official, authorized Dutch translation of the W3C WCAG 2.1 guidelinesAccessibility Foundation on Twitter
Screenreaders and browsers are always improving their software to improve the accessibility of websites. As developers we can do our part as well by letting such software know how to interprete a webpage and make your products, services and information even more accessible.