Location: Home > Terms of Use > Web Accessibility

Terms of Use

Web Accessibility

Accessibility means that people with disabilities and older people can participate in substantial life activities without any difficulty. In telecommunications technology, accessibility means that anybody can access web-based information and information technology tools easily. Improving the accessibility makes them easily accessible to people with disabilities and older people as well as those with no disabilities.

Improving the company’s website accessibility is also an essential element of business from a Corporate Social Responsibility (CSR) standpoint.

OKI started to include a new item for website accessibilities in “OKI Website Guidelines” enacted in 2002, and in October 2004, it compiled the more rigorous guidelines “The Accessibility Guidelines” which meet JIS standards. Then in March 2008, “The Accessibility Guidelines” were revised on the basis of baseline level of achievement “A“ of "WCAG (Web Content Accessibility Guidelines) 2.0" complied by W3C/WAI. In addition, it was revised in November 2010 on the basis of “Guidelines for older persons and persons with disabilities -- Information and communications equipment, software and services -- Part 3: Web content JIS X 8341-3:2010” which was enacted in August 2008 as the Japanese version of WCAG2.0.

OKI will be working on improving the website usability for all visitor's, including people with disabilities and older people.

OKI Website Guidelines:  <The Accessibility Guidelines>

1. Principles for Perceivable: Information and user interface components must be presentable to users in ways they can perceive.
1.1 Actions for Non-text Content Non-text contents such as images, videos, animations and Flash contents must have alternative text suitable for each content such as alt attribute for img element (images).
1.2 Actions for Prerecorded Sound-only and Video-only Media Provide alternative text content for prerecorded media that contains sound track.
Provide text explanation separately for prerecorded media that contains video content.
1.3 Specify Information and Relationships Information, structure, and relationships conveyed through presentation should not only be visually represented, but also can be programmatically interpreted by using elements such as headings, paragraphs, and lists.
1.4 Describe information with Meaningful Sequence To make consideration of access from programs such as reading environments, describe information with meaningful sequence.
1.5 Sensory Characteristic Information Information required to understand and operate Web contents must not be provided with color, width, visual location, direction, and sound alone.
1.6 Information Representation with Color Information required for understanding and operating Web content must not rely on color alone. For example, use text together with color representation.
1.7 Audio Control For video and/or audio content that play automatically for more than 3 seconds, provide one of the functions below.
  • Function that can stop or pause audio
  • Function that can change volume of video information or audio information but doesn’t change whole system
1.8 Contrast The visual presentation of text and images of text should have sufficient contrast to easily distinguish foreground from background.
1.9 Success Criterion for Resize Text The font size must be able to be changed by users.
1.10 Consideration for Multi-line Text If the text extends over multi-lines, consider color, position, and font size.
1.11 No Use of Frames Frames should not be used.
1.12 Image Map As a general rule, provide client-side image maps instead of server-side image maps.
2. Principles for Operable: User interface components and navigation must be operable.
2.1 Consideration for Keyboard Operation All functionality of the website content should be operable through a keyboard interface without pressing several key strokes in a short time, and pressing it for a long time to access contents.
2.2 Consideration for Focus Move Operation If content is possible to focus by keyboard, removing focus with keyboard is necessary. Also, if it is necessary to operate with other than arrow keys or tab key, operation key must be notified to users.
2.3 Consideration for Adjust Timing of Operation Do not limit the input time except when really necessary. If it is necessary to limit the time for security reason reluctantly, specify clearly the specific time.
2.4 Consideration for Pause, Stop and Hide Displayed elements (images, texts, Flash contents and so on), should avoid the moving, blinking, scrolling, or auto-updating.
2.5 Consideration for Flash or Below Threshold When creating blinking content, ensure that it isn't blinking at a speed of more than three times per second in any one second period.
2.6 Consideration for Bypass Blocks It is necessary that a mechanism is available to bypass blocks of content that are repeated on multiple Web pages.
2.7 Consideration for Page Titles A page should have a title that enables users to identify its content.
2.8 Consideration for Focus Order If a webpage can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components should receive focus in an order that preserves meaning and operability for screen readers.
2.9 Consideration for Link Text and Alternative Text of Image Link For link text and alternative text for image link, link text should be clearly stating the content of the page linked to.
Links to download data file should have file type and file size information.
2.10 Multiple Ways to Locate a Webpage Provide more than one way to locate a Web page within a website.
2.11 Consideration for Heading and Label To help users understand contents easily, provide headings and labels which clearly show their contents and/or purposes.
2.12 Focus Visible It is necessary that the location of focused component is visually recognized.
2.13 Current Location Provide information of the current location within a website structure, so that the user can recognize where he/she is.
2.14 Prohibition of the Forced Opening New Window Links should not open new windows (unless directed by users) but should open items in the same window.
2.15 Consideration for Position of Selection Button When you place buttons for users to be able to select something, always put the buttons that you want users to select on the right.
3. Principle for Understandable: Information and the operation of user interface must be understandable.
3.1 Specifying Language Language code shall be specified.
3.2 Consideration for Unusual Word Foreign terms or technical terms should not be heavily used. When using such words, explanation shall be provided when the word first appears on the page.
3.3 Consideration for Abbreviations Abbreviations should not be heavily used. When using such words, explanation shall be provided when the word first appears on the page.
3.4 Consideration for Pronunciation and Reading of the Words When using proper names or technical terms with difficult pronunciation, or difficult readings, explanation shall be provided when the word first appears on the page.
3.5 Consideration for Focused Component When components such as links and buttons receive focus, an unexpected change of context such as an update of a page, a redirection to another page, or automatically opened new page must not be occurred.
3.6 Consideration for Changes of Context by User Interface Component If a change of setting a certain element, such as checking checkboxes, or input text in text fields makes changes of context, which include automatic reload or a moving to another page, users must be noticed clearly before it happens.
3.7 Consistent Navigation Position of navigations and the way to navigate website should be consistent throughout the website.
3.8 Consistent Notation of Labels and Icons It is necessary that notations such as labels and icons should be consistent throughout the website.
3.9 Error Identification If an input error is automatically detected, the item that is in error should be identified and also the error should be described to the user.
3.10 Consideration for Understandable Input Forms An input example, e.g. contents and conditions should be easy to understand and must be related to an input field.
3.11 Suggestion for Correction of Input error If an input error is automatically detected then provide the suggestions for correction clearly to the user.
3.12 Error Prevention for Legal, Financial, Data Crrection and Submissions A form should have one of the following ways to check and/or correct information before user send it.
  • Considering input errors or other errors, allow users to go back the previous form.
  • Data entered by the user should be checked automatically, and allow users to correct the errors immediately.
  • A form should have a confirmation screen to check and/or correct information before user send it.
3.13 Providing Help Provide Context-sensitive help.
3.14 Symbolic Characters When symbolic characters are used, make their meanings clear.
4. Principle for Robust: Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
4.1 Implementing Web Contents complying with OKI Website Guidelines <The Coding Guidelines> Web content should comply with the OKI Website Guidelines <The Coding Guidelines>. When using brand new technology, comply with concept of the Guidelines, and then comply with specifications of the new technology.
4.2 Name, Role and Values should be Programmatically Interpreted Make sure that all user interface components are to be programmatically interpreted, and their roles are clear, use standard elements such as those in (X)HTML, JavaScript, Flash, PDF.

Top of this page