accessWidget is a game-changer in web accessibility, simplifying and streamlining the process of becoming accessible and compliant using AI, machine learning, and computer vision.
This product will not fix your web accessibility. It is a band-aid on a broken leg. Automated accessibility scanners can only find about 30% of accessibility issues. The rest needs a human to review and suggest solutions. You need to provide machine-readable information so that users of assistive technologies, like screen readers, can interpret websites correctly. This product duplicates functionality users already have and guesses fixes. It is not sustainable change but accessibility lip service. See this blog post for more information: https://adrianroselli.com/2020/0...
@yatil you are the expert...though Rome wasn't built in a day. I would imagine that the efficiency of machine learning is what makes this service affordable and scalable. I would assume that over time the service will improve. Just bringing awareness that accessibility is a challenge for many people and there are solutions out there is a positive.
@leadoneer The issue here is that some changes that would need to be done are impossible for a computer – even with AI – to figure out. What was the intention of the text? If I find a bold large text, is that a sub heading of the prior heading or a heading of the same level? There are things that can be automatically fixed, but this product expects users to go into a special mode, which they need to find and access.
@leadoneer@yatil That issue was addressed in another reply up above for mobile devices.
It is my understanding that it recognizes screen readers and welcomes the user audibly with options.
And as soon as someone uses the tab to navigate, it automatically activates keyboard navigation.
@leadoneer@growmap Yes. On an accessible site that is not necessary. What if you’re on a train and your JavaScript does not load? What if you don’t want to be tracked by external trackers. Everything that the tool does can be built-in first party. And not missing 70% of critical issues.
@leadoneer@yatil I don't think anyone would argue that building the site 100% accessible in the first place or having it optimized to that level is an excellent goal.
But that is a major project and there are more sites that need it done than experts to do it. So why not utilize this first and then work on manually making improvements, too? They aren't mutually exclusive, right?
If your business is accessibility, make your site 100% accessible.
- You have duplicate IDs
- The carousel is not accessible
- Contrast problems
- At some place the heading hierarchy is wrong
- ...
@hotgeart Hi Thomas, this is a classic case of testing accessiBe without an actual screen-reader or by navigating the keyboard. accessiBe modifies the session on the fly, while users interact with it. You can't just test the source code, it doesn't work like that. Happy to set you up on a demo :)
@shir_ekerling1 I don't need to open NDA to know the titles will be miss leading. For the keyboard navigation I did, if you want examples: your main menu. When you press tab you need to focus on the first item if i press tab again I need to go to the next focusable item other than the menu items. If I want to go in the rest of the menu items I need to use the arrows keys and space/enter to open the submenus bonus if I can do to the first element with HOME and last with END key. Your carrousel: the controls need to be the FIRST focusable items, also same for the menu (tab ->next focusable element outside of the carrousel). But hey WTF do I know? I only do websites for the federal gouvernement of Belgium and some EU institutions. Those sites are checked and validated by two org. But yeah I do rookie mistake, like just checking the source code 🤷♂️.
@hotgeart Funny thing is, this is exactly how accessiBe works. On our site, and all other sites using accessiBe. It just comes to show that you haven't even attempted to navigate the site using the keyboard. And that's a shame. Again, I'm more than happy to set up a Zoom session and personally walk you through how accessiBe works and show you everything live. I'm more than happy and open to receiving feedback or even criticism but not in the form of trolism like some of you do here, that won't help. Not you, and not us. BTW - we have hundreds of government websites, law bars and state attorneys. Believe me, they all have tested accessiBe thoroughly.
@shir_ekerling1 I'd love to take you up on a Zoom session. I'm a grad student researcher at Cornell just starting on work involving making tech and the internet accessible to people of all abilities.
Hi everyone
I’m thrilled to share accessiBe with you today!
Before my co-founders and I started accessiBe, the only way to make a website accessible was through tedious and expensive manual code development. This made website owners reluctant to start and left people with disabilities shut off from the digital world.
accessiBe uses AI and automation to make any website fully accessible and compliant with legislation. You just implement one line of code, accessiBe does the rest. With such a simple and effective solution, website owners don’t have to think twice before opening their sites to people with disabilities.
But giving people with disabilities access to the Internet isn’t just about making their lives better, it’s about improving the lives of everyone. Access to the Internet encourages the spread of knowledge, creativity, and contribution to society. By ensuring that people with disabilities have access to the web, we’re not only granting them basic rights but we’re granting ourselves a more progressive society.
Thank you for joining us on this journey, let us know what you think!
@johnrampton Ah, interesting. I just had a look on your blog. Most of the accessibility issues could probably be addressed in a couple of hours, one thing that this tool seems to do is to hide the options behind the Categories dropdown but does not give the dropdown functionality to keyboard users. This could be easily changed in your code (probably like 3 lines of JavaScript around the dropdown code). But it certainly feels like an oversight or bug in this tool, @shir_ekerling1.
This is a piece of crap. Accessibility cannot be fully realized with a bolt-on script. Only about 30% of accessibility issues can be detected and address through automation. That leaves 70% of your site's accessibility issues left uncovered. You need to test your site with people who use assistive technologies and various abilities. You can't code your way out of this.
Happy to hear that web accessibility awareness is growing. My uncle is quadriplegic and one of my friends is blind...I can't imagine how hard could be to browse the internet without the solution offered by providers like accessiBe. Web accessibility should be for ALL!
@benln, great question!
When a user enters an accessiBe website through their mobile phone with assistive technologies (VoiceOver, TalkBack, etc) enabled, they will receive an announcement letting them know that screen reader adjustments are available. Then, they can use the right swipe and left swipe just like keyboard users use Tab and Shift+Tab. Likewise, they can double-tap as an equivalent to the Enter key.
This is a great tool to help website owners have their websites be accessible to everyone as well as have their websites be ADA-compliant. I would recommend everyone use this product if their websites don't currently meet the standards set out by the law.
@lorrainereguly Unfortunately those websites would probably still not meet the standards set out by the law: adrianroselli.com/2020/06/accessibe-will-get-you-sued.html
Replies
Moonshot OKR Notion Template
accessiBe
accessiBe
accessiBe
Calendar.com Scheduling Chrome Extension
accessiBe
Calendar.com Scheduling Chrome Extension
accessiBe
Chatway
accessiBe
accessiBe
accessiBe
Chatway
accessiBe
accessiBe
accessiBe
Notion
accessiBe
Dashly
accessiBe
accessiBe
accessiBe