Travis Leithead
Travis Leithead
There are a few things that really make review drafts hard to read for me: * The browser's default serif font (no font-family set for the body) * Lack of...
As part of looking over the scope and charter for the recent call for review of the [Accessibility Education and Outreach Working Group](https://www.w3.org/2002/09/wbs/33280/EOWG2020charter/), I asked myself: why is this a...
Putting some thoughts down here for discussion. This is currently an open question in the spec. (This issue was split off #990) How to treat native elements that already have...
In the explainer today, focusgroup elements cause all of their direct-children to become _focusgroup candidates_, but that's it. If there are some other potential focusgroup candidates that are not direct-children,...
It has been expressed in accessibility discussions ([990](https://github.com/openui/open-ui/issues/990) and [aria-1947](https://github.com/w3c/aria/issues/1947)) that providing a visual indicator for a focusgroup could be helpful even for sighted users as a clear pattern to...
Quick fix to a broken link.
Filed from TAG review of WebSocket in HTML spec: w3ctag/design-reviews#268 WebSockets predate Streams in the platform, but there's no reason why support for Streams can't be grafted into WebSockets! The...
The explainer's data model allows height and width to be specified. Depending on the writing-mode specified on the context object, either of these dimensions could become the block-progression direction. We...
In the Houdini layout API, the metrics infra will already need to handle inline-block content in the flow of inline text. Thus a representation of this kind of content will...