Jay Rewerts
1
Create a working, one-to-one, prototype of the application in AxureRP
2
Meet with client care and gather feedback on proposed wanted wanted/needed changes
3
Design elements that would provide both the desired outcome while also implementing best user experience practices
4
Develop Vue 3 components while abiding by current Accessibility standards and staying Section 508 compliant
5
Re-develop legacy PHP/Laravel components into Vue 3
6
Keep Figma designs updated with proposed features and design/user interface changes
7
Propose and implement new features to improve the User Experience
1
Watched in-house training videos to get acclimated with how clients are taught to use the app day-to-day
2
Met with client care to discuss pain points and features that both they and their clients have with the current app (Also scheduled several one-on-one meetings to screen share with employees who use the app day-to-day to see the differences from the video tutorial and real-life)
3
Created a 1:1 recreation of the application in AxureRP, and started adding features and updating older components to easily present to and have the business click-through the prototype for approvals and discuss other potential updates
4
Once approved, JIRA tickets would be created with links to the approved Figma designs and the AxureRP prototype, as well as, the development requirements and acceptance criteria
5
Tickets would then move to the backlog and I would work with a project manager to determine the importance of, and the length of time that each ticket should take
6
Some of the new components and features include:
7
During the development process we were able to utilize StorybookJS to build and test new Vue 3 components
8
Briefly used PatternLab to define styles used throughout the app for other developers to reference
9
Reviewed code to ensure best coding practices are followed and is both optimized and is consistent with the other components
10
After the code/branch passed both code review & QA we would run an Automated Test Suite to make certain the new feature doesn't cause the application to crash
11
Once a build passes we would finally merge the branch into the release candidate and close the ticket
1
Reviewed third party accessibility tools & reports that were used to address major concerns and ensure Section 508 compliance
2
After the review, it was concluded that the current vendor was unable to meet our needs or expectations and I was able to provide insight on industry standards and other tools that could be used with better results
3
Trained QA on how to use new accessibility tools and how to correctly identify the errors in the reports that are generated in order to give more context to ticket failures
4
Supported team members during the development and design process by offering training on how to keep accessibility a prime focus
5
Updated and contributed to the creation of a VPAT which was used to showcase how seriously Accessibiliy was being taken to current and potential clients
6
Collaborated with the Sales Team to address questions and concerns