E-mail List Archives
Thread: closest alternatives to semantic UI
Number of posts in this thread: 8 (In chronological order)
From: Michael Taboada
Date: Mon, Apr 30 2018 6:27PM
Subject: closest alternatives to semantic UI
No previous message | Next message →
Hi all,
As a bit of an introduction, I am blind, and use screen readers. I also
program in my spare time. To that end, I have been looking into
replacing semantic UI (which I hear is not interested whatsoever to add
accessibility to their framework) with something else in an open source
project [1]. So I'm looking for recommendations for frontend frameworks
that are fully accessible, but have similar or identical features to
semantic UI. Of special note is that this particular application relies
on rich controls such as searchable multiselect boxes, etc. Any help
would be appreciated.
Thanks!
-Michael.
[1] https://github.com/go-gitea/gitea
From: Steve Green
Date: Mon, Apr 30 2018 10:35PM
Subject: Re: closest alternatives to semantic UI
← Previous message | Next message →
Hi Michael,
As far as I am aware, there are no front-end frameworks that are even remotely accessible. If there are, then no one is using them. Most don't even do radio button and checkbox replacements properly, let alone rich controls.
Steve Green
Managing Director
Test Partners Ltd
From: Jeremy Echols
Date: Tue, May 01 2018 9:06AM
Subject: Re: closest alternatives to semantic UI
← Previous message | Next message →
There are some excellent resources for building a lot of rich widgets on W3C's "Aria Practices" page: https://www.w3.org/TR/wai-aria-practices-1.1/
Most everything under the "Design Patterns and Widgets" section have an example or two with pretty in-depth explanations. That's far from a framework, of course, but it's better than nothing.
From: Bryan Garaventa
Date: Tue, May 01 2018 4:19PM
Subject: Re: closest alternatives to semantic UI
← Previous message | Next message →
Hi,
All of the widgets within the AccDC TSG framework have been thoroughly tested to ensure accessibility, downloadable at
https://github.com/whatsock/tsg
The accessible widgets of which plug directly into jQuery, Dojo, or MooTools.
You can test many of these yourself here:
http://whatsock.com/bootstrap/jquery/
"As far as I am aware, there are no front-end frameworks that are even remotely accessible."
I remember us going back and forth about this not long ago on this list. I feel like a broken record sometimes.
Bryan Garaventa
Accessibility Fellow
Level Access, Inc.
= EMAIL ADDRESS REMOVED =
415.624.2709 (o)
www.LevelAccess.com
From: Steve Green
Date: Tue, May 01 2018 4:43PM
Subject: Re: closest alternatives to semantic UI
← Previous message | Next message →
Hi Bryan,
You never responded to the test results I sent you that showed that the your combobox example is flawed. I found that it works ok if users interact with it in certain ways and it behaves incorrectly if they interact in other ways. All those different ways of interacting a perfectly normal, and native comboboxes work correctly in every case. Since that was the simplest of all your combobox variants I saw no point testing the others until that one is fixed. Have you had a chance to review my results?
Regards,
Steve
From: Brandon Keith Biggs
Date: Wed, May 02 2018 2:52AM
Subject: Re: closest alternatives to semantic UI
← Previous message | Next message →
Hello,
This email list and this thread in particular are not a place to report
issues like this. Please open an issue at:
https://github.com/WhatSock/accdc/issues
where it can properly be addressed.
AccDC is the best framework I have ever seen in my life from an UX point of
view. I am looking for someone to help convert it to ReactJS:
https://github.com/WhatSock/accdc/issues/10
So please comment if you are able to help!
Thanks,
Brandon Keith Biggs <http://brandonkeithbiggs.com/>;
On Tue, May 1, 2018 at 3:43 PM, Steve Green < = EMAIL ADDRESS REMOVED = >
wrote:
> Hi Bryan,
>
> You never responded to the test results I sent you that showed that the
> your combobox example is flawed. I found that it works ok if users interact
> with it in certain ways and it behaves incorrectly if they interact in
> other ways. All those different ways of interacting a perfectly normal, and
> native comboboxes work correctly in every case. Since that was the simplest
> of all your combobox variants I saw no point testing the others until that
> one is fixed. Have you had a chance to review my results?
>
> Regards,
> Steve
>
>
From: Bryan Garaventa
Date: Wed, May 02 2018 6:53PM
Subject: Re: closest alternatives to semantic UI
← Previous message | Next message →
Hi,
Thank you, it is indeed helpful for people to open an issue on GitHub when issues are discovered with a particular widget type, because this helps me keep track of those that are open and provides a means to track related discussions.
Steve, I apologize for not getting back. I remember being confused by the format and not having time later to follow up on it, then it slipped off the radar. Please do me a favor and file an issue on the GitHub project where this widget library includes all of these widgets at
https://github.com/whatsock/tsg
For me to fix anything, it helps me to know which assistive technology you are using, which version, in which browser you are seeing this problem, and an explanation of steps to reproduce, plus a link to the relevant widget you are seeing the bug on. Then I'll be able to diagnose things better.
Thanks,
Bryan
Bryan Garaventa
Accessibility Fellow
Level Access, Inc.
= EMAIL ADDRESS REMOVED =
415.624.2709 (o)
www.LevelAccess.com
From: Bryan Garaventa
Date: Wed, May 02 2018 7:00PM
Subject: Re: closest alternatives to semantic UI
← Previous message | No next message
Thanks Brandon also for filing the React bug:
https://github.com/WhatSock/accdc/issues/10
I've already started putting out feelers to see if anybody would like to help with doing this.
All the best,
Bryan
Bryan Garaventa
Accessibility Fellow
Level Access, Inc.
= EMAIL ADDRESS REMOVED =
415.624.2709 (o)
www.LevelAccess.com