Web Accessibility to Digital Accessibility

Web Accessibility -> Digital Accessibility

The question: Do we want to change to "digital accessibility" in some supporting resources?

WCAG is increasingly being adopted for non-web ICT. WAI published WCAG2ICT. EN 301 549 adopted WCAG for web content, electronic documents, and non-web software, such as native mobile apps.
obviously "web" is blurry these days
"digital accessibility" more clearly covers "digital publishing" and many other things not necessarily/considered just "web", like online learning

SEO – is target audience for many of these resources searching for "web accessibility" rather than "digital accessibility"
W3C & WAI's stated scope is "web"

most of our material applies to web content, electronic documents, and non-web software, such as native mobile apps; not hardware. How does "digital accessibility" and "digital technology" work for that scope?

We could add something like:

Note that “web accessibility” and “websites” throughout this page include web and mobile applications and other digital technologies."

or

"Web" and "websites" throughout this page also applies to applications and other digital technology.

For some resources, we could change the title, and not try to change all instances of "web" throughout.
For some resources, we might not change the title, and still add the note.

Planning and Managing Web Accessibility -- fundamentally most of the content applies to other non-web. However "web" and "websites" is used throughout the resource, so a thorough change throughout would be some work.
Involving Users in Web Projects for Better, Easier Accessibility -- would be good to make this clearly broader than "web". Several of the uses of "web" are examples, so wouldn't need to change those. (Shawn might be able to do this under project work.)
Involving Users in Evaluating Web Accessibility -- would be good to make this clearly broader than "web". Quick skim looks light wouldn't be too much work to do it. (Shawn might be able to do this under project work.)
Developing Web Accessibility Presentations and Training probably -- assess with WAI-Guide Project work. Maybe leave as is for now? Or, change title and add the applies-to-other note, but not try to change throughout now.
WCAG2ICT Overview -- possibly something like "WCAG2ICT Overview for Digital Accessibility"?
Why Standards Harmonization is Essential to Web Accessibility -- yes, change web -> digital with rewrite. (not know since it's so old, don't want to trigger any appearance of updating)

Introduction to Web Accessibility – would be a significant change to do throughout the resource. Consider leaving title and adding applies-to-other note.
Video Introduction to Web Accessibility and W3C Standards -- not going to redo video! Could change title. Given it includes "W3C Standards", inclined to leave it.
Web Accessibility Perspectives: Explore the Impact and Benefits for Everyone -- not going to redo the videos. Examples are specific to web, yet most apply to digital.
Essential Components of Web Accessibility -- talks mostly about content, user agents/browsers, authoring tools.
Web Accessibility Evaluation Tools List
Selecting Web Accessibility Evaluation Tools
WCAG-EM Overview: Website Accessibility Conformance Evaluation Methodology
WCAG-EM Report Tool: Website Accessibility Evaluation Report Generator
Before and After Demonstration (BAD)

Accessibility Principles
How People with Disabilities Use the Web - overview
- Stories of Web Users
- Diverse Abilities and Barriers
- Tools and Techniques
Web Accessibility First Aid: Approaches for Interim Repairs
Developing Organizational Policies on Web Accessibility
Tips for Writing for Web Accessibility
Tips for Designing for Web Accessibility
Tips for Developing for Web Accessibility
Evaluating Web Accessibility Overview
Easy Checks - A First Review of Web Accessibility
Template for Accessibility Evaluation Reports
Using Combined Expertise to Evaluate Web Accessibility
Contacting Organizations about Inaccessible Websites
W3C Accessibility Standards Overview
WCAG Overview
Web Accessibility Tutorials -- ? probably leave because much of the content is very specific to web.