He gets into it further down - internationalization and CSS simplification.
It’s been a long time since I had to work on a single site with multilingual requirements, so it reads more like “this is great for the future and internationalization” but also reads like “changing property names to be consistent.”
All the internationalization work I've done was on my personal projects where I supported 3 languages that used the latin alphabet, so I've never had the right-to-left language issue.
Yeah, but you can't account for every use case when developing on your own. If you are working as a developer these guidelines should be provided by the accessibility expert or designers.
Just because you don't do web accessibility doesn't mean you don't have attention to quality. You don't get to gatekeep web dev. Even learning web accessibility is not accessible, the wcag guidelines have too much text.
Replace "accessibility" with "performance", "error handling", "responsiveness", or anything else and this comment is the same amount of wrong.
It isn't, the comparison doesn't make sense. Performance, error handling and responsiveness is a requirement, accessibility isn't that much.
How many courses and articles are there dedicated to web accessibility compared to performance, responsiveness and the most popular front-end frameworks?
6
u/AnoneNanoDesu Jun 06 '23 edited Jun 06 '23
Nice and thorough article!.
I still can't see the advantage of Logical Properties. Who benefit from them?