Categories
- All Categories
- Oracle Analytics and AI Learning Hub
- 44 Oracle Analytics and AI Sharing Center
- 20 Oracle Analytics and AI Lounge
- 278 Oracle Analytics and AI News
- 56 Oracle Analytics and AI Videos
- 16.2K Oracle Analytics and AI Forums
- 6.4K Oracle Analytics and AI Labs
- Oracle Analytics and AI User Groups
- 103 Oracle Analytics and AI Trainings
- 20 Oracle Analytics and AI Challenge
- Find Partners
- For Partners
Accessibility Settings/OAC Users with a Disability
We are currently in the middle of implementing FAW/FDI and OAC as part of a company Oracle ERP roll out. One thing we have recently tested is accessibility for colleagues with disabilities and it's posed some really good questions.
Are there any current accessibility settings to support Keyboard only users, the visually impaired, colour blindness, audio description as part of OAC?
If not, are there any plans to include some settings for accessibility purposes in the application in the future?
Best Answer
-
@Rob Toogood Oracle has been an active participant in the development of the WCAG 2.2 accessibility guidelines, and will implement the additional WCAG 2.2 success criteria after WCAG 2.2 is published. Oracle is closely tracking the progress of EN 301 549, and will adopt additional EN 301 549 criteria in fiscal year ’25.
Refer:Updates to the Accessibility Standards
https://www.oracle.com/in/corporate/accessibility/policy/#policies
For Accessibility Features and Tips for Oracle Analytics Cloud,
Refer Enabling Accessibility Mode for Oracle Analytics
https://docs.oracle.com/en/cloud/accessibility/accessibility-features-and-tips-oracle-analytics-cloud1.html#GUID-E4698A81-025B-4588-B8AB-2EB312596C040
Answers
-
How can you set a tab or focus order in Oracle Analytics Cloud (FDI) in a Workbook?
Using a keyboard only to tab to elements on Canvases to set focus elements like Visualisations and deselect non interactive elements such as Spacers or Date Time Parameters?
WCAG 2.2 AA is the new minimum accessibility standard for all UK Government public sector websites and mobile apps
The Web Accessibility Guidelines (WCAG) 2.2 keyboard accessibility tab order, or focus order, should be logical, intuitive, and follow the visual flow of the page. The tab order should generally follow this sequence:
Web browser page
Canvas page
Prompt / Filters
Visualisations left to right by row (top to bottom
0

