{'fraction_non_alphanumeric': 0.02456140350877193, 'fraction_numerical': 0.005263157894736842, 'mean_word_length': 5.446327683615819, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Sense and accessibility

of this century, we are all, presumably, familiar with the impact of the Americans with Disabilities Act (ADA), Section 508 of the Rehabilitation Act, and WCAG2 (Web Content Accessibility Guidelines 2) on the design and implementation of computer hardware and software[1]. Testing our products for accessibility is just part of the production cycle, especially for large software suppliers doing business with the U.S. government. Yes, there remains a very real need for the visionimpaired, those with physical limitations, and the cognitively challenged—technological solutions to enhance their lives, to help them achieve and maintain independence. We have plenty of compassionate, capable researchers and practitioners addressing these issues, with the support of government and industry. For instance, IBM has a long history of accommodating and supporting physical disabilities in the workplace, with a sort of affirmative action program that seeks to proactively include everyone in the benefits of technology. But what are we doing for an audience whose handicap is the lack of access to pushing the envelope