What I often find such an interesting take in #accessibility discussions is this concept of "We will make it work for the majority first, and then add accessibility features".
This shows a fundamental misunderstanding of how accessibility, and therefore " features" of accessibility work.
For one, making something #accessible for #screenReaders often requires no visual modifications at all, and requires making calls early in the development cycle to not have to rewrite your entire UI using widgets that even support #assistive #technology. Once that call has been made, making elements accessible is often a matter of, what a concept, using the widgets the way they were meant to be used.

What I often find such an interesting take in #accessibility discussions is this concept of "We will make it work for the majority first, and then add accessibility features".
This shows a fundamental misunderstanding of how accessibility, and therefore " features" of accessibility work.
For one, making something #accessible for #screenReaders often requires no visual modifications at all, and requires making calls early in the development cycle to not have to rewrite your entire UI using widgets that even support #assistive #technology. Once that call has been made, making elements accessible is often a matter of, what a concept, using the widgets the way they were meant to be used.