Closed bbertucc closed 3 hours ago
Launched our User Study here:
Interviewed 5 participants.
Recordings logged in the Leads DB. (Private to protect confidential info from users.)
Here's an overview of the key user studies we're focusing on:
Equalify is built to fix web accessibility issues, so every user story is focused on that goal. These are the core users that Equalify is hoping to reach:
Developers, experienced and new to accessibility, will use Equalify to fix issues. After adding pages, Developers would be notified of any new issues related to reports. They don't want to be bugged a lot, so they would need to change the frequency of issues they are notified about. Some developers need hours approved to work, so they should be able to share reports. Developers also hate any UX that they didn't create, so API access is vital to generate raw data that Equalify uses. Developers who are experienced with web accessiblity also use tools, like https://wave.webaim.org/report to visualize issues that they need to fix, so a way to visualize would be key to fixing issues.
Accessibility managers make sure thousands of pages remain accessible to people with disabilities. They like to have a general view of issues. From those general views they create specific tickets that developers execute on. Some tickets include a lot of nodes related to a message. Others are specific about an individual node or page. Accessibility managers also want to ignore nodes that they don't think are useful or create custom scans for information that governance policies require. A job well done is reducing the number of issues per page over time. Accessibility Managers will share these reports of successes with their bosses, or add peers to the account to view or create their own reports. Finally, Accessibility Managers really love emails. They follow updates and continue to use Equalify with regular emails sent.
Agency Owners love reports that get their clients to pay them for additional work. An agency owner may add their existing clients into Equalify and forward emails or share reports when an issue occurs. Once a client pays for a fix, the agency owner will create a ticket for his developer or share a link to the report. Agency Owners can make clients happy by showing them a report that proves they decreased the density of issues per page.
Professionals who rely on screen readers are important users of Equalify. Oftentimes, these testers lead accessibility decisions at their organizations. Blind accessibility pros should be able to analyze Equalify reports, just like other accessibility managers. Additionally, Blind pros can validate issues that are reported in Equalify - marking them as ignored if they are false positives. Equalify can also act as the eyes for a blind user, testing for issues that they might miss because they rely on screen readers.
Problem
We need user stories to understand who we're building for.
Steps to Close this Issue