Direct link to repo: https://github.com/uswds/uswds
USWDS: The United States Web Design System
141–150 of 151 posts
Re: USWDS: The United States Web Design System
#142Earlier quoted context omitted.
I would find real peace of mind in a design system maintained by a government that guarantees compliance with that government's accessibility requirements.
Any kind of technical compliance by government is guaranteed to be old and obsolete in the near future. The reality of the situation is that this "design system" is a waste of time and it will never iterate as fast as other systems maintained by industry experts in web compliance and accessibility. This is just a case where folks are happy that our government isn't doing shit in Dreamweaver anymore and has moved on t…
> Any kind of technical compliance by government is guaranteed to be old and obsolete in the near future. The reality of the situation is that this "design system" is a waste of time and it will never iterate as fast as other systems maintained by industry experts in web compliance and accessibility.
You really ought to check out how fast this design system has iterated to date:
https://github.com/uswds/uswds/releases
> However, government should be focusing on streamlining government operations, not developing accessibility standards and reinventing the same wheel. Leave that to professionals and use what's already available.
First, I'm not sure why you think accessibility doesn't fall under streamlining government operations.
Second, the folks at USDS are top professionals from industry and are limited to a four year "tour of duty", so they aren't lifelong government employees.
Re: USWDS: The United States Web Design System
#143A good and safe UI/UX is the one not using JavaScript.
(Tossing my karma here because I find malicious JS … all … the … time with my heavily instrumented JIT browser. )
Just yesterday, I ran into a CSS/JS snippet conspired to do local net probe scanning. Further googling shows that it is a bank that is doing this.
A matter of time before such a browser-based probe finds a passive infected machines awaiting to respond with a specially-made packet.
Re: USWDS: The United States Web Design System
#144Re: USWDS: The United States Web Design System
#145Earlier quoted context omitted.
At least for our business, we need the components to do fairly specific things that are not, or only partially supported by pre-build components. So we make our own. Now they’d suck for anyone else to use, but they’re perfect for us.
>At least for our business, we need the components to do fairly specific things that are not, or only partially supported by pre-build components. I would say the moment you are dealing with business logic you are no longer dealing with something that can seriously be called a "component", that's just application development. And if you are spending developer time to build custom HTML select boxes or dropdowns in the…
> And if you are spending developer time to build custom HTML select boxes or dropdowns in the year 2022 you're really doing something wrong.
You are, of course, entitled to your opinion.
Re: USWDS: The United States Web Design System
#146Anyone with any part in designing user interfaces seriously needs to commit their section on color to heart: https://designsystem.digital.gov/design-tokens/color/overvie... Especially the contrast/magic number discussion. It's crazy how many user interfaces these days blur design elements to where you can't tell were controls are. The recent trend to eliminate window title bars is particularly infuriating, but button…
> Especially the contrast/magic number discussion. It's crazy how many user interfaces these days blur design elements to where you can't tell were controls are. The recent trend to eliminate window title bars is particularly infuriating, but buttons that don't look like buttons because they blend into the background are another pet peeve - or have light gray on dark gray. Ugh! Contrast serves a purpose! Modern UX de…
[deleted]
Re: USWDS: The United States Web Design System
#147Earlier quoted context omitted.
I would expect modern icon fonts to exclusively use the Unicode Private Use Area. Fallback fonts would then not have glyphs for these code points. Screen readers would hopefully ignore them.
Screen readers ignoring them is a problem when it is UI the user needs to interact with. How does the use know that U+E9AF is the Edit icon they are looking for versus say maybe U+E9AE is the Delete icon?
They don't. That's is why icon-only items (links, buttons, …) must always be explicitly annotated, using aria- attributes. You can do this with any icon technology. You wouldn't annotate the icon itself.
Re: USWDS: The United States Web Design System
#148Free as in "bringing freedom" not free beer: https://github.com/uswds/uswds/blob/develop/LICENSE.md
Re: USWDS: The United States Web Design System
#149Earlier quoted context omitted.
Wait why is the UK gov using a netlify.app link? I'm not a web dev so I'm not sure if that's common or more convenient
They're not, dunno where that other link came from but it's not the official. Sneaky https://design-system.service.gov.uk/components/
This is my side project, I'm a dev currently contracting at DfE. This library and the form builder[0] make working with the design system easier for Rails devs.
Re: USWDS: The United States Web Design System
#150Earlier quoted context omitted.
>In this case to a proper government domain... aha, I bet there's some policy against pointing .gov.uk hostnames to a third-party platform? Some guidance that might be relevant: https://www.gov.uk/guidance/use-your-govuk-domain-name?step-...
Doesn't seem to rule out using a .gov.uk domain name for something hosted on netlify. I agree it looks cheesy and makes me wonder if it's really official government documetnation, without a .gov.uk hostname (and SSL cert, naturally).
It's my side project and definitely not official. It's a library aimed at making it easy to use the official components[0] Rails-friendly.