SayProApp Courses Partner Invest Corporate Charity Divisions

SayPro Staff

SayPro Email: info@saypro.online Call/WhatsApp: + 27 84 313 7407

SayPro Information and Targets Needed for the Quarter: WCAG 2.1 Compliance

Written by

Sibusisiwe Jijana

in

SayPro Information and Targets Needed for the Quarter WCAG 2.1 Compliance: Ensure that the SayPro website achieves and maintains full compliance with WCAG 2.1, meeting the AA level of standards from SayPro Monthly February 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: The primary goal for the quarter is to ensure that the SayPro website achieves and maintains full compliance with Web Content Accessibility Guidelines (WCAG) 2.1, specifically targeting the AA level of accessibility. This will help ensure that the website is fully accessible to users with disabilities, supporting a more inclusive user experience.

The WCAG 2.1 guidelines include a set of accessibility criteria across four main principles: Perceivable, Operable, Understandable, and Robust. Achieving compliance will improve website usability for people with disabilities, including those with visual, auditory, cognitive, and motor impairments.

1. WCAG 2.1 AA Compliance Overview

Goal:
To achieve full compliance with WCAG 2.1 at the AA level, ensuring that the SayPro website is usable by individuals with various disabilities, including those who rely on assistive technologies. This involves addressing all the guidelines that fall under the Perceivable, Operable, Understandable, and Robust principles.

2. Key Information Needed to Achieve Compliance

To meet the goal of WCAG 2.1 AA compliance, several key pieces of information and tasks are required:

A. Accessibility Audits and Reports

  • Current Compliance Status: A thorough assessment of the SayPro website to determine where it stands in terms of WCAG 2.1 AA compliance. This includes identifying areas where the site currently does not meet accessibility standards.
    • Required Documents: Previous accessibility audit reports, detailed evaluations from automated tools (like Axe or WAVE), and any manual testing feedback from accessibility experts.

B. Accessibility Issues Identification

  • Compliance Gaps: Document any issues that prevent the site from meeting WCAG 2.1 standards. These can include but are not limited to:
    • Missing or incorrect alternative text for images
    • Insufficient color contrast for text
    • Inaccessible forms and input fields
    • Navigation issues for keyboard-only or screen reader users
    • Lack of captions for multimedia content
  • Key Areas to Review:
    1. Text Accessibility: Ensure that all text content is legible and has sufficient contrast against the background.
    2. Multimedia Accessibility: Check that all videos and audio content have captions, transcripts, or other accessible formats.
    3. Navigation: Verify that users can navigate the site using only a keyboard or assistive technologies (e.g., screen readers).
    4. Form Fields and Error Handling: Ensure that all forms are accessible, with clear labels, error messages, and instructions.

C. Tools and Testing Methods

  • Automated Testing Tools: Use automated tools (like Axe, WAVE, or Lighthouse) to scan the site for common accessibility issues.
  • Manual Testing: Conduct manual testing to assess more complex accessibility challenges that automated tools may not catch, such as usability for screen reader users or keyboard-only navigation.

D. Timeline and Milestones

  • Set Clear Deadlines: Establish a timeline with key milestones for achieving compliance. This includes setting deadlines for:
    • Conducting the initial audit
    • Addressing specific accessibility issues
    • Testing and validating changes
    • Final compliance check

3. Specific WCAG 2.1 AA Criteria to Address

Achieving AA compliance involves addressing a range of criteria within the WCAG 2.1 guidelines. Below are key areas and specific targets for the quarter:

A. Perceivable

  1. Text Alternatives (Guideline 1.1):
    • Target: Ensure that all non-text content (images, videos, icons, etc.) has appropriate text alternatives (alt text).
    • Example: All product images should have descriptive alt text, especially for images with important content like pricing, descriptions, etc.
  2. Color Contrast (Guideline 1.4.3):
    • Target: Improve the color contrast ratio between text and its background to at least 4.5:1 for normal text and 3:1 for large text.
    • Example: Ensure that text on buttons, links, and forms meets the required contrast for readability by visually impaired users.
  3. Resizable Text (Guideline 1.4.4):
    • Target: Ensure text can be resized up to 200% without loss of content or functionality.
    • Example: Verify that resizing text does not cause layout issues or make content inaccessible.
  4. Audio Content (Guideline 1.2):
    • Target: Add captions to all video content and provide transcripts for audio content.
    • Example: Ensure that all promotional videos or tutorials on the website have closed captions and downloadable transcripts.

B. Operable

  1. Keyboard Navigation (Guideline 2.1):
    • Target: Ensure all interactive elements (buttons, links, forms, etc.) are accessible using only a keyboard.
    • Example: Verify that users can navigate through the entire website without needing a mouse.
  2. Accessible Forms (Guideline 2.4.6):
    • Target: Provide clear labels, instructions, and error messages in all forms.
    • Example: Ensure that all form fields have descriptive labels and error messages are clear and easy to understand when an input error occurs.

C. Understandable

  1. Readable Content (Guideline 3.1.1):
    • Target: Ensure that content is written in clear, understandable language.
    • Example: Avoid jargon and provide explanations for any complex terms or concepts.
  2. Error Suggestions and Prevention (Guideline 3.3.3 & 3.3.4):
    • Target: Provide users with suggestions for correcting errors and allow them to review and correct before final submission.
    • Example: After form submission errors, display clear error messages and suggest ways to fix them.

D. Robust

  1. Compatibility with Assistive Technologies (Guideline 4.1.2):
    • Target: Ensure that the website is compatible with assistive technologies like screen readers, voice recognition software, etc.
    • Example: Test the website with screen readers (e.g., JAWS, NVDA) to ensure it reads content in a logical and accessible manner.

4. Targets and Milestones for the Quarter

Goal:
To ensure full WCAG 2.1 AA compliance for SayPro’s website by the end of the quarter.

Milestones:

  1. Week 1-2: Initial Audit and Evaluation
    • Complete an initial audit using automated tools and manual testing.
    • Document current accessibility issues and categorize them according to severity (e.g., High, Medium, Low).
  2. Week 3-4: Implementation of Immediate Fixes
    • Prioritize and address high-severity issues, such as missing alt text, low color contrast, and keyboard navigation problems.
    • Make improvements to text readability, multimedia accessibility, and form error handling.
  3. Week 5-6: Usability Testing with Disabled Users
    • Conduct usability testing with users with disabilities to ensure the site’s improvements are effective and to uncover any remaining barriers.
  4. Week 7-8: Final Adjustments and Testing
    • Implement further changes based on testing feedback, ensuring all interactive elements are fully operable and accessible.
    • Test compatibility with screen readers and other assistive technologies.
  5. Week 9: Final Compliance Check
    • Conduct a final review of the site’s WCAG 2.1 AA compliance status.
    • Create a compliance report documenting all improvements and the status of unresolved issues (if any).
  6. Ongoing Monitoring and Maintenance:
    • Establish a schedule for periodic accessibility reviews and audits to ensure continued compliance, especially when new content or features are added.

5. Success Metrics

The success of the WCAG 2.1 AA compliance efforts will be measured using the following metrics:

  • Percentage of WCAG 2.1 AA Criteria Met: Achieve 100% compliance with WCAG 2.1 AA criteria.
  • User Feedback: Gather feedback from users with disabilities regarding the accessibility of the site after changes are implemented.
  • Audit Results: Monitor the reduction in the number of high-priority accessibility issues over the quarter.
  • Testing Outcomes: Ensure positive results from usability testing with users with disabilities, confirming that they can easily navigate the site and complete tasks.

6. Resources Needed

  • Internal Teams: Accessibility experts, web developers, and UX designers.
  • Tools: Automated accessibility testing tools (e.g., Axe, WAVE), screen readers (e.g., JAWS, NVDA), and usability testing platforms.
  • Training: Regular training for the development and design teams on accessibility standards and best practices.
  • User Feedback: Engaging users with disabilities to test and provide feedback on the website’s accessibility.

Conclusion

By setting clear targets and milestones for WCAG 2.1 AA compliance, the SayPro team can ensure that the website becomes and remains fully accessible to all users, regardless of their abilities. The focus for this quarter is on addressing any gaps in the website’s accessibility, refining its design and functionality, and establishing a strong foundation for ongoing accessibility improvements.

Comments

Leave a Reply

More posts

SayPro Table of Contents

→ Index