Grouping Guidelines and Outcomes by End User Categories

[Svenje7]

Individuals in multidisciplinary teams are responsible for meeting different parts of the accessibility standard. WCAG3 should be specific about each individual’s responsibility. For example, visual designers may be responsible for outcomes concerned with the visual elements of content, and developers are concerned with those related to the underlying code.

Guidelines and outcomes should therefore indicate to which responsibility (role) they belong to. This could be done using tags.

The tags can also be used for filtering, e.g.: a visual designer can filter all relevant guidelines and outcomes and hide the others.

The different responsibilities (roles) should be kept not too granular, e.g.:

• Visual designer
• Developer
• Content editor

[chaals]

I support making an effort at this through tagging. I think your point about not making it too granular is important, because the divisions in a large team providing operating instructions for a chain of supermarkets are likely to be very different in a team of 2 who produce a weekly employee newsletter and podcast for the same supermarket chain, let alone a sole trader managing a promotional website for their legal advice service (to pick two examples I've looked at today).