> Twitter’s Entire A11y Experience Team Let Go
A8y "A11y" s4s f1r accesibility. (Apparently "A11y" stands for accesibility). "Twitter is better in the app" is not a sign of "accesibility". Sign in is not a sign of "accesibility".
A8y "A11y" s4s f1r accesibility. (Apparently "A11y" stands for accesibility). "Twitter is better in the app" is not a sign of "accesibility". Sign in is not a sign of "accesibility".
- alt text on images which is helpful for blind people (but also helpful for search and ML image categorisation)
- keyboard navigation which is helpful for users with motor problems (also helpful for power users)
- responsive design, which is very helpful for screen readers because it controls information flow (also helpful for users on devices that don't have the specific viewport specs that the designer aimed for)
Literally every accessibility feature you can name is like this - they all improve accessibility for disabled users and make things better for everyone else. Throwing out accessibility doesn't just hurt a minority of users who needed those features. It hurts everyone.
Doesn’t apply to accessibility except in the sense that widgets must be operable 1) by sighted persons using the keyboard, and by non-sighted persons 2) using screen reader shortcuts or 3) accessibility devices such as game controllers or sip-and-puff controls mapped to those shortcuts.
No but many studies have shown that designs (in architecture as well as web and print design) that focus on accessibility are rated as having better UX by the general populace as well
Cutting a11y likely will also lead to a decline in UX in general
This has been a common term since a few decades ago. No need to be snarky if you don't understand something.
If you are into making software for something more than just the naive "one market" your first introduction would be internationalization which should be the most widespread. When you make things for government in the EU/US you will most probably have laws demanding accessibility features. The problem isn't the numeronym but that so few people care about accessibility.
Tbh a11y is the main one that makes sense. I don't get what the point of i18n and l10n acronyms is besides saving us some typing and generally fitting into the vague category of "giving a crap about users often not considered in design"
It’s also the reason why Arabic text can be output on the screen, Ruby characters can be used and screen mirroring is usable for UIs that need RTL layouts. You really should look it up before criticising it.
It deals with things as small and as important as date formats, number seperators, punctuation marks, monetary formats, support for different calendar systems, capitalisation rules… you name it, it encompasses it.
It’s a genuine discipline. It’s used extensively in Windows, Mozilla and LibreOffice.
https://en.wikipedia.org/wiki/Internationalization_and_local...
idk if you're responding to the wrong user, but I never made the claim that it hasn't been...
The point was that having a landing page that goes to a Sign Up option before showing all the content is not necessarily an accessibility issue, it's a decision made to drive sign ups and therefore revenue and it's not something the a11y team would've been in charge of. Blind people can still navigate the page provided the components are accessible in the same way sighted users can.