340 likes | 511 Views
Using Oracle Application Express to Build Highly Accessible Web Applications. Marc Sewtz Senior Software Development Manager, Oracle USA Inc.
E N D
Using Oracle Application Express to Build Highly Accessible Web Applications Marc Sewtz Senior Software Development Manager, Oracle USA Inc.
The following is intended to outline Oracle’s general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions.The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.
Agenda • Oracle’s Accessibility Commitment • Application Express Overview • Accessibility Overview • Building for Accessibility • Accessibility and Application Express • Demonstration • Testing • Into the Future • Questions
Oracle Corporation • The world’s most complete, open, and integrated business software and hardware company • Scale • 370,000 customers in 145 countries • 20,000 partners • 104,500 employees • 10 million developers in Oracle online communities • Over 100 U.S. Federal government organizations • 38 U.S. States run Oracle Applications • 24 of the 100 largest U.S. School Districts run Oracle Applications • 11 of the 15 largest U.S. Counties run Oracle Applications • 35 of the 50 largest U.S. Cities run Oracle Applications • Innovation and Investment • 29,000 developers and engineers • 15,500 customer support specialists, speaking 27 languages • 20,000 implementation consultants • 1.5 million students supported annually • 870 independent Oracle user groups with 355,000 members
Oracle Corporation#1 in 50 product or industry categories • Applications • CRM • Enterprise Performance Management • Project Portfolio Management • Transportation Management • Industries: • Communications • Construction • Discrete Manufacturing • Life Sciences and Healthcare • Public Sector • Professional Services • Retail • Transportation • Technology • Database • Database on Linux • Database on SAP • Database on Solaris • Data Warehousing • Embedded Database • Development Language – Java • Middleware • Application Servers • Identity and Access Management • Hardware • Tape Storage • Unix Server
Oracle’s Commitment to Accessibility "Oracle is committed to creating accessible technologies and products that enhance the overall workplace environment and contribute to the productivity of our employees, our customers, and our customers’ customers.” - Safra Catz, President and CFO
Overview APPLICATION EXPRESS
Oracle Application Express (Oracle APEX)Browser Based Application Development
Oracle Application Express (Oracle APEX)Benefits Leverage SQL Skills Rapid Browser Based Development Point your browser and start developing Build reports and charts using SQL Self Service Provisioning Runs within Database Out-of-the-box elastic private cloud service Simple to manage, highly scalable
Oracle Application Express (Oracle APEX)Architectural Overview • Simple 2-Tier Architecture • Pages dynamically rendered using database Metadata • No code generation or file based compilation • Runs Everywhere Oracle Database Runs
What is it, and why is it important? Accessibility Overview
What is Web Accessibility?#1 The goal Equal access
What is Web Accessibility?#2 “The Four Principles of Accessibility” • Perceivable • Operable • Understandable • Robust Reference: Introduction to Understanding WCAG 2.0
Why Accessibility is ImportantProcurement and Discrimination Laws Examples: • Section 508 of the Rehabilitation Act of 1973, amended 1998 (U.S.) • In effect as of 2001 • New revision expected sometime in 2013 or 2014 • Mandate 376 (E.U.) • Largely aligned with revised Section 508 for content and timing • Accessibility for Ontarians with Disabilities Act (Canada) • Americans with Disabilities Act (U.S.) • Disability Discrimination Act, and Equality Act (U.K.) • Twenty-First Century Communications and Video Accessibility Act (U.S.) The list goes on and on, worldwide…
Why Accessibility is ImportantProcurement and Discrimination Laws, continued Basic premises of these regulations: • Organizations must develop, procure, maintain or use E&IT accessible to employees and members of public with disabilities • Employers must make “reasonable accommodations” unless it poses an “undue hardship” • Employers must not place an employee at a “substantial disadvantage” in comparison with persons who are not disabled. • Narrow exceptions for national security, non-availability, undue burden, etc.
Why Accessibility is ImportantIt makes good business sense • Up to 16% of the population is disabled, either through birth, ageing, illness, or the result of an accident • Accessible products remove obstacles between a company and its existing or potential customers • It allows employers to recruit from a broader pool of talent • Generally improves product for everyone (Universal Design) And…it’s the Right Thing To Do
It’s not just a checklist! Building for accessibility
How Application Express helps you to address accessibility Accessibility and apex
Accessibility and Application ExpressHow APEX helps you address accessibility • The power of themes and templates • Solid templates provide a solid base • Theme 21 underwent accessibility testing for 4.1.1 • Declarative • Exposes declarative attributes that help you define important properties, eg page titles, form field labels, button labels, table column headers, etc. • Metadata based • Easier to identify possible violations
Accessibility and Application ExpressHow APEX helps you address accessibility • Accessibility Modes • Screen Reader • High Contrast • Adopting modern standards • HTML 5 / WAI-ARIA to help write more semantic code & make richer content accessible • Further information • APEX 4.1.1 VPAT (Accessibility conformance statement for APEX) • User Guide > Accessibility in Application Express
Building the application DEMONSTRATION
TestingDeveloping a robust testing strategy • What do you test? • Theme testing first (we tested theme 21 in APEX 4.1.1) • Cover primary application flows, and pages representative of common functionality • Include custom code, e.g. PL/SQL based regions, custom HTML, etc. • APEX Metadata audits
TestingDeveloping a robust testing strategy • What types of testing will you do? • Keyboard-only (for users unable to use a mouse, including screen reader users). (First) • Using automated tools / toolbars (to identify definite failures and present other mark-up to you in a way that helps you determine compliance). (Second) • Assistive Technology (AT) testing (such as screen reader testing for users with low vision or who are totally blind). Do this after keyboard-only and using automated tools. • Colour contrast (for users with low vision, or colour vision deficiency) • Windows High Contrast mode (for users with low vision, or colour vision deficiency) • User (very important)
TestingDeveloping a robust testing strategy • Ensure testing is valid • Unplug your mouse for keyboard-only testing. • Turn off your monitor and unplug your mouse for screen reader testing. You just need a keyboard and speakers! • Engage with users with disabilities • Raise awareness of standards and testing practices across your team
What’s planned for future versions of Application Express Into the future
Into the FutureWhat’s planned for future versions of APEX • White paper on how to build accessible applications with APEX underway • Planned removal of modes (bug #14198613) • Further adoption HTML 5, WAI-ARIA & WCAG 2.0 • Incorporate jQuery UI 1.9 when released • Metadata auditing • Ongoing framework / theme improvements and fixes • Minimise VPAT exclusions • Community feedback • APEX 4.2 Early Adopters • Feature Requests
Summary • Accessibility is not just a checklist • Get your templates and theme right up front • Know the current problems in Application Express • Plan out your testing strategy and include real users • Spread awareness across your team • Watch out for the white paper!