Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Defining views #46

Open
JJdeGroot opened this issue Aug 31, 2024 · 2 comments
Open

Defining views #46

JJdeGroot opened this issue Aug 31, 2024 · 2 comments
Labels
session Breakout session proposal track: UX

Comments

@JJdeGroot
Copy link
Member

JJdeGroot commented Aug 31, 2024

Session description

Defining what constitutes a view has been tried over the years. In this session, we will re-open the discussion.

Web page in WCAG 2.2

a non-embedded resource obtained from a single URI using HTTP plus any other resources that are used in the rendering or intended to be rendered together with it by a user agent

Views in WCAG 3

Views include all content visually and programmatically available without a substantive change. Conceptually, views correspond to the definition of a web page as used in WCAG 2, but are not restricted to content meeting that definition. For example, a view could be considered a “screen” in a mobile app or a layer of web content – such as a modal.

Interpretation of Web Terminology in a Non-web Context

A small number of success criteria are written to apply to “a set of web pages” or “multiple web pages” and depend upon all pages in the set to share some characteristic or behavior. Since the unit of conformance in WCAG 2 is a single web page, the task force agreed that the equivalent unit of conformance for non-web documents is a single document. It follows that an equivalent unit of evaluation for a “set of web pages” would be a “set of documents”. Since it isn't possible to unambiguously carve up non-web software into discrete pieces, a single “web page” was equated to a “software program” and a “set of web pages” was equated to a “set of software programs”.

Session goal

Getting closer to the definition of views

Additional session chairs (Optional)

No response

Who can attend

Anyone may attend (Default)

IRC channel (Optional)

#views

Other sessions where we should avoid scheduling conflicts (Optional)

No response

Instructions for meeting planners (Optional)

No response

Agenda for the meeting.

  1. Web page definition (WCAG 2.2)
  2. View definition (WCAG 3)
  3. Web page mapping (WCAG2ICT)
  4. Defining view

Links to calendar

Meeting materials

@JJdeGroot JJdeGroot added the session Breakout session proposal label Aug 31, 2024
@tpac-breakout-bot
Copy link
Collaborator

Thank you for proposing a session!

You may update the session description as needed and at any time before the meeting, but please keep in mind that tooling relies on issue formatting: follow the instructions and leave all headings and other formatting intact in particular. Bots and W3C meeting organizers may also update the description, to fix formatting issues or add links and other relevant information. Please do not revert these changes. Feel free to use comments to raise questions.

Do not expect formal approval; W3C meeting organizers endeavor to schedule all proposed sessions that are in scope for a breakout. Actual scheduling should take place shortly before the meeting.

@JJdeGroot
Copy link
Member Author

Meeting minutes: https://www.w3.org/2024/09/25-views-minutes.html

Slides: https://janjaap.com/tpac2024/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
session Breakout session proposal track: UX
Projects
Status: No status
Development

No branches or pull requests

3 participants