3 ms·

Screen readers are browsers. They could just ... not do that.

• jay_kyburz 3y ago
  Browsers can't change their behavior.
  • danShumway 3y ago
    It is extremely complicated for browsers to change their existing behavior, and we should be cautious about them doing so. We could however introduce another attribute that has the correct behavior, deprecate `disabled`, and throw warnings during ARIA validation/linting for pages that continue to use it. Call it `blocked` or `unsusable` or have if you want to be fancy, make a `status` or something with attribute with multiple values that it accepts. Whatever seems most reasonable. But my point is we're not trapped in the world of developers needing to poorly replicate browser functionality for every single form they make; we could still have an attribute that makes it easy for developers to by-default program forms with the correct behavior. In Javascript, adding `let` and `const` didn't require us to get rid of `var`. We didn't have to change `var` behavior to make `let` throw errors on redeclarations. There are options here for providing tools within browsers that work correctly.
  • Lornedon 3y ago
    Why not?
    • gpvos 3y ago
      They can, but they have to think a lot about backwards compatibility and existing code. So sometimes they can't, and in this particular case I think it's going to be hard, mostly because of existing Javascript code. Also there's standardization and coordination between browsers, but if there is a genuine need for something they tend to find a way.