joelanman

so if you wrote a book in Google docs, Google should have just as much right to it as you? Or Microsoft should have just as much right to the app you write in VS Code?

Each person would ask a question on their mic, they're not using one shared laptop

also it's not named horizontal and vertical because it depends on the direction of the text - some text reads vertically

'protected' how?

it's also possible they had very limited vision and used very high magnification, where indentation might be actively unhelpful since you'd just see lots of blank space at times

I always think this should be an incident in itself - why did our status page not reflect the reality of a degraded service? It's so common that they don't, and something user-driven like DownDetector is often more reliable

I used the page title as per the guidance, but clearly its not very helpful. This is actually an important piece about Google search:

> It’s been over a year since I last told you to just buy a Brother laser printer, and that article has fallen down the list of Google search results because I haven’t spent my time loading it up with fake updates every so often to gain the attention of the Google search robot.

> It’s weird because the correct answer to the query “what is the best printer” has not changed, but an entire ecosystem of content farms seems motivated to constantly update articles about printers in response to the incentive structure created by that robot’s obvious preferences. Pointing out that incentive structure and the culture that’s developed around it seems to make a lot of people mad, which is also interesting!

Yeah it is ableist, it's hard to imagine a game making fun of any other illness or disorder these days.

this wouldn't be accessible would it? For example to screen readers, so just wondering what the use case is over accessible tech

traditionally, lack of accessibility has unfortunately not held back people's use of tech, see Flash and most SPAs

that would be nice but when Apple dropped Flash it was Flash that died

Not the same, but some similar modern games:

- Pikmin

- Zombie Night Terror

- Humanity

A related old art project: Making a toaster from scratch by Thomas Thwaites

https://www.dezeen.com/2009/06/27/the-toaster-project-by-tho...

Penpot is too https://youtu.be/r-USvt_p46g

I use Elk Mastodon client - being able to install it as a PWA is great - I get a nice icon on my mobile screen same as any other app, and it runs full screen without an address bar. I can switch between it and other apps, I don't see the downside really

Gmail has recently become extremely slow for me in Safari on a well specced M1 max

People who need to zoom in a lot in order to use it. In practice this gives you a small screen view. It's a WCAG requirement

You're right! Mistake on my part

They very much killed the golden goose. It's a real failure to think in terms of systems. Google relies on a healthy open web, yet as arguably the biggest single influencer of the web it has completely failed to maintain that let alone improve it.

Reminds me of my old GSmart Mini 2, fantastic little credit-card sized camera. No screen was part of the fun

https://www.productindetail.com/pf/mustek-gsmart-mini-2

I think I just didn't realise how poor placeholders are in general at that point, compared to just having visible labels/examples. Placeholders disappear when you start typing and have poor contrast

author here, just to note our current design pattern for this is slightly updated: https://design-system.service.gov.uk/components/date-input/

we have a blog post on why: https://technology.blog.gov.uk/2020/02/24/why-the-gov-uk-des...

author here, for known dates like date of birth it's still easier and faster to just type it in. Also type=date has accessibility problems and the design varies a lot, so people might get a decent experience on one browser/OS and a really poor one on another

We removed it from GOV.UK in 2016:

https://designnotes.blog.gov.uk/2016/11/28/removing-the-exte...

I've tried a bunch and plantnet is the best so far

We'll be publishing soon on the GOV.UK Design System, but in summary we can't make browser validation consistent with our Design System, or guarantee it's always accessible.

In our research it's commonly most often helpful to validate when the user submits as that's when you can be sure they're 'done'. There are cases when realtime helps so it's fine to add it in those situations.

Important to note that in the article we mention we only use pattern to trigger the right keyboard in old iOS. We actually turn off HTML validation in favour of doing server side validation, we'll soon be publishing guidance on that too. Disclaimer - I work on the team.

The article covers quite a few issues with type=number, including some pretty bad accessibility ones. On balance I think even if inputmode doesn't have 100% support, those users will simply get a normal keyboard, which isn't so bad. Disclaimer - I work on the team.

update - here's the original calendar design challenge:

http://www.elzr.com/blag/infodesign-challenge/