This document discusses a model-driven approach to improving the accessibility and organization of wiki content. The researchers propose using conceptual models and transformations to automatically generate wiki code with structured namespaces, pages, and menus. This aims to help non-technical users more easily plan and create an intuitive information architecture for wikis. The models focus on accessibility elements to reduce barriers for diverse users. While wikis are flexible, their content can be difficult for new or disabled users to understand and navigate. The proposed approach generates wiki code from conceptual models in order to better support users in organizing content.

1. Universidade de São Paulo - USP Instituto de Ciências Matemáticas e de Computação - ICMC Accessible organizational elements in wikis with model-driven development Authors: Thiago Jabur Bittar (UFG – ICMC/USP), Luanna Lopes Lobato (UFG - UFPE), David Fernandes Neto (ICMC/USP) and Renata P. M. Fortes (ICMC/USP) Thiago Jabur Bittar [email_address] Phd Student at USP and Professor at UFG São Carlos-SP – 2010/09/27 ACM SIGDOC 2010

2. Agenda Introduction and Motivation Information architecture Research Goal Model-Driven Development Models Use Web Accessibility Proposal and Case Study Conceptual modeling Possible Advantages Conclusions Future Work

3. Introduction Wiki is a web collaborative tool for promoting rapid publication of information Allowing users to edit, add or revise content

4. Introduction - Motivation Despite various benefits offered There is no guarantee that a good structure of the Wiki content Because Inexperienced users have difficulty to create structured content, even they want Difficult to visualize its information architecture graphically Only code Idea: Learn by Example and use of Graphical Environment

5. Information architecture Information architecture aims to organize the content in an intelligible and organized way Improving the search and understanding of information by users in a given context A poor information architecture results in the majority of the users failures Increasing the rate of usability and accessibility problems

6. Information architecture Graphical viewers are not usually available for better understanding and planning of the wiki structure Wiki A lot of information are often added because its flexibility and easiness - collaboration Great But it is necessary a good information structure and acessible elements

7. Research goal Improve and organize wiki content In a structured and accessibly way, which is important to the user for understanding the information and having a good interaction with it How Studying models and its application on a wiki context Using namespaces Graphically edited and viewed, providing easiness for the user in a better planning on the content that will be inserted

8. Models use To provide a correct use of the models and to support the generation of structured wikis, with good accessibility features We used concepts related to Model-Driven Development (MDD) MDD proposes the use of high-level abstract models And successive transformations to increase the details in each ones

9. Models use Modeling namespaces Implementing accessible organizational interface elements Conceptual Model Coding Level

10. Models use Organizational elements Graphical environment Support for a good Information Architeture planning User Usability Acessibility

11. Web Accessibility In web applications, accessibility questions are important Due to the variety of user types that can work together They often must interact quickly and easily with the interface It is important to reduce the number of accessibility barriers

12. Proposal and Case Study Use Model-Driven Development (MDD) with explicit focus on the improvement of the users’ experiences to support authoring in Wikis This is done through model construction and rules specification for Processing Support tools Automatic code Documentation generation

13. Results - Conceptual modeling Our first meta-model A particular model instance Hierarchical items Properties

14. Conceptual modeling Generated code Interfaces Pages Skeleton Distinct levels Itens and sub-itens Blank pages with titles waiting its filling

15. Possible Advantages Non-specialists can model interfaces Making a conceptual wiki structure More intuitive and less technical user interface design

16. Conclusions The wikis, although widely accepted by users, may require a difficult start planning, especially for individuals with disabilities, which impairs the information design and retrieval

17. Conclusions This work presented the use of meta-models to generate wiki codes But it is not easy to build meta-models that generalize problems. So, we recommend that each organization has its own meta-model and efficient code generation structures.

18. Conclusions And, unlike what occurs in the normal process, using this approach The wiki namespaces are created visually and then pages and menus are generated This approach does not affect the flexibility and freedom of users They can usually create new pages and structure The idea here is to support users in the difficult task of structuring the content and use navigational elements in a consistent and effective way

19. Future Work We intend to model user permissions graphically and integrate the CSS editing with high-level, allowing a non-HTML specialist to choose custom colors and layouts Another idea is to use tools for natural language processing to find unusual expressions and abbreviations Indicating some suggestions to the author

20. Thank you for your attention! Questions? Thanks to University of São Paulo, Federal University of Goiás, CNPq and FAPESP