GreggVan
commented
11 months ago Grin
Yes it would Patrick
And we tried to figure out how to make the work in WCAG2ICT (the first one) and never could figure out how to define “VIEW” the term we used since what a persons sees changes ever time a toolbar is shown or hidden or moved or… and more
We finally gave us saying that we could not figure out any way to make it testable — since we couldn’t figure out how to define a VIEW in any stable fashion.
If you can figure that out — there are a lot of people on your side
As to your comment that being rooted in a Web Page means it doesn’t apply to software — that doesn’t grok.
Since most Web Apps are all at one URL — and WCAG therefore applies to that entire web app It would seem to apply to Apps (software) in exactly the same way it applies to web apps.
RE suite of software applications — if you look at the definition of “set of software’ you will find that that definition is indeed for a suite of software — but it is even more restrictive — with lots of additional conditions. If we changed it to simply “suite of software” then a MUCH wider range of software would be cooped up into having to comply - than is true with our current treatment. Software that would have a very difficult time conforming.
But good thoughts and let us know if you solve the VIEWs definition problem.
Best
Gregg
On Nov 13, 2023, at 2:36 PM, Patrick H. Lauke @.***> wrote:
Gathering the side conversation from #225 https://github.com/w3c/wcag2ict/issues/225 for discussion.
assuming that the discussion around "set of software" is an attempt to translate "sets of web pages" ... wouldn't a more apt adaptation be "sets of related views/screens" within the same piece of software?
seems to group came to the conclusion that this would not be possible due to the difficulty in defining what a view/screen in a complex software application may be, and that this is an issue that even WCAG when applied to web content struggled with (caused by the arguably outdated - these days - idea that a "web page" is characterised by having its unique URI/URL, which causes problems in old-style SPAs or similar that don't also dynamically modify the address when switching between views).
if the TF indeed translated "sets of web pages" to mean "sets of software" for WCAG2ICT here, and if so suggest that this may not necessarily make much sense
"set of web pages" [...] refers to subcomponents of a website as a whole that is the subject of an assessment, while "software" is the whole that is being assessed. this seems to make little sense, regardless of the mitigation of "it doesn't happen often".
My two primary suggestions from that discussion:
I would rather suggest that WCAG2ICT would outright state that because "set of web pages" is rooted on the concept of "web page", and that in turn is rooted on - per the definition - a resource available at a particular URL, the whole idea is not applicable to software at all since it has no concept of a URL. Rather than making an ill-fitting stretch to mean "set of software".
Or refer to "set of software applications within a suite of applications", assuming that the subject of an assessment is indeed the suite as a whole. This would then have the same effect of immediately NOT applying to cases where a single standalone application on its own is assessed...it would only apply to suites.
— Reply to this email directly, view it on GitHub https://github.com/w3c/wcag2ict/issues/261, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACNGDXTH3EVKZBLU5IBABETYEKOIJAVCNFSM6AAAAAA7J32X6WVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE4TCNRQGA3DSNY. You are receiving this because you are subscribed to this thread.
patrickhlauke
maryjom
Gathering the side conversation from https://github.com/w3c/wcag2ict/issues/225 for discussion.
seems to group came to the conclusion that this would not be possible due to the difficulty in defining what a view/screen in a complex software application may be, and that this is an issue that even WCAG when applied to web content struggled with (caused by the arguably outdated - these days - idea that a "web page" is characterised by having its unique URI/URL, which causes problems in old-style SPAs or similar that don't also dynamically modify the address when switching between views).
My two primary suggestions from that discussion:
noting that nowadays "suites" are few and far between (thinking back to the old days of mozilla which integrated a browser and a mail client.
whether the "within a set of web pages" SCs actually make much sense in the context of even a suite though is also debatable (e.g. whether they have a consistent navigation ... as it's possibly irrelevant whether they do or not, as they're different standalone software applications, so have different purposes - contrasted with the whole idea of "set of web pages" which indicates a much stronger relationship between the component web pages to form a single cohesive web site / section of a web site.
so my preference would actually be the first suggestion: outright stating that because the concept of "set of web pages" is rooted on "web page" meaning a unique URL, the whole idea does not translate to non-web ICT so the SCs are not applicable as written.