Custom Generated Accessibility Audit Report
See below on Report Guidelines
Software and Hardware Specifications
Such as Operating Systems, Browsers, Screen Readers, and the URL for testing.
Extensive Experience Using Accessibility Tools:
Color Contrast Analyzer, Axe, Wave, ColorZilla, Siteimprove, Arc Toolkit, and Zoom. Screen Readers: Chrome Vox, Voice Over, and NVDA.
Testing Methodology
I have 10 years of experience in Semi-Automated and Manual Accessibility Testing, plus expertise in Assistive Technology. Checking for good semantics is essential as providing developers with an Accessibility Checklist. I check for implementation of WAI-ARIA Roles and ARIA attributes and ensure developers use Alt tags for images. I create Accessible Design Systems, Accessibility Statements, and Patterns. I also perform training in this area.
Past Experience
Thomas Jefferson University: Contract through Kforce
Texas Commission on Environmental Quality: Contract through Deloitte
Trailhead (Salesforce): Contract through Cyber Innovations
Federal Aviation Administration (FAA): Contract through Yona-Brixtel
U.S. General Services Administration (GSA): Contract through Robbins Gioia
Utilizing Standards, Guidelines, and Principles
WCAG 2.2 Guidelines and Section 508 Standards are implemented. WCAG is organized by four main principles:
Perceivable
Operable
Understandable
Robust
Accessibility Report Format
Page title, WCAG Success Criterion, Assistive Technology, identified errors and made recommendations. Identified areas in which the site was out of accessibility compliance.
Education
University of Maryland, Baltimore County Master’s in Science for Human-Centered Computing
Deque University Online Courses in Accessibility
W3Cx (an online learning initiative of World Wide Web Consortium) WAI0.1x: Introduction to Web Accessibility
Accessible Documents for Microsoft Office and Adobe Acrobat
Two Different Examples of Audit Report Issues
This example is part of an Audit Report using Siteimprove, Accessibility Tools, and Manual Testing. Screenshots of errors and code snippets will be documented.
Another example in the Audit Report using Accessibility Tools and Manual Testing.
The Agile Project Cycle for Accessibility
The Agile Project Cycle for Accessibility begins with gathering comprehensive accessibility requirements from stakeholders. I then create planning documentation that incorporates these accessibility needs. Additionally, I train the team on maintaining the design system with accessible components.
Testing for accessibility compliance follows WCAG 2.2 and 508 standards. I implement accessible prototypes, adhering to accessibility guidelines and using accessible components/patterns.
Throughout the process, I collaborate with developers to ensure functionality with accessibility considerations for the live UI.