Article URL: https://kasperjunge.com/blog/capitalism-gone-wrong/ Comments URL: https://news.ycombinator.com/item?id=48864233 Points: 7 # Comments: 0
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
A developer guide published on DEV Community outlines how poor focus management in Angular apps creates serious barriers for keyboard and screen-reader users. Unlike sighted mouse users, keyboard navigators have a single focus position, meaning every UI change must deliberately direct where focus lands next. The article identifies four common failure points: SPA route changes that leave focus stranded, modals that trap focus but fail to return it to the trigger element on close, drawers and menus that open without shifting focus inside them, and destructive actions like row deletions that cause focus to disappear entirely. Recommended fixes include programmatically moving focus to page headings on navigation, using Angular CDK for dialog focus trapping and restoration, and leveraging afterNextRender to wait for DOM updates before redirecting focus. The guide emphasizes that automated accessibility audits cannot detect these focus-flow errors, making manual attention to focus discipline essential.
New York City Mayor Mamdani has announced new consumer protection regulations requiring businesses to offer a simple click-to-cancel option for subscriptions. The rules aim to make it as easy for consumers to cancel services as it is to sign up for them. The announcement was made through the mayor's office in 2026. The policy targets companies that use complicated or obscure cancellation processes to retain customers against their will. The move is framed as a significant step forward in consumer rights protections for NYC residents.
A developer building an autonomous AI system discovered that its append-only audit log, meant to prevent history tampering, was fundamentally broken despite appearing functional. Two separate components were writing to the same log file in incompatible formats, with no locking mechanism, causing race conditions that corrupted the hash chain. Real corrupted records were found where stored hashes did not match their content, bearing the signature of concurrent writes. The team resolved the issues by routing all audit writes through a single locked implementation, anchoring the chain with an external cryptographic signature inaccessible to the runtime, and scheduling automated verification checks. The fixes highlight that a hash chain alone represents only a fraction of what a genuinely tamper-evident audit log requires.
Companies often grant external auditors AWS access by creating IAM users or identity provider accounts, but neither approach is necessary or secure. AWS supports a cross-account IAM role mechanism that allows auditors to assume a temporary role in your account without any credentials ever changing hands. The setup relies on four safeguards: a trust policy tied to the auditor's AWS account, an External ID condition to prevent unauthorized access, time-limited STS session credentials, and full CloudTrail logging of every action taken. Permissions are restricted to read-only managed policies, with optional billing access and a supplementary policy covering services like GuardDuty and Security Hub. A developer has published two CloudFormation templates on GitHub — one for a single account and one for an entire AWS Organization — each deployable in roughly five minutes.
Discussion (0)
Log in to join the discussion and vote.
Log in