Phase2 Technology is committed to delivering digital experiences that is accessible to people with disabilities. Websites and mobile applications comply to Section 508 and WCAG 2.1, Level AA conformance. Direct any questions or issues to email@example.com
Phase2 Technology builds its products with accessibility in mind. Utilizing an in-house Accessibility Expert, all development, design, and product management teams are trained on Section 508 accessibility requirements. At the core of Phase2’s mission statement is to:
unlock the potential for anyone, anywhere to engage with the world’s most impactful organizations at any time.
This reflects a fundamental commitment to helping our clients serve their audiences regardless of ability.
Section 508 is a legal requirement for Federal agencies to make their electronic and information technology (EIT) accessible to people with disabilities. Additionally, any agency that receives federal funding must comply to Section 508 on their web properties.
The Web Content Accessibility Guidelines (WCAG) contain 12-13 guidelines that are categorized within 4 principles (perceivable, operable, understandable, and robust). The International standard is set at WCAG Level A and Level AA. Phase2’s baseline is conforming to WCAG 2.1, AA conformance, of which also complies with Section 508.
During active development and launch of a digital experience, Phase2 will monitor and review accessibility conformance specific to the client. Accessibility is an ongoing process, in that, due to the ongoing nature of development and content, it is never a ‘one and done’ process. In response, Phase2 works with the client on a training, remediation and monitoring plan informed by priorities.
Accessibility that is considered at the beginning of a digital experience process saves on time, budget, and resources. By catching potential issues early, designers and developers are working from an accessible foundation. In this evaluation, the Accessibility team consults designs to evaluate all touchpoints that may have an impact on website accessibility. In response, accessibility considerations are documented for the developers to follow during development. All touchpoints are documented with an expected outcome for product managers to validate through manual testing with assistive technology and/or keyboard controls.
Phase2 Technology developers are not only trained in accessibility best practices, but are also having their code monitored for any accessibility regressions through a continuous integration process. This safeguards against undetected issues resulting in costly and time-consuming remediation later in the development cycle.
Additionally, Phase2 Technology’s pattern lab, “Particle” has accessibility built in, providing the optimal foundation from which front end developers can begin from. Particle also has the automated testing tool integrated for any new code updates to Particle, to continue safeguarding against accessibility issues.
Phase2’s in-house Accessibility Team oversees all monitoring and accessibility testing conducted on projects. Utilizing a combination of testing approaches from automated to manual in all stages of development, Phase2 is able to catch issues early, prioritize, and develop a remediation plan. Our automated tools include SiteImprove Platform, pa11y for the development process, of both which automatically generate accessibility reports for evaluation.
In the manual testing process, the Accessibility team supports product managers in manually testing features for accessibility, using a screen-reader and keyboard navigation to fully test the experience. Results go into a detailed reporting tool and are tracked, prioritized, and remediated throughout the development cycle. Phase2 provides a final “audit” to the client on the accessibility efforts and remaining steps or issues regarding conformance.
Phase2’s Accessibility Team provides an extensive audit on applicable projects for accessibility. This includes, but is not limited to the following:
Inventory of Features and associated Accessibility Requirements
Test Results and High-Level explanation of Issue failures
Test Steps with explicit instructions for screen-reader and keyboard navigation
Impact Score and Prioritization Recommendation