What Happens When You Configure a Page to Specify Locale

Internationalizing and Localizing Pages 21-19 decimal-separator {view.locale.language==de ? , : .} decimal-separator -- Render the page right-to-left for Arabic -- -- and left-to-right for all other languages -- right-to-left {view.locale.language==ar ? true : false} right-to-left formatting-locale {request.locale} formatting-locale -- Set the time zone to Pacific Daylight Savings Time -- time-zonePDTtime-zone 21-20 Web User Interface Developers Guide for Oracle Application Development Framework 22 Developing Accessible ADF Faces Pages 22-1 22 Developing Accessible ADF Faces Pages This chapter describes how to add accessibility support to ADF Faces components with keyboard shortcuts and text descriptions of the component name and state. Accessibility guidelines for ADF pages that use partial page rendering, scripting, styles, and certain page and navigation structures are also described. This chapter includes the following sections: ■ Section 22.1, Introduction to Accessible ADF Faces Pages ■ Section 22.2, Exposing Accessibility Preferences ■ Section 22.3, Specifying Component-Level Accessibility Properties ■ Section 22.4, Creating Accessible Pages ■ Section 22.5, Running Accessibility Audit Rules

22.1 Introduction to Accessible ADF Faces Pages

Accessibility involves making your application usable for persons with disabilities such as low vision or blindness, deafness, or other physical limitations. This means creating applications that can be used without a mouse keyboard only, used with a screen reader for blind or low-vision users, and used without reliance on sound, color, or animation and timing. Oracle software implements the standards of the Web Content Accessibility Guidelines WCAG 1.0 Level AA using an interpretation of the standards at http:www.oracle.comaccessibilitystandards.html Additional framework and platform issues presented by client-side scripting, in particular using asynchronous JavaScript and XML AJAX have been addressed in Oracle’s accessibility strategy. ADF Faces user interface components have built-in accessibility support for visually and physically impaired users. User agents such as a web browser rendering to nonvisual media such as a screen reader can read component text descriptions to provide useful information to impaired users. Access key support provides an alternative method to access components and links using only the keyboard. ADF Faces accessibility audit rules provide direction to create accessible images, tables, frames, forms, error messages and popup windows using accessible HTML markup. While following provided ADF Faces accessibility guidelines for components, page, and navigation structures is useful, it is not a substitute for familiarity with accessibility standards and performing accessibility testing with assistive technology.