profile
viewpoint
Léonie Watson LJWatson @TetraLogical Bristol, UK http://tink.uk/

bkardell/common-panel 14

An effort to define a new element with clear semantics and separation

aduggin/govuk-accessibility-sandbox 3

A place to build components that will have a public url so we can get them tested by the community.

jonathantneal/outline-tests 1

evidence gathering for the document outline

LJWatson/demos 1

Demonstrations of different HTML, CSS, JavaScript, ARIA and SVG patterns.

LJWatson/voice-xr 1

An experiment in creating a voice UI for describing WebXR content.

push eventLJWatson/website-tink-eleventy

Patrick H. Lauke

commit sha 905315634a1bf1ab378735b26283a16daaf58277

Avoid measures overflowing viewport width not tested live, but this *should* result in a rendered CSS of `max-width: min(100%,65ch)` for `.post__body>*`, which will avoid having images in small-screen view bleeding off to the right (see for instance https://tink.uk/patrick-h-laukes-goulash/ on mobile)

view details

Léonie Watson

commit sha 9bc3750eca85ec26d9be3164f72df8e20bb142a1

Merge pull request #18 from patrickhlauke/patch-1 Avoid measures overflowing viewport width

view details

push time in 17 hours

PR merged LJWatson/website-tink-eleventy

Avoid measures overflowing viewport width

not tested live, but this should result in a rendered CSS of max-width: min(100%,65ch) for .post__body>*, which will avoid having images in small-screen view bleeding off to the right (see for instance https://tink.uk/patrick-h-laukes-goulash/ on mobile)

+2 -2

1 comment

1 changed file

patrickhlauke

pr closed time in 17 hours

pull request commentLJWatson/website-tink-eleventy

Avoid measures overflowing viewport width

Oh. Lovely. Thanks @patrickhlauke

patrickhlauke

comment created time in 17 hours

delete branch LJWatson/website-tink-eleventy

delete branch : adds-recipe-post

delete time in 2 days

push eventLJWatson/website-tink-eleventy

LJWatson

commit sha 9a005482e9445aa8f456f7de5db91564b31388eb

Adds Patrick's goulash recipe post

view details

Léonie Watson

commit sha f08e3525829137d354e1c067ea399108d70355b9

Merge pull request #17 from LJWatson/adds-recipe-post Adds Patrick's goulash recipe post

view details

push time in 2 days

create barnchLJWatson/website-tink-eleventy

branch : adds-recipe-post

created branch time in 3 days

pull request commentw3c/html-aam

clarify img naming steps

@jcsteh wrote:

I'm not convinced discarding title where alt="" is present is a good thing. The title is still available on hover for sighted users.

AFAIK it's only available to sighted mouse users, and even then causes problems for magnifier users and others. It's not available to sighted keyboard users or to anyone using a touch screen device.

We've spent decades drumming it into authors that alt="" means an image is hidden from AT. We haven't succeeded in getting the message through to everyone yet, so the last thing we need is to complicate the message by throwing title into the equation.

Yes, if we agree that alt="" means an image has no accessible name, there will be times when screen reader users miss information that would otherwise be useful to them.

But if we allow title to override alt="", there will be times when screen reader users will be presented with meaningless information not intended for human consumption (think SEO stuffing), or will get duplicated and/or conflicting information.

Like @scottaohara, I've seen title misused more often than not over the years, but in the absence of actual data (as opposed to anecdotal data) to indicate which of these scenarios is the more prevalent in the wild, I caution against assuming that either one is better for users than the other.

So my preference would be to accept this PR.

scottaohara

comment created time in 4 days

push eventLJWatson/website-tink-eleventy

Nic Chan

commit sha 26dc6b6ee44141f1813d2683da415fb2dc925d6c

Fix comment display issue with fresh comments

view details

Léonie Watson

commit sha 1b92c0009dd85b2c1f372f54bbd254406f35f7de

Merge pull request #16 from nchan0154/fix-comment-display Fix comment display issue with fresh comments

view details

push time in 7 days

push eventLJWatson/website-tink-eleventy

LJWatson

commit sha af0b154c136694f79f99d4a786408611b6238552

Experimental date format change

view details

push time in 8 days

push eventLJWatson/website-tink-eleventy

LJWatson

commit sha f97d230b3a7b2006a07214f227c63c03236f6aae

Changes 'Filed under' heading text

view details

push time in 8 days

push eventLJWatson/website-tink-eleventy

LJWatson

commit sha 633a76f7ce6966171a2adf9cf12d512175439676

Corrects conference JSON

view details

push time in 8 days

push eventLJWatson/website-tink-eleventy

LJWatson

commit sha 39361e2bcfc358d6bd2a2e29dee580ce4c2fc5ef

Corrcts conferences JSON

view details

push time in 8 days

push eventLJWatson/website-tink-eleventy

LJWatson

commit sha f71ea2881b7d0a948b226edd811a0a60859dfe1e

Updates conferences JSON

view details

LJWatson

commit sha def9e3a5090aa607eaf6cb45364ea21f2350c1f1

Merge branch 'main' of https://github.com/LJWatson/website-tink-eleventy

view details

push time in 8 days

push eventLJWatson/website-tink-eleventy

Nic Chan

commit sha 17ae488a42047528f21505cdc4f8e5a78e8a2888

Add accessible commento implementation from tetralogical

view details

Léonie Watson

commit sha e1b42eba2377e0c4708c6fd00254d5a45e18d385

Merge branch 'main' into commento

view details

Léonie Watson

commit sha 6175d0c21c4f2cbea03cb4803753e816a5da12eb

Merge pull request #14 from nchan0154/commento Add accessible commento implementation from tetralogical

view details

push time in 8 days

push eventLJWatson/test-cases

LJWatson

commit sha 0adb318596d13e7c6bdd5d452ff98760b0775967

Removes gz file

view details

push time in 8 days

push eventLJWatson/test-cases

LJWatson

commit sha c40373bb2c9e6ce288f7e4d8733f4b36b25417d7

Replaces gz file

view details

push time in 8 days

issue commentw3c/w3process

The 2021 "Revising a Recommendation Process" is painful for WGs

The process introduced in 2020 not withstanding, a specification can be in one of six states: ED, FPWD, WD, CR, PR, and Rec. That's a lot of stages even before you add CR Drafts, CR Snapshots, Candidate Editions etc.

I agree with @marcoscaceres that we could do with some fundamental rethinking, so here goes...

Based on the incubation process, when a spec moves into a WG and onto /TR, it could immediately be published as an FPWD, triggering the patent exclusion and wide/horizontal review.

With some WG already auto-publishing their ED straight to WD, the WD could become the "work in progress" version of the spec and we could do away with ED altogether.

We'd need to keep FPWD and CR because they both trigger patent exclusions and wide/horizontal reviews, but could we combine CR and PR into a single stage?

Implementation experience would need to be a requirement to enter CR instead of exit it, but again this is a direction some WG are already moving in.

If the AC was included in the wide review done in preparation of advancement to CR, it would give them an opportunity to raise any issues at a time where they could still be dealt with without generating more admin overhead. As with issues raised during wide and horizontal review already, the WG could need to provide evidence that they'd been dealt with appropriately.

Then, assuming all other transition requirements are met, the WG consents to transition to CR, and the Director (or whatever Director-free solution we arrive at) approves, the CR is published.

This triggers the patent exclusion and the final AC review (though the latter may be delayed to allow the patent exclusion period time to run down first), and assuming they both go OK, the Rec is published.

Probably lots of reasons why this would not work, but...

msporny

comment created time in 12 days

push eventLJWatson/decks

LJWatson

commit sha d158e6b1e7ebfe1ec81170f01308ae87ec4d6427

Adds C'T Webdev deck

view details

push time in 12 days

pull request commentw3c/w3process

Make the Team responsible for Group creation and Closure

People keep on saying that. In my mind creating and approving work has to be owned by an elected body, and if not the TAG, who? OTOH I don't see how spec reviews require the authority of an elected body -- the TAG can and should delegate some of this work if necessary.

That could help alleviate the impending problem, yes.

frivoal

comment created time in 19 days

pull request commentw3c/w3process

Make the Team responsible for Group creation and Closure

@mnot

I'm not happy with this -- given the relative inactivity of the AC, and its composition, its' not really a good custodian of the technical roadmap for activity at the W3C. Better to invest this authority with a body that's accountable to the AC, like the TAG.

It's a fair point about AC engagement, though if the AC is not the appropriate custodian of the technical roadmap, does that also include deciding which WG are created do you think?

As an aside, I'm worried that the TAG and/or AB are often suggested as an alternative to many of TimBL's erstwhile responsibilities though, when they're both already extremely busy.

frivoal

comment created time in 20 days

pull request commentw3c/w3process

Make the Team responsible for Group creation and Closure

@caribouW3

Would there be a reason that could make it really urgent to close a WG right away in the middle of the charter duration?

That's a good question. Do we have any data about how often and why early closure has been needed in the past?

frivoal

comment created time in 20 days

push eventLJWatson/test-cases

LJWatson

commit sha ae56d6422a8e8bb81799d606408d9a6ad65627eb

Updates .gz file

view details

push time in 21 days

push eventLJWatson/test-cases

LJWatson

commit sha 98c58b03cef2e66f16209b78f179bc65c65b9a6c

Adds comments in different format

view details

push time in 21 days

push eventLJWatson/test-cases

LJWatson

commit sha c0b4a70877272a8be95dd3ab93e4a67288a13d47

Replaces temporary comments file

view details

push time in 21 days

push eventLJWatson/test-cases

LJWatson

commit sha d50f18d6f030b5b238d9eb19cfb6bf9579957c6c

Uploads temp comments file

view details

push time in 22 days

push eventLJWatson/website-tink-eleventy

LJWatson

commit sha 5cfe8c5d8fe15b68a785a5d21090b9c96a5d3b6d

Removes comments

view details

push time in 22 days

more