Skip to content

Instantly share code, notes, and snippets.

@aguilavajz
Created April 3, 2026 21:19
Show Gist options
  • Select an option

  • Save aguilavajz/1389a632064e34b7791f96c93a4d9e3e to your computer and use it in GitHub Desktop.

Select an option

Save aguilavajz/1389a632064e34b7791f96c93a4d9e3e to your computer and use it in GitHub Desktop.

πŸ“‹ APEX Accessibility Quick Guide

Why Accessibility (A11y) Matters

Accessible applications are inclusive, professional, and compliant with international standards like WCAG 2.1. This guide provides a practical checklist to ensure your Oracle APEX applications are usable by everyone.


Developer's Quick Checklist

Forms and Inputs

  • Every Item Needs a Label: Even if hidden visually. Use the "Hidden" template but always define a label.
  • Meaningful Error Messages: Clear, descriptive error messages that guide the user on fixes.
  • Required Flags: Correctly set "Value Required" to inject aria-required="true".

Navigation and Structure

  • Logical Heading Hierarchy: One H1 per page (title), followed by logical H2, H3.
  • Skip to Main Content: Ensure the Universal Theme's "Skip to Main Content" link functions.
  • Landmarks: Proper use of regions (e.g., Breadcrumb, Main Content) for navigation.

Visuals and Media

  • Color Contrast: 4.5:1 ratio for normal text. Use the Theme Roller integrated checker.
  • No Color Soloing: Never rely solely on color for meaning (e.g., use Icons + Red for errors).
  • Alternative Text: Meaningful Alt text for images, charts, and icons.

Testing and Validation

  • The "No Mouse" Test: Complete a primary business flow using only the keyboard.
  • Accessibility Tab (Page Designer): Refresh and resolve all identified structural violations.
  • Screen Reader Check: Occasionally test with JAWS or NVDA on critical complex screens.

πŸ“ˆ Elevate Your APEX Applications

Connect & Stay Updated

Work With Me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment