Comprehensive Fix for Screen Readers & Accessibility Settings
in progress
Jonathan haber
This task aims to completely resolve all issues related to screen readers and accessibility settings within the application. The focus will be on:
Improving ARIA roles and attributes to ensure compatibility with assistive technologies.
Fixing navigation issues that hinder screen reader users from accessing key features.
Enhancing contrast, focus states, and keyboard interactions for better usability.
Ensuring compliance with WCAG 2.1 standards for an inclusive experience.
This will be a high-priority initiative to make the platform fully accessible for all users. Please upvote if you support this improvement!
Jonathan haber
in progress
Jonathan haber
Comments from another post on this
I finally got the work I did to production ( that means you can see it and use it as a client ), so you should see a lot of improvements. Its far from perfect so I also created a project around improving it
Im just learning about what works, right now Im shooting for having the tab button move through any menus and options on any screen, and everything having aria labels so its correctly announcing things.
Im still struggling with understanding how to handle when your in a menu of items like on ixcoach.com/explore and theres another row of things, like explore will have a section of "presence based coaching methods" but then a different button is needed to get into that list of methods instead of just to the next menu ...
Im thinking up and down keys are my friends here, so Ill try to first make sure everything is labeled well, then go into fixing this...
We have probably 500 or so buttons in likely what is about 1,500 pages of code, so its slow going but I am committed to making it work for you and every other person that needs the accessibility features ... so glad you spoke up
K
Krista Giannak
Jonathan, thanks so very much!
Interestingly, as a user, I don't see 500 buttons. I only see a few. For instance, the unlabeled buttons to send/regenerate and to use the mic or play. Also the labeled buttons in the menus, of which there are only a few.
Most elements in Explore or Pure have links or other cues next to the buttons, thank goodness!
The Play button has some sort of tooltip label or something that says "Speaker." I guess I'd have to dig into the source code to find where that's coming from, but I can tell you now that it's read out about a second after coming to the button, though it may not be read out at all.
Would two brief screencasts be helpful: one for iOS web view and one on my PC? Then you could see the workflow and catch which buttons to focus on.
Maybe many of the buttons are in creating the coach? I have not tried that.
Jonathan haber
Krista Giannak: ABSOLUTELY!
I got overwhelmed trying to finish this task after the first day or so but I have new tools that code for me while I manage so I think i could get it finished pretty quickly now, and yes if you coul d show me your main workflow I can absolutely fix those.
The top menus in the coaching dashboard open to long menus, each of which open to pages, and yea, theres somewhere around 100 pages in the code depending on what path you take, some of them are 10 to 30 pages of actual code long, some even longer.