Focusable Elements Are Not Keyboard-Accessible Without Key Handlers, WCAG Warns

·1 views

A web accessibility guide highlights a common misconception: custom UI controls that receive focus are not automatically keyboard-operable under WCAG 2.1.1. A custom checkbox may display a focus ring and announce correctly via screen readers like VoiceOver, yet fail to respond to keyboard inputs such as the Space key if only a mouse click handler is implemented. The WCAG 2.1.1 Keyboard criterion requires that all functionality be available via keyboard, not just that an element be focusable. Proper implementation demands that checkboxes respond to Space for toggling, and radio groups support arrow-key navigation using a roving tabindex pattern. The guidance stresses that assigning a role and making an element focusable is insufficient — key event handlers are essential to true keyboard accessibility.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

YouTube Crawlers Explained: Metadata Scraping vs. Downloading vs. Official API

A YouTube crawler is a tool that loads public YouTube pages and extracts structured metadata — such as titles, URLs, view counts, and publish dates — into tables like CSV or JSON, but does not download video files. Three main approaches exist: web crawlers/scrapers for bulk metadata, authorized video downloaders for saving media you own, and the official YouTube Data API for developer-maintained applications. Each method suits different use cases, and choosing the wrong one can create unnecessary complexity or compliance risks. The YouTube Data API has a default quota of 10,000 units per day, and public subscriber counts are rounded to three significant figures. Regardless of method chosen, users are advised to validate collected data, preserve missing values, and log the collection date for accuracy.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer guide explains how to build an IATA-compliant boarding pass barcode in JavaScript

A detailed technical tutorial published on DEV Community walks developers through generating a valid IATA Bar Coded Boarding Pass (BCBP) payload using JavaScript, following the strict field layout defined by IATA Resolution 792. The guide covers encoding mandatory and conditional sections with precise character widths, correct padding rules, and nested hexadecimal size fields required for scanner compatibility. It also demonstrates signing the security section using the WebCrypto API so that any altered field can be detected later. The generator supports rendering the payload as four barcode symbologies — PDF417, Aztec Code, QR Code, and Data Matrix — entirely in the browser using the bwip-js library with no build step required. The project includes a self-checking parser that reads back the page's own output to verify conformance.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why Proxies Alone Won't Stop Your Web Scraper From Getting Blocked

A technical analysis explains that proxies solve only one problem in web scraping: masking the origin IP address, and nothing more. Datacenter proxies are fast and cheap but are easily flagged because their IP ranges belong to cloud providers, not real household connections. Residential proxies route traffic through genuine consumer devices, bypassing reputation checks, but are slower, costlier, and can drop mid-session when the host device goes offline. Crucially, neither proxy type addresses other bot-detection signals such as TLS fingerprints, header ordering, or request timing patterns. Teams that switch to expensive residential proxies expecting all blocks to stop are often disappointed because a bot-shaped request remains detectable regardless of how legitimate its IP looks.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Opsgenie Shuts Down April 2027: How to Migrate Before Your Data Is Deleted

Atlassian ended new Opsgenie license sales on June 4, 2025, and will fully shut down the platform on April 5, 2027, permanently deleting any unmigrated data. Existing customers have until that deadline to move, but typical migrations take six to sixteen weeks depending on integration complexity. Atlassian offers Jira Service Management as its official successor, with an automated migration tool and 120 days of parallel access for teams already embedded in the Jira ecosystem. Teams preferring a dedicated on-call tool outside a ticketing suite can migrate to alternatives like the open-source Regen, which reads existing Opsgenie configurations via a read-only API key without disrupting live setups. Experts recommend a phased cutover — running both systems in parallel for at least one full on-call rotation — before fully decommissioning Opsgenie and exporting historical data for compliance.

0 comments Read more at DEV Community