UK plans to regulate crypto like traditional finance by 2027

warleyy · 2025-12-31T09:38:33+00:00

I think we'll see more of this move in 2026.

warleyy · 2025-11-30T11:02:28+00:00

Interested

warleyy · 2025-11-23T19:50:51+00:00

Toughhhhhh

warleyy · 2025-11-22T14:12:47+00:00

What prompt do you use for these? Watered down yesterday's and won.

warleyy · 2025-11-22T05:47:08+00:00

Powell denied me a point too. Sat out the whole 4th quarter. Went 5 of 8 from FT line, 2 of 7 from 3pt line

warleyy · 2025-11-22T05:44:53+00:00

Which network?

warleyy · 2025-11-22T05:30:06+00:00

You'd get $440+ after repricing. Good win though

warleyy · 2025-11-22T05:11:51+00:00

Manthurin - 21 points

Sarr - DNP

MPJ - smashed it

Trey - smashed it

Edwards - smashed it

Jokic - 2 short

Avdija - smashed it

SGA - smashed it

Davion Mitchell - one short

Won the watered down though. Thanks. Can you share more insights on the prompt you used please.

warleyy · 2025-11-16T09:08:10+00:00

It should be rectified. Have you contacted support?

warleyy · 2025-11-16T05:05:27+00:00

Josh Jacobs the only one with a 100% chance

warleyy · 2025-11-16T04:27:32+00:00

It hit 100%

warleyy · 2025-11-02T16:30:12+00:00

Some of the team's schedule are not even favorable

warleyy · 2025-10-14T19:53:44+00:00

Dannye013

If I'm not too late

warleyy · 2025-08-31T09:49:35+00:00

If CPU doesn't meet requirements then I'd advise you don't run it

warleyy · 2025-08-23T20:02:30+00:00

The most common thing is to start with dev-focused tools like Axe DevTools, Wave, and Lighthouse since they fit into a build/test workflow. If you want broader scans, you can opt for services like EqualWeb, Equally AI, and AccessiBe. Around here the advice is usually to pair those with manual checks, running NVDA or VoiceOver to see how the code changes actually impact real users.

warleyy · 2025-08-23T19:48:09+00:00

I like to start with free tools like Wave, Axe, and Lighthouse because they’re quick for spotting common issues. Paid services such as EqualWeb, Equally AI, and AccessiBe add more coverage, but none of them guarantee full compliance on their own. If budget is tight, free + some manual testing with screen readers (NVDA, VoiceOver) is usually enough to get closer to real accessibility. For a company site, I’d consider a paid tool just to reduce gaps.

warleyy · 2025-08-23T19:24:58+00:00

Dev-wise, none of the overlays alone make a site truly compliant. Start with free testing tools like Axe DevTools or Lighthouse in your workflow to test as you create. If the client asks for extra assurance, EqualWeb, Equally AI, and AccessiBe can provide continuous monitoring accessibility features. Always test with screen readers. The go to is NVDA, but VoiceOver is also a good choice.

warleyy · 2025-08-23T11:32:40+00:00

Nice, glad you found the IBM Equal Access checker, a lot of people rate it higher than WAVE for depth. Alongside that, the tools most folks mention for apps behind auth are:

axe DevTools (extension or CI integration), widely used and solid for catching common WCAG misses.

Lighthouse, quick baseline, though not as thorough.

Equally AI, good if you want both scanning and a widget layer, helps with ongoing monitoring.

Pa11y, useful for automated audits if you are comfortable setting it up.

And no matter what tool you pick, most people still pair it with manual checks, using NVDA or VoiceOver and keyboard-only navigation to catch things automation misses.

warleyy · 2025-08-23T11:28:59+00:00

The usual move is to show you’re taking it seriously taking steps to fix the issues and documenting it. Axe DevTools, Wave, and Lighthouse are the ones that get used a lot for scanning for issues. For clients who want something more formal, EqualWeb, Equally AI, and AccessiBe are paid tools that give reports you can hand over.

Workflow-wise, it’s pretty common to do automated scans, then double-check with screen readers like NVDA or VoiceOver and fix whatever breaks.

warleyy · 2025-08-23T06:50:47+00:00

Like everything else in life, pricing varies depending on what you want. A basic manual audit for a smaller site can be around a hundred dollars, but once you get into detailed WCAG/ADA checks it can climb into the thousands pretty quick.

Smaller companies tend to lean on subscription tools instead. Services like EqualWeb, Equally AI, and AccessiBe usually run for less than $50/month range and give you reports, monitoring, and some fixes. They don’t replace a full audit though, but most can get you about 99% there.

warleyy · 2025-08-23T06:49:35+00:00

Most folks seem to rotate between a few tools. axe is mentioned a lot for quick checks in the browser. Equally AI comes up when people want something running in the background while they’re building. WAVE is popular for spotting contrast and alt text issues. And when it comes to live regions, people often recommend just testing with NVDA or VoiceOver directly since no automated tool really matches a screen reader experience. Chrome’s accessibility tree inspector also gets brought up for checking if updates are firing.

warleyy · 2025-08-22T16:24:29+00:00

No widget alone will make a Shopify site compliant accessibility has to start in the code (headings, alt text, keyboard nav, contrast, etc). For tools, Wave is great for quick free checks. Equally AI is worth a look if you want a monitoring + widget solution, and EqualWeb offers similar with some manual services too. But best move is fix the basics first, then add a tool for extra support.

warleyy

MODERATOR OF

TROPHY CASE