W3C

– DRAFT –
Accessibility at the Edge Teleconference

22 Jan 2024

Attendees

Present
-
Regrets
-
Chair
Janina
Scribe
janina, Lionel

Meeting minutes

Welcome and Introductions (as needed)

We have several regrets and no new participants today.

Continue Capabilities Reorganization

subsection: What are available outputs from Figjam?

We looked and find only CSV or Figma stickies

janina: So, tool takes html as input but does not provide html output?

subsection: Review of reorg continues

janina: We should stay with the terminology commonly adopted by the community, even if we dont find it sufficiently useful

jason: Agree that it has become an industry term
… it has some valuable components as defining a domain
… but if you ask someone to describe an overlay, they would lead with things that pop up on a screen, take control of assistive technology
… and would hardly talk about any of the capabilities that we are talking about here, technically
… so perhaps we could say, those things are not part of javascript include
… we need to discuss what can you do well, and what can you do safely, from the edge

janina: We understood that no one wants to read the entire list, we see the table of contents as enabling people to jump to the section that interests them

Lionel: Agree with Jason

Lionel: If we differ it's been in tactic -- how we put this together

jason: Interested in what can be automated

jason: Duplicated id hrefs on a site are an example of what cannot be auto remediated

Lionel: Trying to find the abstract explanation of what is done

janina: WCAG itself has the binary pass/fail issue built into it

janina: We are not after full accessibility, we are after how well can we succeed in resizing text, enhancing contrast, along the lines of how individual users need those adjustments
… that is more interesting than something called full accessibility

jason: Companies use edge technologies, some by only handcrafting the fixes

jason: Suggesting we enumerate WCAG 2.2 SC by SC as which are automatable, and which not

Lionel: Believe we can break down as static or dynamic analysis

Lionel: Listing exactly what automated detection and automated remediation can do today is subject to change rather rapidly
… w3c is a slower moving body than that
… I see the value in our bringing to the conversation very clear high level "ingredeients" list
… so a company that provides something relating somewhat to the term 'overlay' can say
… Are you looking for a widget that does personalization changes like text size? well maybe go to such and such a company, we dont do that
… are you looking for automated detection? We're happy to discuss that
… are you looking for handcrafted code to be provided via edge technology, so we can do accessibility development for you? We do that.

jason: These are reasonable buckets for discussing the topic

Lionel: Personalization (CSS-type adjustments), Automated detection, Automated remediation, Hand written code via Edge, Miscellaneous

jason: This isn't a linear list

jason: Customization, Automation, Handcrafted Code, Miscellaneous

Minutes manually created (not a transcript), formatted by scribe.perl version 221 (Fri Jul 21 14:01:30 2023 UTC).

Diagnostics

No scribenick or scribe found. Guessed: Lionel

Maybe present: janina, jason, Lionel, subsection

All speakers: janina, jason, Lionel, subsection

Active on IRC: janina, Lionel