Communicating Your Final Product

Communicating with posters and other final handins

Jennifer Mankoff

2025-03-10

Announcements

Learning Goals

  • Announcements

  • VPATS

  • Group Work

  • Handin Expectations

  • Communication

Quick Reminder

Link to these slides:

  • Turn on captioning
  • Turn on recording

Reminders

  • Final report up
  • Final poster spec up

Slight changes to final report

  • Required README with your code repository so we can run your code
  • As a standard good practice, comment your code
  • Provide a VPAT table
  • Required: include your final accessibility audit (based on your final code) with yoru final handin

Plan for This Week

  • I’m traveling; no office hours tomorrow
  • No class; work on your projects
  • Audits due on Wednesday

VPATS

Learning Goals

  • Announcements

  • VPATS

  • Group Work

  • Handin Expectations

  • Communication

Transparency is key

A VPAT is truthful

Doesn’t mean everything is accessible

Level of compliance

  • Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
  • Partially Supports: Some functionality of the product does not meet the criterion.
  • Does Not Support: The majority of product functionality does not meet the criterion.
  • Not Evaluated: The product has not been evaluated against the criterion. This can only be used in WCAG Level AAA criteria.

Not Applicable Vs Supports

A response may use ‘Supports’ where one might otherwise be inclined to use ‘Not Applicable’.

This is in keeping with WCAG 2.0 Understanding Conformance.

This means that if there is no content to which a success criterion applies, the success criterion is satisfied.

Explanation

When the conformance level is ‘Partially Supports’ or ‘Does Not Support’, the remarks should identify:

  1. The functions or features with issues
  2. How they do not fully support

If the criterion does not apply, explain why.

If an accessible alternative is used, describe it.

VPAT Table

Criteria Conformance Level Brief Explanation
1.4.4 (Resize Text)
1.4.10 (Reflow)
2.4.3 (Focus Order)
4.1.2 (name, role, value)
… (based on WCAG beginner’s guide reading)

Group Work

Learning Goals

  • Announcements

  • VPATS

  • Group Work

  • Handin Expectations

  • Communication

Importance of Gratitude

Working together can be both rewarding and hard

You can’t know what everyone in your group is going through

Expressing thanks is a critical practice to successful group work

Gratitude Exercise

Consider yourself

  • Write down something you are thankful for in your life

Consider each individual in your team (and your mentor). For each person

  • Write down something you are grateful for each of your team mates & mentor

Share it here We’ll collect it as anonymous feedback.

Handin Expectations

Learning Goals

  • Announcements

  • VPATS

  • Group Work

  • Handin Expectations

  • Communication

Accessible Posters

See DO-IT’s guide for a complete list of expectations

  • Try to minimize text
  • Make sure all images you include are clear and legible; Use high-resolution images or vector graphics when possible
  • Use a relevant and consistent color scheme
  • Keep in mind whether the font and color contrast will be visible when the poster is printed.
  • Provide a QR code next to each image that provides ALT text for that image.

Other Notes

  • Make your poster source accessible as well (ALT text; etc)
  • Upload source and pdf to canvas by Friday (ideal, helps Aaleyah print them!); Sunday latest
  • Share poster with your mentor

Poster text size

Bigger is better! If you use smaller fonts, we will make a judgment call on readability. Ideally:

  • Title is 158 point
  • Section headings are 56 point
  • Body text is 36 point
  • Figure captions & footnotes are 24 point.

Poster contents

  • Project title; Group members; Mentor name and Class name
  • Client information (Include at least one quote)
  • LoFi Prototype pictures & learnings
  • Final Application screenshots & technical details
  • Justice-centered Design analysis
  • What you learned & suggested questions (“Ask me about…”)

Other poster Expectations

Will look at:

  • Quality of your setup,
  • How you introduce your project
  • The level of finish of your prototype (from from a technical standpoint and a design standpoint)
  • The level of finish of your poster (from a design standpoint)

Poster Session Audience

People from CREATE (UW CSE, HCDE, iSchool, mechanical engineering, etc)

You can invite your friends and family too! (We’ll send the zoom link and password shortly prior to the showcase).

Final Documentation (Gitlab)

This is where your accessible markdown goes

It should be separate from the README so we can run your codes

It should be accessible markdown (use of headers; alt text; etc)

Final Document Contents

Similar to poster

  • Introduction
  • Client Input
  • Final Concept including justice analysis

Communication

Learning Goals

  • Announcements

  • VPATS

  • Group Work

  • Handin Expectations

  • Communication

What is communication?

Telling a story

  • Short prepared speech
  • Includes “why” and “how”
  • Max 30 secs
  • Before saying something, ask yourself: What is this adding to the story?

Using your poster and prototype

  • Show, don’t just tell
  • Anecdotes, examples, quotes, etc all help
  • Think about who you are presenting to
  • You have a specific audience, what is their purpose?
  • Present accessibly

Presenting a poster accessibly

  • Similar to an Accessible talk (e.g. describe images)
  • Bring a notepad or printout and pen where attendees can write questions down
  • Allow time for communication challenges and share equally among visitors
  • Don’t expect people to read the poster
  • Allow people to ask questions when you’re not there (provide contact information or post it notes

In your team (~ 5 minutes)

  • Write down what your main need/problem was as you identified it from the initial user research.
  • How does your current prototype address this need? Discuss and write down 1-2 sentences explaining it.
    • If it doesn’t address the need (if you have pivoted), what need does your prototype address?
    • How could you still “sell” it to us and others? Does it perhaps address another need?

In your team (~ 10 minutes)

Write up a pitch that explains the need and how your prototype addresses it

No more than 30 seconds (>5 sentences). Ideally even shorter!

Start with the need/problem (you can add numbers, e.g., “More than 80% of CS students feel….”)

Red pen it! (Eliminate any unnecessary information, words, jargon etc)

Present to another team

Show off your pitch! (And collect feedback)

For all three parts, add your notes and pitch to the google doc (link in the chat)

Course Evaluation

This is a new course. We need your input! Please fill out the Course evaluation before you leave today.