Does Sorting Activity in Rise 360 work with screen readers?

This must be a design flaw rather than a bug, a mistake in code, otherwise it would have been a quick fix. Treating these things as bugs means doing nothing for four years (four years!) which makes it look like Articulate's ok with designing discrimination into their product. I do believe Articulate's not ok with that, but really needs to prove it by just getting on and properly redesigning these interactions that aren't accessible. Maybe a different internal route is required to cover unacceptable usability/accessibility design so these things aren't treated alongside genuine bugs.