| A | B | C | D | E | |
|---|---|---|---|---|---|
1 | Grid Analysis of the three components of transparency on the wikipedia 4chan’s page (governance rules, interface issues, software issues). | ||||
2 | |||||
3 | Legend of the grade column : | ||||
4 | Grade Legend : 0 -> element inexistant, strong lack of transparency. 2,5 : some efforts, the element is present but not clear, not well situated in the interface. | ||||
5 | 5 -> It's ok the elemnts are clear but it can be better designed. 7,5 -> it's ok the things are here and well designed. 10 -> It's perfect. | ||||
6 | |||||
7 | Ergonomic Criteria | Sub-Criteria | Definition | Analysis | Grade |
8 | Depth of transparency information on Content / Governance Edition | General Information | Refers to general information of the page | See Page information on the left menu, plus all the page on the last line of links of the footer : “Privacy policies” ... | 10 |
9 | Depth of transparency information on Content / Governance Edition | Consensus work | Refers to the fact that the content of the website is a result of a consensus involving users participation and diplomacy | See Talk Page | 7,5 |
10 | Depth of transparency information on Content / Governance Edition | History of the page | Is it possible to know the date of creation of the content and the history of the edition and to compare differents version of the page ? | Yes, see history and contributions pages, and the comparison button on the history page | 7,5 |
11 | Depth of transparency information on Content / Governance Edition | Basis of arguments | Can we know what are the first source of the argumentation or from which ideas/references the contents come from ? | See all of the external at the end of the article. | 5 |
12 | Depth of transparency information on Content / Governance Edition | Quality of the content | What is the accuracy and the degree of validity of the content ? | Mention regarding arguments such as WP:DUE, WP:NPOV, MOS:ELLIPSIS in the talk page. Plus “Disclaimers” page in the footer. | 5 |
13 | Depth of transparency information on Content / Governance Edition | Condition of reuse of the content | Does the content is published with a copyright or a CC licence or another licence ? | Yes, see CCL at the end of the page. | 10 |
14 | Depth of transparency information on Content / Governance Edition | Privacy Policy / Cookie Statement | Does the privacy policies are clear and present on the page ? | Yes, see the link of the privacy policies at the bottom left of the page. Cookie Statement | 10 |
15 | Depth of transparency information on Content / Governance Edition | Disclaimers | Does disclaimers issues are assumed and visible ? | See Disclaimers page in the footer | 10 |
16 | Depth of transparency information on Content / Governance Edition | Authors | Can we precisely know who create the content ? | YEs, see sytem of account and login, plus tracking on the talk page, plus ip address tracking | 7,5 |
17 | Depth of transparency information on Content / Governance Edition | Authors Contact and/or Technology providers contact | Can we contact the authors of the content and the technology providers ? | See “Contact Wikipedia” page in the footer, and the contact info on each editors profile if they are available. | 5 |
18 | Interface Issues | Guidance / Immediat Feedback (Bastien & Scapin) / Visibility of System Status (Nielsen) | “concerns system responses to users’ actions. These actions may be simple keyed entries or more complex transactions such as stacked commands. ” (Bastien & Scapin) | Not really relevant for the moment, need to be test in an “editor” mode | 2,5 |
19 | Interface Issues | Guidance / Significance of signs (Bastien & Scapin) / Match between system and the real world (Nielsen) | “qualifies the relationship between a term and/or a sign and its reference. Codes and names are significant to the users when there is a strong semantic relationship between such codes and the items or actions they refer to.” (Bastien & Scapin) + “The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.” (Nielsen) + “” | On 4chan’s page, problem of labelling for the “Interaction” menu : not all of the submenu are related to interactions, plus confusion : Interaction with whom ? Between users ? Between a user and the system ? | 7,5 |
20 | Interface Issues | Workload / Brevity / Concision / Aesthetic and minimalist design (Nielsen) | “corresponds to the goal of limiting the reading and input workload and the number of action steps.” (Bastien & Scapin) + “Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.” (Nielsen) | OK but Maybe to much links on the left section related to core wikipedia pages | 7,5 |
21 | Interface Issues | Workload / Information Density (Bastien & Scapin) | “concerns the users’ workload from a perceptual and cognitive point of view with regard to the whole set of information presented to the users rather than each individual element or item.” (Bastien & Scapin) | OK but maybe to much links on the left section related to core wikipedia pages | 7,5 |
22 | Interface Issues | Explicit Control / Explicit User Action (Bastien & Scapin) | “ the computer must process only those actions requested by the users and only when requested to do so.” (Bastien & Scapin) | Tracking of the user with an ip address by default. When we edit everything is track on our profile, is it what we want ? | 5 |
23 | Interface Issues | Explicit Control / Consistency and standards (Bastien & Scapin) | “Users should not have to wonder whether different words, situations, or actions mean the same thing.” (Nielsen) | Problem with the two “Talk” button, confusion whether what does each button + confusion between the page history, the recent pages and the user contributions page | 5 |
24 | Interface Issues | Explicit Control / User Control/Freedom (Nielsen) | “refers to the fact that the users should always be in control of the system processing (e.g., interrupt, cancel, pause and continue). Every possible action by a user should be anticipated and appropriate options should be provided. (Bastien & Scapin)” / “Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.” (Nielsen) | Not relevant for the moment, need to be test in an “editor” mode | 10 |
25 | Interface Issues | Adaptability / User Experience / Flexibility and efficiency of use (Nielsen) | “ Different levels of interaction should take users’ experience into account.” (Bastien & Scapin) / “Accelerators -- unseen by the novice user -- may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.” | All the WP:NPOV or wp:DUE elements in the talk page that links each comments with a reference to wikipedia guidelines : ensure that all types of users are inform of the rules. | 10 |
26 | Interface Issues | Error Management / Error protection + Quality of error messages+Error corrections (Bastien & Scapin) | “refers to the means available to detect and prevent data entry errors, command errors, or actions with destructive consequences.” (Bastien & Scapin) + “ refers to the phrasing and the content of error messages, that is: their relevance, readability, and specificity about the nature of the errors (syntax, format, etc.) and the actions needed to correct them.” (Bastien & Scapin) + “ refers to the means available to the users to correct their errors”. (Bastien & Scapin) | Not relevant for the moment, need to be test in an “editor” mode | 2,5 |
27 | Interface Issues | Error Management / Help and documentation (Nielsen) | “Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large.”(Nielsen) | OK, a lots of links to wikipedia rules and guidelines in the left menu, the header, the footer. On the talk page, same things for the blocs on top. On the history page, see the question mark button on the top right | 10 |
28 | Software Issues | Source Code availability | Is the source code is easily available ? | Yes, see “View Source” menu, on the top right menu | 10 |
29 | Software Issues | Technology used | Does the interface announce the technology he used to create the interface ? | Yes, see the “Powered by Mediawiki” at the bottom right of the page | 10 |
30 | Software Issues | Hypertextual situation of the content on the web | Do we know where the page is on the website (menu, breadcrumb) and on the web (internal and external links) | See all of the wikipedia categories to which the pages belong at the end of the article, plus the “What links here ? ” page on the left menu | 7,5 |
31 | Software Issues | Semantic Web / Interoperability / Forking | Does the page and its content is described as a semantic web item? | Yes, see the “Wikidata item” on the left menu | 10 |
32 | Software Issues | Technical contribution guide | Is it possible to contribute to the code and how ? | See the Developers page in the footer | 7,5 |
33 | Software Issues | Archiving System | Does the system has an archiving plan? Does this one is available and clear ? | See archiving bloc on the talk page, at the bottom right after the yellow blocks | 7,5 |
34 | Software Issues | Data feed | Does the website generate a data feed ? Is it available ? | See Atom Rss feed on the history page, plus the wikipedia API for data in other formats | 10 |