Name of Product: Klaxon Application (https://app.klaxon.io)
[note: this is a licensed site and can only be access with appropriate license and permission].

  At Klaxon, we are committed to ensuring digital accessibility for people with disabilities.  Since inception, we are continually improving the user experience for everyone and applying the relevant accessibility standards as the product design matures.  We are aiming to conform to WCAG 2.2 AAA as our long term commitments as part of product design.  

 As majority of our users are recipients of emergency notification via SMS, Text and Email, they do not interact with Klaxon Application directly.  For those users who does, you should be able to do the following:
  1. Zoom text to at least 200% without content spilling off screen
   2. Navigate and operable through most of the site using a keyboard
   3. Listen to most of the site using a screen reader
   4. Sufficient contrast on contents to improve readability  

Conformance Status

The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility for people with disabilities. Currently, is Klaxon application is partially compliant WCAG 2.2 AA with limitations identified below for most of the users.  

Limitations and Alternatives

Despite our best efforts to ensure accessibility of Klaxon Application, there may be some limitations. Below is a description of known limitations:
  1. Tab navigation

- Internal Reference no: ACC-N005, ACC-N010
- Known Limitation: Tab navigation for some pages maybe out of sequence affecting screen reader output for limited number of users (i.e. administrator)
- Alternative Solution: We are working to address these issues, and in the meantime, users can familiarise with the current sequence.  

 2. Notification title
- Known Limitation: Title of notification not read by screen reader  
- Alternative Solution: Contents of the notification body usually includes the title; hence impact is not critical. This is one of the items to address in future development sprints.  

3. Admin accessible button
- Known Limitation:  The incident button use by Admin only are not readable by screen reader - Alternative Solution: We are working to address these issues  

4. Mobile Consideration
- Known Limitation: due to the number of contents the site is designed to display, it is not the best experience to view it on small screen i.e. smartphone.  
- Alternative Solution: For better user experience, all users are encouraged to download and use the Klaxon App from Apple App Store or Google Play Store.    

Feedback and Contact Information

Klaxon always welcome your feedback and collaboration on the accessibility of our application. Please let us know if you encounter any accessibility barriers:
Email:
support@klaxon.io
We aim to respond to accessibility feedback within 14 business days.