Serve IT · Jan 2024 to May 2024 · Case study
City of BloomingtonTester · I wrote what I would change
City of Bloomington Serve IT work, Jan to May 2024. I tested the paths residents use, then turned the friction into recommendations. Public access starts with making the next action understandable.
Who it is for: residents, including keyboard and screen-reader users. What I did: tested paths and wrote what I would change. What I didn't do: rebuild the live site.
This page is long because the rubric asks for every row. The semester detail is not filled in yet. Empty rows stay marked ... a blank is more honest than a story I don't have yet. Where the public-safe write-up needs a boundary, you will see an honest scope note. I would rather leave a blank than invent a metric or a quote.
01 · 5 pts
Introduction / professional profile
Who you are
Jade Zhao. Informatics student at IU Bloomington Luddy (May 2027). Student Digital Humans project lead. Laurie Burns McRobbie Serve IT Clinic, Jan 2024 to present. Clinic work for partners whose staff keep the page after students leave. On this term I was the tester for the City of Bloomington. I wrote what I would change. I didn't rebuild the live site.
Your area(s) of interest
Digital Humans, human-centred AI, UX (user experience), and business technology. This case study is the spring 2024 City of Bloomington term.
Your technical strengths
Testing paths on a public site and writing the change in plain language, including for keyboard and screen-reader users. The later rungs are on Serve IT.
The kinds of work you want to do
GTM (go-to-market) engineering, AI product, and solutions work. Digital Humans is the project I keep studying. I only write down what has actually shipped.
Links
02 · 5 pts
Project overview
Problem statement
Residents use the city site, including people on a keyboard or a screen reader. If a path is hard to get through, they can't use the page they came for. I tested paths and wrote what I would change. I didn't rebuild the live site. Rows that aren't written yet are marked under Process, Deliverables, and Reflection.
- Dates
- Jan 2024 to May 2024. [still writing: exact kickoff and handoff dates from that semester]
- Team
- [still writing: team names from that semester's roster]
- What the team as a whole was asked to do
- [still writing: the semester brief, once it is safe to publish] True line for now: look at the city site for residents, including keyboard and screen-reader users. The live site was not a student rebuild.
- What my part of the work entailed
- I tested the paths and wrote down what I would change. I didn't rebuild the live site.
03 · 5 pts
Client description
Client: City of Bloomington. Agency website: https://bloomington.in.gov/. Residents need the public site. My part was testing and notes, not a live rebuild.
1. What the client wanted
[still writing: quote or paraphrase from the semester scope once it is safe to publish] True line for now: residents, including keyboard and screen-reader users, need to use the city site.
2. What problem you tried to solve
[still writing: client-stated problem in their words] True line for now: a path that fails on a keyboard or a screen reader shuts people out of city information.
3. The process you went through to reach the final solution
[still writing: short process summary once the testing notes are written up] See also the labelled rows under Process / how you worked.
4. What that final solution is
[still writing: the written changes, if a public-safe copy exists] True line for now: I wrote what I would change. I didn't rebuild the live site.
04 · 5 pts
Process / how you worked
True boundary for every row below: I tested paths and wrote what I would change. I didn't rebuild the live site. The semester detail is not filled in yet.
Research
[still writing: stakeholder research notes / public-safe summary]
Data collection
[still writing: which paths I walked, and what I wrote down]
Accessibility assessment
I tested paths for residents, including keyboard and screen-reader users, and wrote what I would change. [still writing: which pages, and the findings that are safe to publish]
Wireframes
[still writing: wireframes or annotation sketches if you made any]
Agile / sprint workflows
[still writing: how the team organised the weeks]
Testing
[still writing: how you tested, page by page]
Iteration
[still writing: what you revised in the notes before the term ended]
Technical decision-making
[still writing: which checks you trusted, and how you phrased a change for someone else to make] Boundary that stays firm: write the change. Don't rebuild the live city site.
05 · 5 pts
Tools and technologies
Only real lines where confirmed. Unconfirmed tools stay marked.
- Figma
- [still writing: name the tool if you used it]
- Tableau
- [still writing: name the tool if you used it]
- GitHub
- Real for this portfolio: github.com/jadexzhao versions the public case study page.
- Excel
- [still writing: name the tool if you used it]
- Accessibility tools
- I tested paths, including keyboard and screen-reader use, and wrote what I would change. [still writing: name the tool if you used it]
- CMS platforms
- [still writing: name the tool if you used it]
- APIs
- [still writing: name the tool if you used it]
- Microsoft Planner / Teams
- [still writing: name the tool if you used it]
06 · 10 pts
Deliverables / artifacts
Security-team documents must keep client privacy. Block out or remove client names and website mentions on any item shown. On this public page, do not paste private scope text, vulnerabilities, or non-public names. City of Bloomington is the public project name and is fine.
Screenshots
[still writing: public-safe screenshot]
Dashboard images
[still writing: dashboard image if used]
Wireframes
[still writing: wireframe or annotation if used]
Reports
[still writing: the notes on what I would change]
Code snippets
[still writing: code snippet if relevant]
Data visualisations
[still writing: data visualisation if used]
Videos / demo links
[still writing: video or demo link if used]
Presentation slides
[still writing: presentation slides]
Before / after comparisons
[still writing: before / after only if a public fix is shared]
Testimonials or client feedback
[still writing: attributed quote with permission, in quotation marks]
07 · 10 pts
Final reflection
The semester detail is not filled in on this page yet. Empty rows stay marked until the notes are real.
What you learned
[still writing: what I learned]
Challenges encountered
[still writing: challenges encountered]
What you would improve
[still writing: what I would improve]
Team communication lessons
[still writing: team communication lessons]
Ethical considerations
[still writing: ethical considerations]
Technical growth
[still writing: technical growth]