3 ms·

You just can't expect a script to make a website accessible. Accessibility cannot be fully automated. Sure there are tools that can highlight some issues, and p

by scoot 4y ago

You just can't expect a script to make a website accessible. Accessibility cannot be fully automated. Sure there are tools that can highlight some issues, and provide guided review to help find others, but there's no panacea. Instead, start with a UI library that already applies accessibility best practices, such as Material UI [0], then follow the guidance provided for each component (a library can't do everything for you, despite what many claim), as well as applying accessibility best practices to the site as a whole. Only then apply automated review, and manual review by accessibility experts, fixing issues raised at each stage. Disclosure – I contribute to Material UI. [0] https://mui.com/material-ui/react-text-field/#accessibility https://mui.com/material-ui/react-text-field/#accessibility

geraldwhen 4y ago
That’s great until design decides that modals shouldn’t close with the escape key and users should be forced to scroll a text field and click a toggle to navigate away. Then some data elsewhere on the page animates to a new value, and the user should be notified of this data immediately. Designers don’t like using prebuilt components. I haven’t found one yet that can live with constraints.
- scoot 4y ago
  It sounds like design needs to be educated on accessibility. That said, all this and more is possible with Material UI. It's designed for flexibility and customizability in both functionality and appearance. That doesn't make it okay to break accessibility though.
  - geraldwhen 4y ago
    Until you need to theme some tabs because design must align the text and icons -just so- and quickly find that not everything in material is themable. Some things are missing. So you style deep dom elements that break when you upgrade material, if you ever do, because upgrading is now too expensive with the Frankenstein you’ve tried to jam into material’s default styles. I’ve worked with many, many designers. None of them have ever liked working with constraints. Even getting a single designer to commit to a color palette is pulling teeth.

by scoot 4y ago

geraldwhen 4y ago

That’s great until design decides that modals shouldn’t close with the escape key and users should be forced to scroll a text field and click a toggle to navigate away. Then some data elsewhere on the page animates to a new value, and the user should be notified of this data immediately. Designers don’t like using prebuilt components. I haven’t found one yet that can live with constraints.

scoot 4y ago
It sounds like design needs to be educated on accessibility. That said, all this and more is possible with Material UI. It's designed for flexibility and customizability in both functionality and appearance. That doesn't make it okay to break accessibility though.
- geraldwhen 4y ago
  Until you need to theme some tabs because design must align the text and icons -just so- and quickly find that not everything in material is themable. Some things are missing. So you style deep dom elements that break when you upgrade material, if you ever do, because upgrading is now too expensive with the Frankenstein you’ve tried to jam into material’s default styles. I’ve worked with many, many designers. None of them have ever liked working with constraints. Even getting a single designer to commit to a color palette is pulling teeth.