| Oracle® Retail RICS Data Viewer (APEX/DDS) RICS Data Viewer Guide Release 19.3.000 F79086-01 |
|
 Previous |
 Next |
| Oracle® Retail RICS Data Viewer (APEX/DDS) RICS Data Viewer Guide Release 19.3.000 F79086-01 |
|
Previous |
Next |
This chapter gives a brief introduction to Application Express (APEX).
Oracle APEX(Application Express) is a rapid web application development platform for the Oracle Database.
Developers assemble an HTML interface (or application) on top of database objects with wizards or direct input. Each application is a collection of linked pages using tabs, buttons, or hypertext links.
You can manage, manipulate, and display the data in a local Oracle Database or an external data source using REST-based APIs.
Retail Integration Cloud Services (RICS) on APEX is useful for exposing data in a schema with data that is not directly visible to the user. Good examples for this would be a back-end schema of other Oracle applications. Any data that is not exposed by these applications can be viewed using APEX because users cannot connect to database schemas, from a cloud environment, using standard database tools without proper permissions.
APEX offers various functionality regarding databases. It can connect to various RICS database schema connections. The application then discovers the schema inside the databases and allows the user to work and interact with the tables and data within the tables. The following is a high-level list of functionalities offered:
Viewing Table Definition
Querying table data
Creation and modification of records.
Web accessibility means people with disabilities can effectively use and contribute to the web. To ensure people with disabilities can use APEX, you need to design and develop more accessible web applications and software.
What is Web Accessibility?
Web accessibility allows people with disabilities to interact with and contribute to the web.
Why is Accessibility Important?
Accessible products improve experiences for everyone.
About Building for Accessibility
Oracle tracks conformance to Section 508, WCAG, and other standards and guidelines in the Accessibility Conformance Report.
Web accessibility allows people with disabilities to interact with and contribute to the web.
This guide refers to the Web Content Accessibility Guidelines 2.1 (WCAG 2.1) to back up some of the guidelines with the relevant standard and provide further reading.
According to W3C, web accessibility means that people with disabilities can perceive, understand, navigate, and interact with the web, and that they can contribute to the web. The disabilities that affect access to the web can be categorized as: visual, auditory, speech, cognitive, physical, and neurological. The goal of web accessibility is to provide equal access to users with disabilities. That is, developers need to focus on building more accessible web applications and products. Apart from people with disabilities, the elderly with increasing impairments, and people in a limiting situation (for example, slow internet connection, no audio, and so on) can also benefit from accessible applications and products.
WCAG 2.1, which is created by W3C, defines the four principles of accessibility as:
Perceivable: Information and user interface components must be presentable to users in ways that they can perceive. That is, users must be able to perceive the information presented.
Operable: User interface components and navigation must be operable. That is, users must be able to operate the interface.
Understandable: Users must be able to understand the information as well as the operation of the user interface.
Robust: Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
Accessible products improve experiences for everyone.
Up to 16% of the world population is disabled, either through birth, aging, illness, or the result of an accident. Accessible products remove obstacles between a company and its existing or potential customers. Accessibility enables employers to recruit from a broader pool of talent. Overall, accessibility improves products for everyone.
Oracle tracks conformance to Section 508, WCAG, and other standards and guidelines in the Accessibility Conformance Report.
Building for accessibility means coding to standards, and not for a specific technology. Building to standards often leads to better, standardized HTML and cleaner code. The process of building accessible applications at Oracle involves a considerable amount of time and resources at all stages of the development cycle.
The Oracle Accessibility Program Office, reporting to the office of the Chief Corporate Architect, is responsible for defining the corporate standards for accessibility, and developing materials to train all employees so that they can successfully create products that meet those standards. To learn more about Oracle's Accessibility Program, see Oracle Accessibility Information and Resources.
Oracle uses the Accessibility Conformance Report (ACR) to represent the degree of conformance to various accessibility standards and guidelines, including Section 508 and WCAG. Depending on when a product was developed and released, different standards may be listed.
