Definition of view as agreed by a majority in yesterday's AGWG call - strong objection

I think the decision yesterday to go with your (in my view hard to 
understand) definition of "view" is a grave error that should be corrected.
I actually have a problem locating the exact wording: The minutes Ihave 
not been published yet, and the agenda does not link to the WCAG 3 
github discussion but to a longish Google docs file, In the githib 
discussion on views https://github.com/w3c/wcag3/discussions/286 I found 
the definition I believe has been presented and okayed by most:
*
An interface with a specific layout. If the layout includes at least one 
component that is used to change the content within the layout, that is 
part of the same view.*

That creates a big practical problem. In the evaluation of mobile apps, 
it should be possible to allocate conformance errors to particular views 
/ screens, i.e. where they occur, regardless of whether these views 
share elements like a navigation bar with other views. If we seriously 
say: if there is any element (such as such a nav bar) that all screens 
that share, then all these screens are lumped together in the same view, 
we end up amassing a broad range of issues under a single view, having 
to spell out in reporting to which screen of that monstrous view an 
issue belongs. That is not helpful. And if this turn leads to defining 
individual screens as components, i.e. components then being the actual 
units that are evaluated, you wonder what the aggregate of "view" is 
then good for. The only advantage would be to focus on the element(s) 
shared by all screens under that concept of a view (say, the navigation 
bar) but that I believe is not intended in the current definition.
>
> *From: *Katherine Eng <eng@access-board.gov>
> *Date: *Monday, 23 June 2025 at 15:50
> *To: *Alastair Campbell <alastair.campbell@thisisgain.com>, WCAG list 
> <w3c-wai-gl@w3.org>
> *Cc: *Daniel Montalvo Charameli <dmontalvo@w3.org>, Wilco Fiers 
> <wilco.fiers@deque.com>
> *Subject: *RE: REVIEWS and AGENDA - AGWG Meeting June 24th 2025
>
>
>  
>
> You don't often get email from eng@access-board.gov. Learn why this is 
> important <https://aka.ms/LearnAboutSenderIdentification>
>
>  
>
> Hi Alistair,
>
> ACT rules review is on the agenda tomorrow but neither ACT Task Force 
> co-facilitator will be available to join.
>
> There aren’t any unresolved comments on the PRs, but I can attend the 
> July 1 meeting if you want to have the ACT topic then.
>
> These are the ACT rules PRs:
>
>  1. Summary element has non-empty accessible name
>     <https://deploy-preview-335--wai-wcag-act-rules.netlify.app/standards-guidelines/act/rules/2t702h/proposed/>.
>
>     Comments on github PR 346
>     <https://github.com/w3c/wcag-act-rules/pull/346>.
>  2. Orientation of the page is not restricted using CSS transforms
>     <https://deploy-preview-335--wai-wcag-act-rules.netlify.app/standards-guidelines/act/rules/b33eff/>.
>     Comments on github PR 335
>     <https://github.com/w3c/wcag-act-rules/pull/335>.
>  3. [Don't merge] Set Element with role attribute has required states
>     and properties [4e8ab6] to approved by WilcoFiers · Pull Request
>     #334 · w3c/wcag-act-rules
>     <https://github.com/w3c/wcag-act-rules/pull/334>
>
> Thanks,
>
> Kathy
>
> *From:*Alastair Campbell <alastair.campbell@thisisgain.com>
> *Sent:* Sunday, June 22, 2025 11:36 AM
> *To:* WCAG list <w3c-wai-gl@w3.org>
> *Subject:* Re: REVIEWS and AGENDA - AGWG Meeting June 24th 2025
>
> Apologies, I was so focused on the agenda I forgot the date!
>
> The AGWG will be meeting on Tuesday, 24^th June  2025 at 11.00 AM 
> Eastern US (Length: up to 2 hours).
>
>
>     Agenda
>
>   * ACT rules for review
>
>       o Summary element has non-empty accessible name
>         <https://deploy-preview-335--wai-wcag-act-rules.netlify.app/standards-guidelines/act/rules/2t702h/proposed/>.
>         Comments ongithub PR 346
>         <https://github.com/w3c/wcag-act-rules/pull/346>.
>       o Orientation of the page is not restricted using CSS transforms
>         <https://deploy-preview-335--wai-wcag-act-rules.netlify.app/standards-guidelines/act/rules/b33eff/>.
>         Comments on github PR 335
>         <https://github.com/w3c/wcag-act-rules/pull/335>.
>
>   * Scheduling Approach Alternatives
>     https://github.com/w3c/wcag3/discussions/322
>
>       o We are aiming to pick a direction to include in the charter,
>         please try to review the options in advance of the meeting.
>
>   * Finalizing terminology
>     https://github.com/w3c/wcag3/discussions/286#discussioncomment-13531745
>
>       o There is an update to the view definition, which is to have
>         two conformance units!
>
>   * Subgroup work
>
> Please reply with regrets to group-ag-chairs@w3.org (only) if you 
> would normally attend this meeting.
>
> Meeting call-in and zoom information is at this non-public page: 
> https://www.w3.org/events/meetings/fad52978-dc63-4427-90b9-e64dd31b0566/#next
>
> IRC: https://webirc.w3.org/channel #ag
>
> Scribe list: https://www.w3.org/WAI/GL/wiki/Scribe_List
>

-- 
Detlev Fischer PhD
IAAP Web Accessibility Specialist (WAS)
DIAS GmbH (Testkreis is now part of DIAS GmbH)

Telefon: +49-40-43 18 75-25
Mobil: +49-157 57 57 57 45
E-Mail:fischer@dias.de

http://www.dias.de
Beratung, Tests und Schulungen für barrierefreie Websites