Jump to content 
Important notes:

This page is archived information that is not up-to-date.

Information about EOWG closing is in the 19 September 2024 blog post: Accessibility education and outreach: Another milestone in W3C's 30-year history and evolution.

This Wiki page was edited by participants of the EOWG. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.

Definitions & Role Groups

From Education & Outreach

Parent document: https://www.w3.org/WAI/EO/wiki/Role-Based_Decision_Tree

NOTE
This document is deprecated and has been merged into the Roles Definition document.


“Question 1” Definitions & Discussion

Implementation

  • Focuses on the delivered code and decisions made first (and therefore owned) by Dev
    • Checkpoint ownership of implementation errors when provided accessible design requirements
    • Success criteria ownership of new projects where implementation or code is the introduction point (example: Meeting SC4.1.1 Parsing is almost completely dependent on the delivered code and cannot be tested before)
  • Does not cover decisions provided as requirements by other groups, most specifically Design

Design

Focuses on user experience and presentation decisions including

  • Success criteria ownership design decisions of new projects that can/should be provided to developers (before starting implementation)
  • Checkpoint ownership of issues that are unclear from design or requirements, or dependent on non-code issues (such as color selection) found during testing of delivered code (or existing product)
  • Ownership covers (by role)
    • Visual Presentation (Vx, possibly UX)
      • Color selection (Vx)
      • Decorative elements (Vx)
      • Text selection, size and spacing (Vx)
      • Layout
    • Data Visualization (UX and Vx)
      • Charts
      • Graphs
    • Structure (UX)
    • Semantics (UX, possibly CA)
    • Features (UX)

Content

  • Success criteria ownership content in new projects that should be provided to developers (before starting implementation)
    • Can include existing taxonomy, lexicon or writing standards
  • Checkpoint ownership of issues that are not unclear from design or dependent on non-code issues (such as specific terminology, instructions, translations)
    • New standards for previously missing terminology guidelines
    • Providing new or edited content necessary because of changes to site contents, presentation, or operation

Covers mainly textual information presented as

  • Short text (such as)
    • Labels for links, fields and buttons
    • Instructions
    • Taxonomy of terms used (example: "Sign in" or "Log in")
  • Long text (lengthy body copy) such as
    • Legal documents (e.g., terms and conditions, privacy policy)
    • Includes scripted content (for media production)
      • Audio
      • Video
      • Animations
      • Transcripts for all of the above
  • Corrections
    • Typos, grammar errors
    • Translation errors (including both language codes and content text)

Covers Content Images and Graphics - emphasis on text alternatives and descriptions (chosen with Vx Designer) Examples:

  • Clip art
  • Photographs
  • Illustrations

Implementation (Role Group)

Dev (FED or Front-End Developer) Role

Front End Code Implementation

  • Web-based
    • HTML
    • CSS
    • JavaScript
    • Acrobat
    • Flash
  • Native
    • Android
      • Java
      • Kotlin
      • C#, C, C++
    • iOS
      • Objective C, C
      • X-code
      • Swift

Does not include:

  • Functional or Semantic Design [Design (UX)]
    • Interaction requirements
    • Semantic page structure
  • Authored content:
    • Body copy (small or large)
    • Time-based media (video or audio content)
  • Visual Presentation
    • Colors
    • Fonts
    • Images

Deliverables

  • HTML
  • CSS
  • JavaScript
  • Server configuration

Design (Role Group)

Vx (Visual) Design Role

Presentation-Specific Decisions

  • Colors
  • Font selections and style
  • Final images

Deliverables

  • Style Guides
  • Page Comps (composites, final design)
  • Image files

UX (User Experience) Designer Role

User Experience Design Decisions

  • Usability
  • Site, page and functional interaction
    • Detailed feature definition and operation
    • Page structure
  • Site semantics
    • Page element semantic specification
      • Header
      • Main
      • Footer
      • Navigation
      • Asides

Deliverables

  • Wireframes
  • Requirements
  • Usability Reports
  • Interface Guidelines


CA (Content Author / Design) Role

Content Authoring Decisions

  • Short text
    • Control titles
    • Field labels
    • Short descriptions or non-text content
  • Long text
    • Body copy
    • Long descriptions of non-text content
  • Time Based Media
    • Scripted content for video and audio
    • Extended audio description
Deliverables
  • Copy, text, managed content
  • Taxonomy (if used)
  • Writing guidelines
  • Scripts
  • Media files

Business (Role Group)

Biz (Business Owner) Role

Biz Design Decisions

  • Budget for design and implementation
  • Core Features (high level, budget)
    • Multiple language support
    • Site search
    • Infrastructure budget
  • Formal Site Requirements
    • Legal, Financial, Data
    • Session timeout
    • Other security requirements (e.g., CAPTCHA)
  • Branding (high level)
    • Brand book and guidelines (typically at corporate, not site/product level)
Retrieved from "https://www.w3.org/WAI/EO/wiki/index.php?title=Definitions_%26_Role_Groups&oldid=29764"