SayPro Information and Targets Needed for the Quarter Testing Data: Collect data from user testing to understand which areas of the website require the most attention for accessibility from SayPro Monthly January SCMR-17 SayPro Monthly Inclusive Design: Ensure the site is accessible to users with disabilities by SayPro Online Marketplace Office under SayPro Marketing Royalty SCMR
Objective:
To ensure that the SayPro website is fully accessible, Testing Data must be collected systematically to identify specific areas that require attention. Gathering detailed data from user testing with individuals who have disabilities will enable the team to make targeted improvements, prioritize fixes, and achieve WCAG 2.1 AA compliance by the end of the quarter.
Key Information Needed
- User Demographics for Testing:
- Diverse Participant Pool: Ensure that user testing includes participants with a variety of disabilities, including but not limited to:
- Visual Impairments (e.g., blind users, low-vision users, colorblind users).
- Hearing Impairments (e.g., deaf or hard-of-hearing users).
- Cognitive Disabilities (e.g., dyslexia, attention deficit disorders, learning disabilities).
- Motor Impairments (e.g., limited fine motor control or users who rely on alternative input devices).
- Age and Device Diversity: Include users across various age groups and test on different devices (desktop, mobile, tablets) to capture a broad range of accessibility challenges.
- Diverse Participant Pool: Ensure that user testing includes participants with a variety of disabilities, including but not limited to:
- Testing Scenarios:
- Core Use Case Testing: Test for essential tasks such as browsing the product catalog, searching for items, adding products to the cart, checking out, and completing user account actions (e.g., sign-up, login).
- Form Accessibility Testing: Test all forms (e.g., checkout forms, search filters, contact forms) for ease of use by users with visual or motor impairments. Ensure proper field labeling, error messaging, and overall navigation.
- Navigation and Site Structure Testing: Assess the ease of navigating the site, including the main menu, footer, and internal links. Evaluate keyboard navigation, focus order, and the clarity of heading structures for screen readers.
- Specific Areas of Focus During Testing:
- Screen Reader Compatibility: Test the site’s compatibility with commonly used screen readers like JAWS, NVDA, and VoiceOver. Ensure that all interactive elements are properly labeled and the page structure is logical when read by screen readers.
- Keyboard Navigation: Test the website’s accessibility using only the keyboard to ensure users can navigate all interactive elements (buttons, links, form fields) without requiring a mouse or touch screen.
- Contrast and Color Usage: Test the site for color contrast issues, particularly for text and background combinations. Make sure that users with color blindness can easily differentiate content, and ensure compliance with WCAG 2.1 contrast ratio guidelines.
- Multimedia Accessibility: Evaluate whether all multimedia content (videos, images, audio) is fully accessible, with captions, audio descriptions, and alt text. Check how multimedia is perceived by screen readers and whether audio and video content can be navigated with keyboard-only control.
- Error Handling: Check how errors are communicated to users, especially for those using assistive technologies. Make sure that form validation errors, required fields, and other alerts are clear and actionable.
- Gathering Qualitative Feedback from Users:
- User Interviews and Surveys: After the user testing sessions, conduct interviews or surveys to gather qualitative data about users’ experiences. Focus on understanding any difficulties users faced and asking for suggestions on improving usability.
- Usability Rating: Ask users to rate the website’s accessibility on a scale (e.g., 1-5), allowing testers to indicate their satisfaction with specific features like navigation, form usability, and overall accessibility.
- Open-Ended Feedback: Include open-ended questions in feedback forms, allowing users to express any issues or suggestions that may not have been captured in the structured parts of the testing.
- Key Metrics to Track During Testing:
- Task Completion Rate: Measure how often users with disabilities can successfully complete essential tasks on the site. For example, determine the percentage of users who can add a product to their cart and complete the checkout process without errors or assistance.
- Time to Completion: Track how long it takes for users with disabilities to complete key actions compared to non-disabled users. This can highlight accessibility barriers that slow down the process.
- Error Rate: Document the rate at which users encounter issues during testing, especially those related to accessibility (e.g., unable to complete a task due to poor screen reader support, confusing forms, or keyboard navigation issues).
- Drop-off Rate: Monitor where users with disabilities drop off during tasks (e.g., in the middle of the checkout process or while completing a form). High drop-off rates in specific areas may signal a problem that requires attention.
- Assistive Technology Data:
- Assistive Technology Compatibility Feedback: Ensure that all issues related to assistive technologies (screen readers, voice assistants, alternative input devices) are recorded. Specific issues with assistive technologies should be prioritized for improvement.
- Feedback on Keyboard Shortcuts: For users who rely on keyboard shortcuts, gather data on which shortcuts are useful and which may be missing or nonfunctional.
- Voice Control and Gesture Recognition: If applicable, test voice control and gesture navigation. Collect feedback on how well users with motor impairments can interact with the site using voice commands or gestures.
Targets for the Quarter
- Complete User Testing:
- Test Completion: Complete at least two rounds of user testing with 10-15 users with disabilities by the end of the quarter. The second round should focus on testing improvements made based on feedback from the first round.
- Diverse Testing Groups: Ensure that each round of testing includes users with varying types of disabilities, and ensure that tests are conducted on both desktop and mobile devices.
- Collect Data and Feedback:
- Feedback Forms: Distribute feedback forms after each round of testing. Aim for a 90% response rate from participants, ensuring that the feedback collected is comprehensive and actionable.
- User Interviews: Conduct one-on-one interviews with at least 50% of testers to dive deeper into specific issues they encountered. Focus on pain points and suggestions for improvement.
- Identify and Prioritize Accessibility Issues:
- Document Accessibility Issues: Maintain a centralized tracker to document all accessibility issues raised during user testing. Categorize issues into critical, high, medium, and low priority, and assign them to relevant teams for resolution.
- Address Critical Issues First: Ensure that at least 75% of critical issues (those that significantly impact task completion or accessibility) are resolved within the first half of the quarter.
- Achieve WCAG 2.1 AA Compliance:
- Compliance Audit: Complete a mid-quarter WCAG audit to measure progress toward meeting WCAG 2.1 AA compliance. Use this audit to assess areas that still need attention and to ensure that major issues identified during user testing are being addressed.
- Final Compliance Check: By the end of the quarter, ensure the site meets 90% or higher WCAG 2.1 AA compliance, based on both automated tools and manual testing, and that major accessibility issues identified in user testing have been resolved.
- Enhance Usability Based on Testing Data:
- Reduce Task Completion Time: Improve task completion times for users with disabilities by 10-20% compared to baseline data. This will indicate progress in making the site more efficient for users with disabilities.
- Increase Task Completion Rates: Aim to increase task completion rates for users with disabilities to at least 95%, reducing friction and barriers in essential processes (e.g., making a purchase, completing a form).
- Track Improvements and Adjustments:
- Regular Progress Updates: Provide monthly updates to stakeholders on the progress of addressing accessibility issues based on user testing data. Include specific metrics on task completion rates, time to complete tasks, and feedback on new features or fixes.
- Adjustments Based on Feedback: Make adjustments and improvements throughout the quarter based on ongoing feedback. Ensure that adjustments are tracked and reevaluated through additional rounds of user testing.
Conclusion
By systematically collecting Testing Data from users with disabilities, SayPro will be able to identify areas of the website that need urgent accessibility improvements. This data will guide the development team to make targeted fixes that improve usability and accessibility for all users, especially those with disabilities. Setting clear targets for testing data collection, feedback analysis, and issue resolution will ensure that accessibility issues are prioritized and resolved efficiently, ultimately leading to a more inclusive and user-friendly website.