{'fraction_non_alphanumeric': 0.02247191011235955, 'fraction_numerical': 0.0016853932584269663, 'mean_word_length': 5.452898550724638, '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}}
Promoting accessibility by using metadata in the framework of a semantic-web driven CMS

Web content accessibility for impaired people has been mainly addressed by the Web Content Accessibility Guidelines (WCAG) developed by the Web Accessibility Initiative (WAI) of the W3C Consortium. Those guidelines have proved to be good diagnostic means for testing accessibility for different types of impairments, as well as for guiding the development of accessible content. A further step would be to promote discovery of material having appropriate accessibility support, as well as the adjustment of control and display of resources to meet user accessibility needs and preferences [5]. The last two challenges have been addressed by the IMS Global Learning Consortium in the IMS-AccessForAll (ACCMD) and the IMS Learner Information Profile (ACCLIP) specifications. Although IMS has approached both goals in a learning framework, both accessibility specifications pay a special attention to impaired users' needs. As a first step, in this paper we survey how far IMS accessibility specifications cover WCAG, and discuss the convenience of extending it to the whole WAI guidelines. Secondly, we argue how accessibility could be considered as a key issue for promoting reusability. We continue explaining why using a semantic framework (such as the MPEG-7 semantic tool, RDF or OWL) for describing textual and contextual information in a standardized manner could promote both, accessibility and reusability. Finally, we explain how some accessibility issues have been already addressed by XimetriX's ximDEX, a semantic-web Content Management System (CMS). We conclude proposing a plan to better integrate the accessibility specifications and contextual description tools into that CMS.