How does apt render its fancy progress bar?

Re:How does apt render its fancy progress bar? by ClumsyPilot on Wednesday October 13, 2021 @08:28AM (#28851277)

"Applications should share the core business logic, but have entirely seperate "frontends" for every situation."

I think its clear from your post that you have never dealt with the visually impaired or even explored accessebility options of iOS/MacOS/Windows. We have working accessebility for all applications throughfully designed with native OS controls.

Having separate front ends will never happen, most businesse sproduce a single bloated JS app that crashes equally on all platforms.

[ Parent | on HN ]

Re:How does apt render its fancy progress bar? by jhgb on Wednesday October 13, 2021 @10:36AM (#28852634)

> I think its clear from your post that you have never dealt with the visually impaired or even explored accessebility options of iOS/MacOS/Windows. We have working accessebility for all applications throughfully designed with native OS controls.

...which is a simple consequence of Windows people not being used to polyvalent software. You're putting horse before the cart.

[ Parent | on HN ]

Re:How does apt render its fancy progress bar? by csmpltn on Wednesday October 13, 2021 @08:50AM (#28851448)

> "We have working accessebility for all applications throughfully designed with native OS controls."

The comment I'm responding to says that progress bars in the terminals, and that TUIs in general are an accessibility nightmare.

Are you disagreeing? Are you claiming that it's a solved problem? Would you mind elaborating on what you think can be done to solve this?

[ Parent | on HN ]

Re:How does apt render its fancy progress bar? by nightpool on Wednesday October 13, 2021 @09:35AM (#28851882)

You're misinterpreting the GP's post, TUIs are not "thoughtfully designed with native OS controls".

[ Parent | on HN ]

Re:How does apt render its fancy progress bar? by csmpltn on Wednesday October 13, 2021 @01:58PM (#28855341)

No, that's exactly my point.

The bulk majority of applications people use today are not "thoughtfully designed with native OS controls". Sprinkling some ARIA labels around is better than nothing, but the experience itself is extremely limited and is not on-par with what those people deserve.

I'm talking about Javascript/CSS-heavy websites in a web-browser, computer games, or software such as Blender/SketchUp/Google Earth to name a few. ARIA labels aren't good enough here - we would need to develop an entirely different interface to accomodate for each individual accessibility scenario. You can imagine a blind person and a deaf person using entirely different versions of Blender, each built with a different interface accomodating a specific disability.

[ Parent | on HN ]