Deque Systems

Similarly, Section 508 of the Rehabilitation Act and its subsequent refreshes serve as major milestones for accessibility by defining the scope of responsibilities for accessibility in the U.S. Federal Government. Section 508 initiated the federal government’s accessibility transformation and established accessibility as a priority. The Section 508 Refresh in 2017 also helped to synchronize the U.S. federal government with worldwide accessibility standards such as the World Wide Web Consortium’s (W3C) The effort involved in creating and refreshing Section 508 over the last 20 years resulted in improved methods for practicing accessibility within the federal government, as well as improved experiences of customers with disabilities interacting with the Federal Government.

– Deque Systems, the trusted leader in digital accessibility, today announced the release of the axe accessibility testing tool for Microsoft’s new Edge web browser. Like its Chrome and Firefox counterparts, axe for Edge is a simple to use, automated testing tool that helps developers identify and resolve common accessibility gaps that prevent or limit people with disabilities from interacting with websites and their content. The axe extension helps developers catch over 50 percent of accessibility problems while coding, dramatically reducing the time and cost of manual accessibility testing,” says Dylan Barrell, Chief Technology Officer at Deque Systems. The free axe browser extension for Edge is available for download at the Microsoft Edge Extensions store.

Misuse or overuse of ARIA on some components (ex: tables, calendars)Some components are somewhat accessible but are missing pieces to make them fully accessible to all (ex: Calendar)Not easily customizable to add accessibility into componentsDirectives or component life cycles must be used to add in accessibility after renderNgx-Bootstrap is a well-documented framework that provides developers with a set of modular components that can be styled, adjusted by scripts, or manipulated with ARIA roles. A number of components are accessible out of the box, such as:Dropdowns (these are more like menus than select dropdowns)Modals – fully documented as far as how to make sure it’s accessible but require some extra attention to ensure full accessibilityCaveat: requires the developer to add the accessibility featuresSome components are not accessible, such as:Datepicker is missing a number of key accessibility features that will prevent a non-sighted user from using the datepicker at all. Some components require more work to be fully accessible, such as:Tabs require the developer to add a unique id to each tab panel so they are associated with their subsequent tabTooltips use dynamic aria-describedby, which can yield inconsistent results for assistive technology usersRadio buttons and checkboxes have a complex integration but lack a group label out-of-boxVarious components have the ability to customize to a point where you can turn off certain features; in general, these should not be used as they will limit the accessibility of your content. The difference between PrimeNG and other component libraries is that it is extremely customizable and allows you as the developer to add in accessibility with ease on components that may not be fully accessible!The use of accessible properties on tags make for easy integration of ARIADoes use semantic HTML for inputsGood amount of components come accessible as isFloat labels done very well with semantic HTMLDevelopers have to take the time to add in accessibility for label association and proper ARIA propertiesMajor components such as Calendar and Modal are still lacking in their accessibility out-of-the-boxSome overuse or misuse of ARIA on a few componentsVarious components have the ability to customize to a point where you can turn off certain features; in general, these should not be used because they will limit the accessibility of your contentAlthough we have spent most of the time talking about UI Component Libraries and

Intelligent Guided Tests have been the bedrock of axe beta, but we knew the experience could be improved… Jumping from the extension to another website to kick off an intelligent guided test, just to jump back to the extension to run the test, and then back to the website to see your results Viewing and exporting test results, initiating Intelligent Guided Tests, browsing existing test records, managing settings; it can now all be done directly in the extension. Screenshot of Intelligent Guided Tests and refreshed UI in axe Chrome extension.