katekalcevich
commented
2 months ago We have similar feedback at Fable (Elana Chapman, Amber Knabl and myself) around UI terms used in the WCAG 3.0 draft. I'll add them here instead of opening a new issue so they are all in one place.
Specific to 3.3.2.2 Test scopes, we recommend using more common terms to describe the UI, for example: Instead of User processes say Task flows. Instead of Items say Elements. Instead of Views (described as pages or screens or modals / all content available) say Content. Instead of defining a Product as all the views, say "a product or service that is primarily based on digital technology."
Language is one of the reasons WCAG is challenging to understand and our feedback here is to use terms that we and our customers commonly use to describe their products instead of creating new, unfamiliar terms for the UI.
This may be an effort to be more platform agnostic, but we don't feel our recommendations are platform specific.
Summary: User processes = task flows Items = elements Views = content Product = a product or service that is primarily based on digital technology
The Abstract explains that WCAG 3.0 covers web content in a variety of situations including XR, but the Introduction says "web content and apps", section 1.3 says "web content and applications", and several guidelines mention "the website or app".
Web content can, and does, appear in all of these contexts, and will almost certainly appear in contexts we have yet to imagine, so restricting things to "websites", "apps", and "applications" doesn't seem to cover today's use cases, and almost certainly won't be future-proof against tomorrow's use cases.
Perhaps refering to "content" and "interfaces" or "user interfaces offers a simpler, more consistent, and more future-proof option?"