KAMİS
Determination of Content Policy
Alternative File Formats
Principle
Websites should support commonly used file formats, allowing users to access files without the need for additional software installation.
Description
Websites often provide electronic files in various formats for users. To reach a broader audience, it can be beneficial to present files in different formats. For example, when only a text-based file is necessary, the relevant file can be presented in formats like ".pdf," ".rtf," ".docx," or ".odt." This way, users can open the file using various programs without the need for a single specific application.
Guidelines
- On websites hosting files, files should be presented to users in various formats.
- When determining different formats, consider the most common and preferably freely available applications (e.g., LibreOffice, Adobe Reader, Microsoft Office, etc.).
References
- –
Useful Resources
Visual and Functional Consistency
Principle
Similar concepts on the website should be designed with consistent visuals and functionalities.
Description
To maintain the consistency of a website, visuals and operations of the same type should be carried out in a consistent manner. Inconsistent components can lead to user errors. Achieving consistency on a website results in fewer user errors, quicker task completion, and increased user satisfaction. Consistency is a significant factor in determining the perception of an organization's quality.
Guidelines
- Similar types of data in data entry fields should be entered in the same format.
- The positioning of data entry fields should be uniform for similar functions.
- Menus within the site should be similar in both functionality and visuals.
- For processes consisting of multiple similar steps, these steps should be designed consistently.
- In addition to consistency within the site, user habits and commonly accepted operations and formats should be followed.
- Icons, fonts, lines, separators, arrows, and other components used in the design should be consistent in the same abstraction level and should belong to the same family.
References
- –
Useful Resources
Consistency of Contact Information
Principle
Contact information placed on different sections and pages of the website should be consistent.
Description
Public institutions can undergo changes over time, with units relocating to different areas or modifications happening in contact information. Such changes can not only mislead users but also undermine trust in the website and reduce the perceived quality of other services on the site.
Guidelines
- Contact information should be visually and contextually consistent across the sections and locations where it is displayed.
- Details such as the address, phone numbers, postal codes, etc., should be consistent on both the homepage and subunit pages.
- Contact information should adhere to commonly used formats.
- Efforts should be made to ensure that services that index contact information of organizations update their data when contact details change.
- Providing a contact form is preferable.
- Contact information must always be kept up to date.
References
- –
Useful Resources
Downloadable File Names
Principle
Downloadable files on websites should have meaningful names.
Description
Websites may provide downloadable files tailored to specific needs. Paying attention to the naming of these files helps prevent situations that could negatively impact the user experience.
Guidelines
- File names should be short and clear to allow users to understand the purpose of the files.
- Users should be provided with information about the file type and size along with the file name.
- Unless required otherwise, date and version information should be added to the end of the file name.
- File names should avoid using spaces or special characters.
References
- –
Useful Resources
Personalization of the Website
Principle
If internet sites provide services tailored to individuals or organizations, they should be adaptable according to user needs.
Description
In particular, adapting the content and navigation structure on internet sites when accessing regularly used services to specific users or user groups can be highly beneficial. It serves from various aspects such as presenting content based on users' interests and easily directing them to relevant content. It is well known that personalization in systems that are frequently used enhances user performance and satisfaction.
Guidelines
- In internet sites where users perform actions by logging in, if possible, personalization should be enabled based on user needs and preferences.
- If user logins are performed with different roles, the roles and the associated permissions should be clearly defined.
- Users should be granted the authority to view, edit, and delete their profile information and settings.
- If the site automatically adapts based on user navigation habits or visited pages (e.g., suggesting new pages of potential interest based on visited pages), the purpose of this application and the information used should be communicated to users.
- Users should have the option to disable the site's automatic adaptation feature at any time.
- When making adjustments according to user expertise levels, this information should be provided to users in advance, and hints for transitioning between levels should be given at each interface.
References
- ISO 9241-151 / 7.2.9 – Individualization and user adaptation
Useful Resources
Backup of the Website
Principle
Internet sites should be regularly archived and backed up.
Description
Just as organizations archive their paper-based correspondence, it is essential to archive the contents of institutional websites. Archiving website content contributes to the development of institutional memory and serves as a backup in the event of system crashes or cyberattacks.
Guidelines
- A backup procedure should be defined and implemented.
- If archiving all website content is not possible, contents should be identified according to their importance, and archiving should be carried out accordingly.
- Archiving should be performed at regular intervals.
- Authorized personnel should be defined, and relevant individuals should be able to access the archives easily.
- Access logs, database, and system files should be regularly backed up to prepare for possibilities like system crashes or cyberattacks.
- A system restoration infrastructure should be established from the backed-up files.
- When the site design is modified or the structure is changed, archives of the old structure should be preserved for the access of authorized individuals.
References
- –
Useful Resources
User Errors
Principle
Internet sites should be designed to prevent users from making errors.
Description
It is natural and expected for users to make errors. The purpose of all technological systems is to take measures to prevent users from making errors through design techniques and technological support. Errors often occur when there is a mismatch between the mental model in the user's mind and the mental model in the developer's mind. Users who make mistakes usually feel unhappy and incompetent. In some cases, users may try to explain the cause of the error by attributing it to reasons like the system not working correctly.
Internet sites should be designed with the goal of minimizing errors, considering the target audience. It is crucial to eliminate components and structures that can cause errors before errors occur. When an error does occur, users should be guided constructively in a way that does not make them feel bad and should be redirected from the error to continue the process.
Guidelines
- Pages must include "orientation information" and "titles." These elements constantly remind users of their context and prevent them from giving incorrect commands or inputs.
- Form-based data collection processes should include short and clear instructions.
- Input controls must be validated, and potential errors should be detected before the user clicks the submit button.
- Assistance should be provided in places where users may have difficulty, using examples.
- For fields such as phone numbers or citizenship numbers, to prevent incorrect entry and to increase input speed, segmentation fields like 3-3-4 or 3-3-3-2 should be used consistently.
- Access to inactive links and functions should be removed or rendered unclickable.
- Designs and contents that users might misunderstand should be avoided.
- User-entered data should not be reset after an error message.
- Incorrect data should be marked separately in a different color or font in the error message.
- If an important piece of information is provided in the error message and should be used after the user clicks "OK" or "Accept," it should be kept on the screen; users should not be forced to remember it or take notes.
- Error, warning, and informational messages should inform users clearly and understandably. Error messages should define the task the user was trying to accomplish and contain sufficient information (e.g., "Failed to delete mydocument.odt: The file is being used by another program," etc.).
- User-unfriendly structures and message tones that users might culturally disapprove of should not be used in error message language (e.g., "Illegal operation detected," "Access permission revoked!", "You do not have permission!!!," etc.).
- Error messages and warning messages should not be confused with each other and separate visual and textual components should be used.
- Error message language should not include judgemental, questioning and derogatory expressions.
- The error message content must contain information to guide the correct operation.
- Error messages should be presented in such a way that the user cannot miss them and should be supported by audible warnings when necessary, depending on the user context. However, it should be preferred not to use audible warnings as much as possible.
References
- ISO 9241-151 / 10.3.1 – Minimizing user errors
- ISO 9241-151 / 10.3.2 – Providing clear error messages
Useful Resources
Measurement Unit Formats
Principle
The units of measurement used on a website should be consistent and compatible with the language in which the site is displayed.
Description
For websites that offer different language options, the elements (e.g., currency, units of measurement, temperature, date, phone number, address, postal code, etc.) in the content and data entry screens of the website should be created in a manner that is appropriate and consistent with the language in which they are displayed.
Guidelines
- If different language options are provided on the website, the units of measurement used on the pages should be consistent with the language in which they are displayed.
- Data entry fields on the website should be compatible with units of measurement formats in all supported languages.
- Pay attention to the punctuation marks in certain units of measurement, both from a database and user perception perspective.
References
- ISO 9241-151 / 10.1.4 – Using appropriate formats, units of measurement or currency
Useful Resources
Commercial Advertisements
Principle
Public websites should not use content that promotes any commercial organization, product, or service for advertising purposes, whether explicitly or implicitly.
Description
The purpose of public websites is to provide information and services to the public in the digital environment. Public institutions should treat every citizen equally, regardless of discrimination. In this regard, websites should provide an equal experience to all users and should not focus on profit-generating advertising.
Guidelines
- Public institutions should avoid using content that highlights any commercial organization, product, or service for advertising purposes on their websites (with the exception of companies in the commercial sector that generate revenue from commercial ads and sponsored event announcements).
- It should be avoided to emphasise or exemplify certain brands.
- Unless it is mandatory, service types that only certain commercial software packages, certain brand devices, file formats can open and process should be avoided.
References
- –
Useful Resources
- –
Website in a Foreign Language
Principle
Websites targeting users who speak foreign languages should also provide services in the relevant languages.
Description
Some public institutions serve users who speak different languages. Analyzing the user base and providing accurate and high-quality translations on websites where foreign languages are needed is important.
Guidelines
- Websites catering to users who speak different languages should offer language options.
- Language options should use letter codes determined by the ISO 639 standard (e.g., Turkish: "tr," English: "en").
- Since country flags represent a country, not a language, the use of flag images should be avoided.
- Foreign language options should be available on the main page and all sub-pages.
- Translations should be checked for accuracy.
- The main page and sub-pages should be translated into other languages.
- If there is a page that has not been translated, this should be clearly indicated to the user.
- Updates and announcements should be translated in a timely manner, or the untranslated text for these sections should be linked with an explanatory note.
References
- ISO 9241-151 / 9.6.5 – Identifying the language used
- ISO 9241-151 / 10.1.1 – General
- ISO 9241-151 / 10.1.3 – Identifying supported languages