zichy

10 ms·

1. 61.▲
   by zichy 4y ago

   That's a nice way to say "I don't care about accessibility".
2. 62.▲
   Tetsuji: Remote Code Execution on a GameBoy Colour 22 Years Later(xcellerator.github.io)

   2 points by zichy 4y ago|0 comments
3. 63.▲
   by zichy 4y ago

   Using this as an opening sentence without any irony is the worst thing I ever read.
4. 64.▲
   by zichy 4y ago

   Speaking of Geoguessr, I can definitely recommend Geotastic[1] – a free and donor-funded alternative. [1]: https://geotastic.net
5. 65.▲
   by zichy 4y ago

   Having the supposed foresight, I can tell that cryptocurrencies are definitely part of the dystopia.
6. 66.▲
   by zichy 4y ago

   >get rid of the buzzwords such as 'SEO' and 'accessibility' to just think of putting the customer first >a customer first ethos and not treat them as 'disabled' That's a weird way of phrasing it. It
7. 67.▲
   by zichy 4y ago

   This together with some padding could help: <meta name="viewport" content="width=device-width, initial-scale=1">
8. 68.▲
   by zichy 4y ago

   Question yourself every step of the way if you are creating barriers for anyone. To get your started, I recommend this short summary about universal design, inclusive design, and accessibility: https://sayyeah.com/digital-in
9. 69.▲
   by zichy 4y ago

   Trying to be edgy is truly terrible as well.
10. 70.▲
    by zichy 4y ago

    Please keep accessibility in mind when creating forms. I just checked out the demo app and you are using `placeholder` instead of `label`.
11. 71.▲
    by zichy 4y ago

    Finally, a platform where you can say anything you want created by "a bunch of bored incels". And I can already see holocaust denial and transphobia.
12. 72.▲
    by zichy 4y ago

    The fact that there are many bullshit companies out there does not change the fact that all web3/blockchain companies are bullshit.
13. 73.▲
    by zichy 4y ago

    Every single job posting is from a weird crypto bullshit company. Great.
14. 74.▲
    by zichy 4y ago

    https://news.ycombinator.com/item?id=31372373
15. 75.▲
    by zichy 4y ago

    I totally get the minimalist approach to websites, but using plain text instead of semantic HTML elements means giving up accessibility. People who rely on screen readers will not be able to read your content in a pleasant way.
16. 76.▲
    by zichy 4y ago

    Nice work! I have two suggestions usability-wise: * Make sure your navigation is consistent. The left filter links and the about/contact links are missing on many pages. A breadcrumb would help as well. * The horizontal tabs on the rec
17. 77.▲
    by zichy 5y ago

    Really nice showcase. While I like non-JS solutions, some kind of JavaScript is almost always needed when creating interactive elements to ensure accessibility.
18. 78.▲
    by zichy 7y ago

    Good job so far, it feels very lightweight and simple. It works well with different input devices, but the accessibility for screen readers could be improved: * The first day immediately gets focused when opening the datepicker. It might be
19. 79.▲
    by zichy 7y ago

    >I don’t think anyone outside academia values the lives of murderers very much What.
20. 80.▲
    by zichy 7y ago

    Jesus, there is just so much going on. The drop-down menu is huge and too tall for my browser window. I clicked through some of the components, you should learn some basics about accessibility. (Also, this is your third time promoting thi
21. 81.▲
    by zichy 7y ago

    1. I get that short and simple code snippets are important in order to understand the fundamentals of a framework, but people with little experience will just copy the code in your documentation 1:1. I believe that semantic and accessible c
22. 82.▲
    by zichy 7y ago

    Thanks! Besides, please consider to make headlines bold again. That would help a lot with content hierarchy.
23. 83.▲
    by zichy 7y ago

    Whenever I stumble upon yet another UI/CSS framework, I always check the form elements first. Here we go.[1] * _Every_ input needs a <label>. * Use the `for` attribute to connect labels and inputs. * Placeholders are not a replac
24. 84.▲
    by zichy 7y ago

    Raleway is such a poor typeface choice. They even forgot to import the italic styles from Google.
25. 85.▲
    by zichy 7y ago

    I don't get why this is supposed to be particular accessible. <img> is perfectly fine, the alt attribute should describe the contents for users with screen readers and crawlers.
26. 86.▲
    by zichy 8y ago

    1. Please do not import external resources from Google Fonts if you don’t have to. (Hint: You never really have to.) 2. If you want to use as little CSS as possible, simply use `sans-serif`. Otherwise try this font stack: http://
27. 87.▲
    by zichy 8y ago

    I hate this type of article. The headline is "Lazy load images with zero Javascript", so I naturally expect to read about a technique which makes that possible. First of all, the author shows two techniques _with_ JavaScript (by t
28. 88.▲
    by zichy 8y ago

    Please do not remove the link underline in continuous text. It makes the links inaccessible for people who cannot perceive color differences.[1] [1] https://www.w3.org/TR/WCAG20-TECHS/F73.html
29. 89.▲
    by zichy 8y ago

    I just received this email from you: >I’m going to send you a few emails over the next couple of weeks to give you some hints and tips. Yeah, so I just marked your email address as spam. I never subscribed for any newsletter and there is
30. 90.▲
    by zichy 8y ago

    Seven years aren't "surprisingly short" just because there are games which development took even longer.