-
Notifications
You must be signed in to change notification settings - Fork 0
Home
a11ytagger is a tool for adding accessibility tags to PDFs, with the ultimate goal of providing full PDF/UA support.
- Colin Jamison - Wireframe, Generation of Personas
- Lars Bartels - Generation of Personas, Wireframe, Phase 1 draft
- Ian Stewart - Added personas, scenarios, wireframes, & executive summaries to wiki.
- Personas and Scenarios
- Sketches and Diagrams
- Wireframes
- Prototype - Coming Soon
Executive Summary
-
Competitive Analysis revealed key weakness of other accessibility tagging options:
- Too expensive: many existing options are prohibitively expensive for the average user.
- Vendor lock-in: some options are too tightly coupled with preexisting software that the user might not want.
- Bad auto-tagging: many existing options use error-prone auto-taggers that require time-consuming manual fixes.
-
Heuristic Evaluation showed us how to improve upon PAVE:
- Inconsistent user interaction: PAVE suffers from inconsistent interaction design, confusing users.
- PAVE's issue detection quickly shows the user exactly what they need to start with when remediating.
-
Personas and Scenarios expand our insight into user needs:
- Fast and easy tagging is a must!
- Users must have a consistent and easily learnable workflow to follow when tagging documents.
-
Sketches consolidated ideas for initial concepts:
- Multiple divergent sketches allowed us to narrow down our best ideas for design and workflows.
- Better error reporting will prevent user frustration and allow them to recover easily.
- A well-defined workflow will enable users to easily learn a system for quickly remediating documents.
Executive Summary
Improving user workflows became a primary goal after conducting cognitive walkthroughs. More specifically, it became clear that the application would benefit from better feedback on loading or error states. Reviewers also noted that the wireframes have minor inconsistencies in navigation. Feedback from a product demonstration revealed a need for OCR support in addition to a dedicated mode for image tagging. This image tagging mode will enable a list view for users to quickly browse images and add alt-text, with some display of progress remaining. Feedback also highlighted a need for improved tool layouts. Findings pointed out a general need for a more streamlined path for user editing. Wireframes were updated accordingly, adding both detail to tool designs and additional information pages. Research methods were limited due to a small number of evaluators, a lack of hands-on product testing, and inexperienced UX evaluators. Future testing will include a hands-on usability test of a working prototype.
Executive Summary
!!!Put phase II Executive Summary here!!!